Example Recipes

A recipe is a complete, real app taken from /kit-start-setup all the way to Google Play — showing the exact choices you make at each question. Whatever you're building, one recipe is close to your path. Copy its choices, swap in your name, color, and screens.

Why recipes exist: the kit asks you a lot of yes/no/which questions during setup. Each combination produces a different app (free vs paid, login vs none, hard vs soft paywall, Supabase vs Firebase). Recipes are pre-made answer sheets for the common combinations, so you're never guessing what to pick.

Recipes don't introduce new commands — they show the choices inside the commands you already have. Run /kit-start-setup and follow a recipe's table.

---

Pick the recipe closest to your app

Each recipe's page says when it fits — plus a design reference, the full choice table, the build + ship commands, and what you'll see on the device. Mix and match freely; these are starting points, not rules.

---

How to use a recipe

1. Open the recipe closest to your app (links above).
2. Run /kit-start-setup.
3. When it asks a question, answer with the recipe's choice (swap in your own name, package, color).
4. After setup, run the recipe's follow-up commands (e.g. /kit-setup-ai, /kit-design-app, /kit-generate-aso, /kit-generate-landing).
5. Run the device sanity checklist below before you ship.

---

Things to check on your device

After any recipe, a quick sanity pass:

• Only one splash (Android's own) — the app doesn't show a second.
• A free / no-login app goes straight to Home — no login or paywall screens.
• A hard paywall can't be dismissed; a soft paywall has "Maybe later".
• After subscribing (or "Restore"), the paywall doesn't show again.
• Sign out from anywhere sends you back to the login screen.
• Delete account works and lands you back on login (no blank screen).
• Your app icon is your brand mark and the launcher background is your brand color.
• Settings → Open-source licenses lists the libraries (not blank).
• If you only ship one language, the Language row in Settings is hidden.

Re-running a setup command is safe — it notices what you already configured and offers to keep it, change one thing, or start that piece over. You won't be asked everything twice.

---

A note for maintainers

The five recipes are deliberately orthogonal — together they exercise every branch of the kit exactly once (free/paid, no-auth/Supabase/Firebase, hard/soft paywall, Room/Supabase data, each analytics provider, AI on/off, simple vs questionnaire onboarding). So the recipe set doubles as a manual device-test matrix: run all five and you've tested every path.

Next: Components Catalog — the building blocks every recipe uses.