Frequently asked questions.

No. DishDrama runs in your browser, and as a Progressive Web App you can 'Add to Home Screen' for an app-like experience with push notifications. No app store, no native app to maintain.

About five minutes. Create the flat, add 3–5 meals (Breakfast/Lunch/Dinner with their times), drop in 10–15 dishes you'd happily eat, share the invite code in your flat group chat. Done.

Optional. The cook can sign up to use the dedicated cook dashboard (which lets them mark meals as done and send messages to the flat). But there's also a public read-only URL you can share that requires no login — the cook just bookmarks it on their phone.

A scheduled job runs every minute. When a meal's trigger time hits (in IST), it picks a dish from your pool that (a) is preferred for this meal — or has no preference, (b) hasn't been served in the last 3 days, (c) is under its per-day cap. If the strict pool is empty, it relaxes filters one at a time so it always picks something when the pool has dishes.

Yes — at any time. Any flatmate can change today's dish from the meal card. Cooks can change it too, but they have to pick a reason (ingredient not available, made recently, member requested, other) so the rest of the flat sees why.

Tap the 'Skipping' toggle on the meal card. The cook's 'COOK FOR N' number drops by one immediately. If you're bringing a guest, use the +1 stepper and add a note like 'my sister'.

Yes — if you change attendance or the dish after the cook has marked the meal as in-progress, they get a push notification so they can adjust.

DishDrama V1 is free. We're running it on free tiers of Supabase and Netlify, and there's no plan to monetize the core flatmate coordination loop.

In a Supabase Postgres database in the ap-south-1 (Mumbai) region. We store: profile (name, optional phone, optional photo), flat membership, meals, dishes, who picked what when, who's skipping, notes, and cook submissions. That's it.

Only members of the flat can read its data through the app. The public cook URL is read-only and only exposes today's dishes + headcount + notes — no member emails, phones, or per-member attendance breakdown beyond first names.

We use Plausible (privacy-friendly, no cookies, no cross-site tracking) on the marketing pages only — to know if anyone's reading this FAQ. Inside the authenticated app, no analytics scripts are loaded.

V1 is hardcoded to IST (Asia/Kolkata) because we're building for flats in India. Multi-timezone support is on the V2+ list once there's demand.

Grocery management (request items / cook acknowledges), email invite links, Google sign-in, per-member dish-change limits, and a monthly cook attendance report. Native apps are on the long-term list but PWA covers most of the use case.

Email us, or open an issue on GitHub. Both routes feed the same backlog.