08 / WEB DEVELOPMENT
Oppskriftslaboratoriet
A personal recipe notebook with search, ratings, meal planning, and a shopping list. Data stays in browser storage.
Visit live site
The objective
Bring recipes, cooking notes, and planning into one interface. The published app shows search and categories; the implementation also includes editing, favorites, meal planning, and a shopping list.
My contribution
- Developed the idea and defined features for a personal recipe notebook, meal plan, and shopping list.
- Worked on design decisions, testing, troubleshooting, and improvements over several iterations.
How I worked
I used Codex and other AI tools extensively for code implementation. My work focused on developing the idea, defining functionality, making design choices, testing, troubleshooting, and improving the product over several iterations. The technical overview describes the implementation; it does not imply that I wrote all the code independently.
Technical challenges & approach
Separating persistence from the interface
A storage interface and repository layer centralize operations for recipes, planning, and shopping lists. The implementation uses localStorage. An asynchronous interface alone does not make it a server-backed application.
Preserving personal recipes during updates
A versioned migration separates built-in recipes from user-created ones. Deleted recipes can be kept in a trash area before permanent removal. Forms use React Hook Form and Zod; storage failures and imported data still need targeted testing.
Learning focus
A concrete example of separating presentation, domain operations, and persistence, and of keeping demonstration content distinct from a user's own data.
Project scope
No authentication or server database in the reviewed implementation. Browser storage does not provide cross-device sync or backups. Nutrition and price information are estimates. No automated test suite was found in the repository.