Recipe App Design: Search, Cook Mode and Lists
Recipe app design guide: the core screens, ingredient scaling, hands-free cook mode, smart shopping lists and search filters, with specs and copyable prompts.

This guide is for founders and designers building a recipe, meal-planning or cooking app. It walks through every core screen, the decisions that separate a pleasant recipe app from a frustrating one, and the details people only notice when their hands are covered in flour. You will finish with a screen list, specs and prompts you can use to draft the whole app.
TL;DR: Design for two very different moments: browsing on the sofa and cooking at the counter. Browsing needs fast search, strong photos and honest filters. Cooking needs huge text, one step at a time, inline timers, ingredient amounts inside each step and a screen that stays awake. A shopping list that merges and groups ingredients is what turns a recipe app into a weekly habit.
The two modes of recipe app design
Most recipe apps fail because they design only for browsing. The person in your app is in one of two states:
| Mode | Context | What they need |
|---|---|---|
| Plan and browse | Sitting down, both hands free, deciding what to cook | Search, filters, photos, ratings, time and difficulty, save to collection |
| Cook | Standing, messy hands, phone propped 50 cm away | Large type, one step per screen, timers, no accidental taps, screen stays on |
Every screen decision follows from which mode it serves. A recipe detail page is the handover between them, so it has to work in both.
Core screens and what each one must do
1. Onboarding and preferences
Ask only what changes the results: dietary needs (vegetarian, vegan, gluten-free, halal, kosher), allergies, household size and cooking skill. Make every question skippable. Allergies are the one place to be precise; let users add custom exclusions such as "coriander" or "peanuts." For more on structuring these flows, see our onboarding screen design guide.
2. Discover or home
A home feed usually mixes personalized rows ("Quick weeknight dinners," "Uses what you saved") with seasonal and editorial collections. Keep each card scannable:
- •Photo with a consistent aspect ratio (4:3 or 1:1 across the feed).
- •Title in 2 lines maximum.
- •Total time and one other attribute (difficulty, calories or rating).
- •A save icon with a 44 pt tap target.
NYT Cooking and Tasty both lead with strong photography and curated collections, which is a good model: the photo sells the recipe, the metadata qualifies it.
3. Search and filters
Search is the highest-intent screen in a recipe app. People search by dish ("lasagne"), by ingredient ("chicken thighs"), by constraint ("30 minutes") and by occasion ("picnic"). Support all four.
Filters that earn a place:
| Filter | Type | Notes |
|---|---|---|
| Total time | Chips: under 15, 30, 60 min | Use total time, not just cook time |
| Diet | Multi-select chips | Pre-apply from onboarding, show it as removable |
| Include ingredients | Token input | "Use up what's in the fridge" searches |
| Exclude ingredients | Token input | Allergies and dislikes |
| Cuisine | Multi-select | Collapse into a sheet if long |
| Difficulty | Easy, medium, hard | Define what each means |
| Equipment | Air fryer, slow cooker, oven-free | Popular and underserved |
Show the result count live as filters change and never return an empty page without suggesting which filter to relax. Recent searches and "popular this week" suggestions make the empty search field useful before the user types anything. The browse-to-detail patterns in our ecommerce user flow post translate directly to recipes.
4. Recipe detail
This is the most important screen. Recommended order, top to bottom:
- •Hero photo (or short video), title, rating and author.
- •Key facts row: total time, active time, servings, difficulty.
- •Primary action: "Start cooking."
- •Servings stepper and unit toggle (metric or US).
- •Ingredients, grouped by component ("For the sauce," "For the topping"), each with a checkbox.
- •"Add to shopping list" button directly under ingredients.
- •Method steps, numbered, previewed in full.
- •Notes, substitutions, nutrition, reviews.
Put a "Jump to recipe" affordance at the top if you include any story or introduction. The long preamble is the most mocked pattern of recipe websites, and apps have no SEO reason to copy it.
5. Cook mode (step-by-step)
Cook mode is where your app beats a website. Specs that work at counter distance:
| Element | Spec |
|---|---|
| Step text | 24 to 28 pt, line height about 1.35, high contrast |
| Steps per screen | One |
| Next / previous | Full-height tap zones or large buttons at least 64 pt tall |
| Ingredients in step | Show the exact amounts inline: "Add 200 g flour" |
| Timers | Tap a time in the text ("bake 25 minutes") to start a timer |
| Screen | Keep awake while cook mode is open |
| Progress | "Step 3 of 9" plus a thin progress bar |
Useful extras: a swipe-up panel with the full ingredient list, multiple named timers running at once ("Pasta 4:12," "Sauce 9:30"), and optional voice commands like "next step" for hands-free use. If you support voice, show a clear listening indicator and let people turn it off.
6. Shopping list
The shopping list is what turns occasional use into a weekly routine. It needs to be smarter than a notes app:
- •Merge duplicates: two recipes with onions become one line, "3 onions."
- •Normalize units: combine "100 g" and "150 g" butter into "250 g."
- •Group by aisle: produce, dairy, meat, pantry, frozen.
- •Show source: tap a line to see which recipes need it.
- •Pantry staples: let users mark salt, oil and spices as "always have."
- •Share: a household list that syncs between two phones.
Check-off rows should be at least 48 pt tall with the checkbox on the leading edge, and checked items should move to a collapsed "Done" group rather than disappearing.
7. Saved, collections and meal planner
Let people save into collections ("Weeknights," "Hosting"). A weekly planner with drag-and-drop days is a natural next step; when a user plans meals, offer to add every ingredient to the shopping list in one tap. Paprika and Mealime both build their value around this plan-to-list loop.
Ingredient scaling: the details that matter
Scaling looks simple and is easy to get wrong.
- •Scale numbers, then round to kitchen-friendly values: 0.33 cups becomes "⅓ cup," 2.9 eggs becomes "3 eggs" with a note.
- •Do not scale everything linearly: salt, spices, baking times and pan sizes often need a note rather than a multiplier.
- •Keep a clear unit toggle. Show grams and millilitres for metric users and cups and ounces for US users.
- •Show the original servings as a reference: "Scaled from 4 to 6 servings."
Visual system for a recipe app
Food photography does most of the visual work, so the interface should stay quiet.
- •Color: a neutral or warm background with one accent for actions. Avoid saturated greens and reds in the UI that compete with food colors. Our mobile app color palette guide explains how to assign roles, and the color picker from image tool can pull a palette from your hero photography.
- •Type: a characterful serif or rounded sans for headings, a highly legible sans for steps. Use the font pairing tool to test combinations, and follow our mobile typography guide for sizes.
- •Dark mode: useful in evening kitchens. Make sure step text stays at high contrast; see our dark mode app design post.
Recipe app screen checklist
- • Preferences onboarding with skippable questions and custom exclusions
- • Discover feed with consistent card format and save action
- • Search by dish, ingredient, time and occasion
- • Filters with live result counts and a no-results recovery
- • Recipe detail with key facts, servings stepper and unit toggle
- • Ingredients grouped by component with "Add to list"
- • Cook mode with one step per screen, inline amounts and tappable timers
- • Screen stays awake in cook mode
- • Shopping list that merges, normalizes and groups by aisle
- • Collections and optional weekly planner
- • Empty states for saved, list and planner
- • Reviews with photos and "I made this" signals
Copy-and-paste prompts for each screen
You can generate a first draft of these screens in floow and refine them through chat. Prompts that work well:
Recipe detail screen for an iOS cooking app: full-bleed hero photo, title, 4.7 rating, facts row with total time 35 min, servings 4, easy. Servings stepper and metric/US toggle, ingredients grouped into "Pasta" and "Sauce" with checkboxes, "Add to shopping list" button, then numbered method steps. Warm cream background, terracotta accent.
Cook mode screen: one step per screen in 26pt text, "Step 3 of 9" with a thin progress bar, ingredient amounts bolded inline, a tappable "12 minutes" that starts a timer, two running timers in a pill at the top, large previous and next buttons at the bottom.
Shopping list screen grouped by aisle (Produce, Dairy, Pantry), merged quantities like "3 onions", each row showing source recipe count, checked items collapsed into a Done section, and a share button for a household list.
FAQ
What features should a recipe app have?
At minimum: search with filters, recipe detail with scaling, a step-by-step cook mode, saved recipes and a shopping list. Meal planning, pantry tracking and household sharing are the features that drive repeat weekly use.
How big should text be in a recipe app's cooking mode?
Larger than normal reading text, because the phone sits on a counter. Around 24 to 28 pt for step text works well, with high contrast, while still honoring the user's Dynamic Type or font scale settings.
How do I handle ingredient scaling?
Multiply quantities, then round to practical kitchen fractions and units, and add notes where linear scaling does not apply, such as seasoning, leavening, pan size and cook time. Always show the original serving count for reference.
Should a recipe app include a life story before the recipe?
No. App users come for the recipe. If you include author notes, put them below the method or behind a "Read the story" link, and always provide a way to jump straight to ingredients.
Design it with floow
Draft your recipe app's discover, detail, cook mode and shopping list screens in floow, then export them to Figma or code. Start with:
Design a 5-screen recipe app: discover feed with collection rows, search with time and diet filter chips, recipe detail with servings stepper, hands-free cook mode with large step text and timers, and a shopping list grouped by aisle.
Design your mobile app with AI.
Generate pixel-perfect iOS and Android screens in seconds, then export to Figma or code.
You might also like…
Insights17 November 2026Mobile Checkout Design: 11 Patterns That ConvertMobile checkout design patterns that reduce abandonment: guest checkout, wallet pay, smart forms, clear totals and error handling, with specs and a checklist.By floow.design
Insights17 November 2026How to Make an iPhone App: Design, Build, ShipHow to make an iPhone app step by step: scope it, design iOS screens to Apple's rules, pick SwiftUI or cross-platform, test in TestFlight and pass App Review.By floow.design
Guides16 November 2026User Flow Diagram: How to Make One, With App TemplatesHow to make a user flow diagram step by step: notation, happy and unhappy paths, tools, and copy-ready templates for sign-up, checkout and booking.By floow.design