Development of a cookbook database as a mobile application, as well as an accompanying service for transforming recipe texts into a uniform recipe format.
The mobile application can be considered an MVP for future developments.
The ICW should serve as a starting aid for a larger development project, in which the developed cookbook database app should mature into a complete cookbook and meal-planning app. An important part of the already existing concept is the recipe recognition from different materials: normal text, photos, or websites. The conversion of text forms the basis, which is why it should be worked on first.
The idea for the planned application has mainly arisen from personal interest and demand. Although there are already some cookbook and meal-planning apps on the market (such as KptnCook, Whisk, Cookstash, and many more), no application was found that offers all desired features - not even for a fee. The goal is to fill this gap and provide the user with all online features as a paid option. In this way, cross-platform sharing functions - similar to those of Obsidian (https://obsidian.md/) - can also be implemented for people who do not want to invest money.
As this ICW is a practical project, little literature is required. However, documentation on frameworks and tools (such as Spring Boot, React Native, Docker, etc.) is likely to be frequently used. In addition, clean code guidelines should be followed during development, as described in "Clean Code," "Clean Architecture" by Robert C. Martin, or "Effective Java" by Joshua Bloch.
The development of the cookbook and meal planning app has already been divided into epics/features to provide an overview of the concept and necessary functions. The following graphic shows this planning.
The epics should be worked on from top to bottom because the included features build on each other.
The recipe recognition epics are shown somewhat separated in this graphic because they can and should be worked on separately. If possible, recipe recognition should be provided as a separate microservice and provide an API for the respective functions (text, web, image).
Epic division and hierarchy
For the "recipe database" epic, a feature breakdown was already performed in the sense of MVP development, and a sorted backlog of tasks was created.