Name: Recipes App
Availability: InStock

Get started

Ready to build

Build the app you keep thinking about.

Describe your idea. Sanic AI builds the real app, end to end.

Start building See how it works

Built with Appsanic

Recipes App

Save what you cook, plan what's next

A complete recipes starter. Two-column browse grid of emoji-hero cards with name, cook time and difficulty, filtered by category. Recipe detail with tick-off ingredient checkboxes, a numbered method, and a servings stepper that scales every quantity live. Cook mode swaps the sticky bar for a Prev / Next-step / Exit toolbar, tinting the active step. Saved tab with per-category filter chips and live counts. Shopping list auto-derived from your saves, all owner-scoped on your own Supabase.

Two-column browse grid by category with emoji hero, cook time and difficulty
Recipe detail with tick-off ingredient checkboxes and a numbered method
Servings stepper that scales every ingredient quantity live
Cook mode: Prev / Next-step / Exit toolbar with active-step highlight
Saved tab with per-category filter chips and live counts
Shopping list auto-derived from your saved recipes

Use this template

What you can do

Skillet is a recipes starter: a bundled cookbook you browse by category, with a recipe detail that scales ingredient quantities live to your chosen servings, a step-by-step cook mode, a saved tab, and a shopping list auto-derived from everything you've saved. It runs entirely on your own Supabase project, so it opens on a Connect screen until you wire up a backend and sign in (or tap Preview with sample data to look around first). The recipe library ships in the app, so it's browsable either way; only which recipes you save is stored.

Made forHome cooks who want to save recipes, scale them to any number of servings, and turn their saves into a single shopping list.

Browse a bundled cookbook in a two-column grid, filtered by category (Breakfast, Mains, Salads, Desserts, Drinks)
Open a recipe to tick off ingredients and scale every quantity live with a servings stepper
Cook hands-free in cook mode: a Prev / Next-step / Exit toolbar highlights the active step and marks past steps done
Save recipes with a tap of the heart; saves are private to you and sync across your devices
Filter your saved recipes by category with live counts
Get one tidy shopping list automatically combined from every saved recipe's ingredients, and tick items off as you shop
See cooking stats on your profile (saved count, items to buy, favourite category) derived from your saves

Under the hood

For developers: exactly what is included when you start from this template, taken straight from the template's own code.

Stack

Expo SDK 54 (managed workflow, registerRootComponent entry)React Native 0.81.5React 19.1.0 / react-dom 19.1.0TypeScript ~5.9.2@supabase/supabase-js ^2.45 (Auth + Postgres + Realtime)react-native-safe-area-context, react-native-svg (custom icons), expo-status-barreact-native-web 0.21 (web target via Metro)No navigation library: hand-rolled useState routing with a useSyncExternalStore saves store

Screens

Connect
Shown until Supabase is configured: explains how to connect a backend and apply the schema, with an optional Preview with sample data button.
Auth
Real Supabase email/password sign-in and sign-up; sign-up captures a display name.
Browse
The cookbook: a category filter row over a two-column grid of emoji-hero recipe cards (cook time + difficulty), with a quick-save heart.
Recipe detail
Full-screen overlay with a servings stepper that scales quantities live, tick-off ingredients, and a numbered method; Start cooking enters cook mode (Prev / Next / Exit, active step tinted).
Saved
Your saved recipes (the only persisted data) in the same grid, with per-category filter chips and live counts.
Shopping
A combined shopping list auto-derived from the ingredients of every saved recipe; tick items off as a session-only aid.
Profile
Account header with cooking stats and a saved-by-category breakdown, plus sign out (or Exit preview in preview mode).

Data model

customers
One row per user, mirroring auth.users (id, email, display_name, created_at); created automatically on signup, read-only to its owner.
saved_recipes
One row per saved recipe holding the bundled recipe's text recipe_id, owner-scoped and unique per (owner_id, recipe_id); the recipe library itself is bundled app content, not a table.

Backend

