From an ingredient to a checked shopping list.
Connect planning with everyday action.
Where this work fits
A meal-plan template still needs dates, recipes, and progress before a customer can follow it. People also need to find suitable content, save choices, and turn ingredients into a shopping list.
I built shopping-list operations and checked-item state for customers. Ownership checks kept actions scoped to the correct list, and reversible state let an item move between active use and history.
Turn ingredients into a list people can use
Everything for the soup.
0 of 3 ingredients collected. Each item keeps its own state.
Share the content, keep progress personal.
The original plan and a customer’s copy had different jobs. I modeled personal dates and completion separately, checked membership for premium activation, and handled conflicts such as placing two meals in the same slot. Catalogue filters helped narrow the recipes people could choose from.
The skills behind the work
- Data integrity
- Keep records, ownership, and associations consistent as information changes.
- State management
- Represent what is happening now and define which changes are valid next.
- SQL
- Query and update relational data, with clear rules about which records a result represents.
Membership gave customers a plan they could start and follow, with saved choices and progress. Recipe ingredients could become a reusable shopping checklist.