Plated Meal Decision Concept
A family nutrition app concept, reimagined around the question “what’s for dinner?”
Primary Role:
UX/UI Designer
Timeframe:
3 days - 2026
Project Type
Concept challenge
Executive Summary
I designed Plated, a fictional mobile app, as a self-directed challenge to solve one everyday problem: parents know how to cook, but deciding what to make at every meal is exhausting. I designed the core experience end to end: a time-aware home card that asks "What's for breakfast", “What’s for lunch?” or “What’s for dinner?” which leads to a three-question flow that narrows the answer to three options, a recipe detail screen, and a resolved state that logs the meal into daily nutrition tracking. Everything is grounded in my own assumptions and design reasoning.
Industry
Family health & nutrition
The Problem
Deciding what to eat is harder than knowing how to cook it.
Parents don’t need another recipe database, they need a faster way to decide what works for their family, for each meal, with what they actually have. The friction isn’t a lack of knowledge or recipes; it’s the repeated daily translation of “some ingredients, limited time, picky eaters” into one concrete, healthy decision, and it happens up to three times a day, not once.
Who I designed for: Parents managing their family’s day-to-day meals
Opportunity
Most nutrition apps are built around logging and tracking, but the real daily pain point is deciding what to make. Solving it has to show that each meal actually matters, turning a passive tracking tool into something a parent reaches for before eating happens, not just to log it after.
Assumptions
-
A short onboarding collects household size, dietary restrictions and allergies, picky-eater flags, and preferred breakfast, lunch, and dinner times
-
Parents will accept a few minutes of setup if daily decisions get faster afterward
-
Time is a bigger constraint than the cooking skill, so recipes must be quick and practical
-
“Healthy” follows simple, transparent guidelines (balanced macros, a calorie range)
-
Users can add what’s on hand manually; there's also a pantry sync at launch
-
Parents are the primary user
The Feature
Meal Picker
One card that knows which meal you need, and when
Entry point: A single home card that moves through three states, driven by the user’s own meal times:
Active: once the window opens, it becomes the highest-contrast element on screen and asks the real question (“What’s for lunch?”)
Resolved: once logged, it compresses into a calm confirmation with a quiet “Change meal” link
Only one prompt is active at a time, so the home screen doesn’t feel like a to-do list.
Input: Three quick questions: what’s on hand, how much time you have, and who’s eating. Quick-add chips make listing ingredients take seconds, not a form.
Results: Three options, not an endless list. That’s enough for a real choice without bringing back the paralysis the feature exists to remove, plus an option to refresh for new options.
Detail and commit: The full recipe has adjustable servings, ingredients, and step-by-step directions, ending in a single completion action. A drawer keeps the recipe accessible afterward.
Key interaction: Completing a meal logs it automatically into that day’s calorie and macro totals. Deciding and tracking happen as one action.
The design
Calm, warm, and food-forward, not another clinical tracker
The visual system
The interface uses a warm off-white canvas with white, softly rounded cards, so content separates cleanly without heavy borders. Green is used for every primary action. A dark olive appears on ingredient chips and the active nav item, and a soft yellow marks selected states, progress bars, and recipe notes. Food photography carries most of the visual interest, so the surrounding interface stays simple and the recipes remain the focus.
Home active state
The first thing on Home is the date and a greeting, followed by a weekly tracker. Completed days show a filled check, and today shows a dashed circle, so a day’s status is clear at a glance without a label.
The meal card is the main piece. It sits at the top as a white card with a clock icon and the time, the question “What’s for dinner tonight?” (Which will change depending of the time of day) with a primary action underneath, for an obvious next step.
Home selected state
Once the user selects a meal, the question is replaced with their meal choice. The button changes from “Get tonight’s pick” to “Pick another meal.” In case the user, changed their mind and want to cook something different. The card confirms the user's decision without implying that dinner is logged.
Input screen
The input screen has three short sections, and each uses a different control for its kind of answer.
-
What do you have? shows ingredients as removable dark chips, with a green “+ Add” link that opens the grocery sheet. If the user has their pantry list set up, then once they are on this screen, their pantry items will appear within this section. User can remove if they no longer have that item, or add more if they need to.
-
How much time do you have? uses large single-select rows (15, 30, or 45+ minutes), because exactly one answer applies. Selected row will have a darker outline.
-
Anyone to consider? uses checkboxes, since more than one can apply (picky eater and allergies, for example). The selected rows use the same styling, for consistency across the screen.
Add groceries
This is the optional sheet behind “+ Add.” A search bar sits at the top, with three shortcuts underneath: Barcode scan, Grocery scan, and Quick Add. Below that, “Recently logged” lists of foods, with a plus button to add onto the pantry list. The recent list matters because most people re-buy the same foods, so a returning user can add several items in a few taps instead of searching each time.
Top 3 results
Three full-width recipe cards, each led by a large photo. Under each photo sits the name, time, ingredient count, and difficulty, then a short description. These three options are the ones users needs to decide for their meal. so I kept them visible without opening anything.
A checkbox appears on the top corner of every photo, for the user to choose. The selected card gets a darker outline. The bottom of the screen contains “I’ll cook this” button which is the primary action. The "Show different options” sits below as a quiet text link with a refresh icon. If users don't like the current three options, then they will tap this secondary action for new meal options.
Recipe drawer
Tapping a card opens a bottom drawer so users can check a recipe without losing their place in the three results. It has a photo header with a close button, the title and details, a short description, and a servings stepper (which can be adjusted). The ingredients and directions sit in collapsible sections, so the drawer starts short and expands only if users want more. A yellow note container carries the cooking tips, and “I’ll cook this” is repeated at the bottom so they can commit right from the preview.
Recipe detail
The full recipe opens on a large photo, then the title, details, and description. A servings stepper sits above the ingredient list, which user can reduce or increase depending how much serving is needed, this will update the contents of the ingredient list. The yellow note container holds the tips that prevent common mistakes. A single green “Dinner complete” button stays at the bottom.
Home resolved state
Tapping “Dinner complete” returns to Home, and the card shrinks into a calm confirmation. The clock is gone because they were prompts, and the question has been answered. The numbers below update automatically: the calorie count, the macros, and the dinner row in the meal list show the recipe and its calories. Users will not have to log manually, which is the main point of the feature.