Row Level Security on both tables: customers is read-only to its owner (id = auth.uid()), saved_recipes is full CRUD restricted to the owner (owner_id = auth.uid())
Trigger on_auth_user_created on auth.users runs the SECURITY DEFINER function handle_new_customer() to insert the customers row (deriving a display name from metadata, email, or 'Cook')
Realtime: saved_recipes is added to the supabase_realtime publication and set to REPLICA IDENTITY FULL so live sync (including DELETEs) carries owner_id for the device-to-device subscription
The shopping list is computed entirely on the client from saved recipes' ingredients; no aggregation table
No SECURITY DEFINER RPCs beyond the signup trigger, no storage buckets, and no Edge Functions

More templates

All templates

Lifestyle

Fitness Tracker App

Log workouts, see real progress

View template

Social

Photo Journal App

One photo a day, with your friends

View template

Social

Social Feed App

An Instagram-style starter: feed, stories, likes, comments, follows, and an activity inbox

View template

Social

Live Streaming App

Broadcast yourself, watch others live

View template

Built with Appsanic

Recipes App

Save what you cook, plan what's next

Two-column browse grid by category with emoji hero, cook time and difficulty
Recipe detail with tick-off ingredient checkboxes and a numbered method
Servings stepper that scales every ingredient quantity live
Cook mode: Prev / Next-step / Exit toolbar with active-step highlight
Saved tab with per-category filter chips and live counts
Shopping list auto-derived from your saved recipes

Use this template

What you can do

Made forHome cooks who want to save recipes, scale them to any number of servings, and turn their saves into a single shopping list.

Browse a bundled cookbook in a two-column grid, filtered by category (Breakfast, Mains, Salads, Desserts, Drinks)
Open a recipe to tick off ingredients and scale every quantity live with a servings stepper
Cook hands-free in cook mode: a Prev / Next-step / Exit toolbar highlights the active step and marks past steps done
Save recipes with a tap of the heart; saves are private to you and sync across your devices
Filter your saved recipes by category with live counts
Get one tidy shopping list automatically combined from every saved recipe's ingredients, and tick items off as you shop
See cooking stats on your profile (saved count, items to buy, favourite category) derived from your saves

Under the hood

For developers: exactly what is included when you start from this template, taken straight from the template's own code.

Stack

Screens

Connect
Shown until Supabase is configured: explains how to connect a backend and apply the schema, with an optional Preview with sample data button.
Auth
Real Supabase email/password sign-in and sign-up; sign-up captures a display name.
Browse
The cookbook: a category filter row over a two-column grid of emoji-hero recipe cards (cook time + difficulty), with a quick-save heart.
Recipe detail
Full-screen overlay with a servings stepper that scales quantities live, tick-off ingredients, and a numbered method; Start cooking enters cook mode (Prev / Next / Exit, active step tinted).
Saved
Your saved recipes (the only persisted data) in the same grid, with per-category filter chips and live counts.
Shopping
A combined shopping list auto-derived from the ingredients of every saved recipe; tick items off as a session-only aid.
Profile
Account header with cooking stats and a saved-by-category breakdown, plus sign out (or Exit preview in preview mode).

Data model

customers
One row per user, mirroring auth.users (id, email, display_name, created_at); created automatically on signup, read-only to its owner.
saved_recipes
One row per saved recipe holding the bundled recipe's text recipe_id, owner-scoped and unique per (owner_id, recipe_id); the recipe library itself is bundled app content, not a table.

Backend

Row Level Security on both tables: customers is read-only to its owner (id = auth.uid()), saved_recipes is full CRUD restricted to the owner (owner_id = auth.uid())
Trigger on_auth_user_created on auth.users runs the SECURITY DEFINER function handle_new_customer() to insert the customers row (deriving a display name from metadata, email, or 'Cook')
Realtime: saved_recipes is added to the supabase_realtime publication and set to REPLICA IDENTITY FULL so live sync (including DELETEs) carries owner_id for the device-to-device subscription
The shopping list is computed entirely on the client from saved recipes' ingredients; no aggregation table
No SECURITY DEFINER RPCs beyond the signup trigger, no storage buckets, and no Edge Functions