Daily Rasoi
A household meal planning app that builds weekly meal plans and grocery lists around your family's size, preferences, and pantry — so dinner stops being a daily decision.
Overview
Daily Rasoi plans your household’s meals for the week and turns that plan straight into a grocery list. It’s built around one entity — your household — and everything else (servings, ingredient exclusions, what gets cooked when) is personalized against it.
How Onboarding Works
Setup is a short, five-step flow: a welcome screen, household composition (adults and children, which drives default servings), which meals you actually want planned (breakfast, lunch, dinner, snacks), the ingredients your household doesn’t eat, and a review step that estimates how many dishes are available given your exclusions before generating your first active meal plan.
Ingredients are opt-out, not opt-in — everything is included by default, grouped into vegetables, fruits, pulses, grains, dairy, eggs, and spices, and the household only marks what to avoid. That keeps the exclusion list short and the planner’s dish pool as large as possible.
Core Features
- Household-aware planning — meal plans and grocery quantities scale to your household’s adult and child count
- Selective meal slots — plan only the meals you want covered; the choice persists across regenerations
- Ingredient exclusions — mark what your household doesn’t eat once, and the planner respects it everywhere
- Grocery list generation — the weekly plan turns directly into a shopping list, grouped for a real grocery trip
- Meal swapping and templates — swap out individual meals or apply reusable meal templates without rebuilding the whole week
- Prepared food reuse — plan around leftovers and prepared dishes instead of always starting from scratch
- Today / Tomorrow views — a glanceable look at what’s cooking now and what to prep next
Architecture
Daily Rasoi is a native SwiftUI iOS app backed by GRDB/SQLite for local persistence. The household profile, planned meal slots, and ingredient exclusions are written atomically in a single transaction, and a dedicated planner engine generates, validates, and activates meal plans against that data — keeping planning logic independent of the views that display it.
Status
In active development.