The device guides you at the stove. The app handles everything around it: setting up, choosing what to cook, keeping an eye on the cook from another room, and tracking what you ate.
I can't disclose more here. To know more, reach out to me.Get in touch ↗
Timeline
Feb 2026 to present
Platform
iOS, Android
Role
Sole designer
Team
12 people
The app and the device, mid-cook
Overview
You can't read a recipe with wet hands, and you can't plan a week's meals from a screen above a hot pan. So Cravv is two things. Tara guides the cook at the stove. The app handles the rest: sign-up and dietary needs, browsing and saving recipes, grocery lists, customising a dish before you cook it, watching the cook from another room, and tracking what you ate.
I designed the app alongside the device, as the only designer on the team. This page is mostly about that last part: turning what someone cooked into a number they can trust.
The problem
People wanted to know whether what they cook is good for them.
In interviews, two questions came up together: what should I cook, and is it good for me? The device answers the first. The second needs a record of the dish, the person eating it, and what their body needs.
50+
interviews
259
survey responses
1
consulting nutritionist
The device
In the kitchen, at the pan
Guides the cook, one step at a timeWhile
Watches the heatWhile
Counts whistles and watches for boil-oversWhile
Shows the dish's score at the endAfter
Shows today's score when idleAfter
Anything that needs reading, choosing or remembering stays off the device.
The app
Everything around it
Sign-up, preferences and requirementsBefore
Browse and save recipesBefore
Build grocery listsBefore
Customise a dishBefore
Live view of the cookWhileAway
Reminders when you've left the kitchenAway
Track meals and daily scoresAfter
Log meals cooked elsewhereAfter
Which surface handles which moment. Filter by moment.
Process
The whole flow
Most of it happens on the phone. The device owns the middle: the cook itself.
On the phone
On the device
Setup
Before cooking
While cooking
After
Nothing on the device until you cook
mirrors the cook
1Sign up
2Set requirements
3Browse and save recipes
4Build a grocery list
5Customise the dish
8Live view and reminders
6Start by voice or by phone
7Guided cook
9Dish score
13Today's score, when idle
10Dish breakdown
12Daily score and trends
11Log a meal eaten out
Most of the flow happens on the phone. The device owns the middle: the cook itself.
Or hover over any step.
The flow across the phone and the device. Hover over any step.
Start from the person, not the dish
A score only means something against a target, and targets depend on who's eating, so sign-up comes first. Age range, gender and the most specific health condition pick one of 24 archetypes, with targets traced to ICMR-NIN 2020 guidelines.
Onboarding / About you
9:41
Step 2 of 367%
About you
This sets your daily health point targets.
Age range
13 to 1718 to 2425 to 3435 to 4445 to 5455 to 6465+
1
Gender
WomanManOther
Health condition
NoneDiabetesOther
If more than one applies, choose the most specific.
2
PreviousNext
The profile picks one archetype
Woman, 25 to 34
One of 24 archetypes: age range, gender and the most specific condition
The archetype sets targets for twelve slots
Slots 1 to 3
Macros
Same for everyone, targets differ
Protein
Carbs
Fat
Slots 4 to 6
Priority
Nutrients come from the archetype
Iron
Folate
Calcium
Slots 7 to 9
Secondary
Nutrients come from the archetype
Vitamin B12
Vitamin D
Fibre
Slots 10 to 12
Limits
Same for everyone, tightened by condition
Sugar
Sodium
Saturated fat
Shaded slots change with the profile1Age range and gender narrow the archetype2One condition, the most specific, finishes it
Height and weight feed one BMI multiplier, using Indian cutoffs. It's the only place a person's details touch the formula itself.
The twelve slots never change. The targets do.
Switch the profile. The twelve slots stay put and the targets move.
Design
During the cook
The cook, from anywhere in the house
The phone mirrors the step, the timer, the burner and the camera. It was built as a fallback for when the device drops. In testing, people used it to check on a child, an ageing parent or household help from another room.
On the device
What the cook sees at the pan
Cook / Live
9:41
Dal tadka
Ongoing session
Step 1 of 617%
1
Cook the dal
Guide
Pressure cook the dal
Ingredients (2)
Toor dal (1 cup), Water (3 cups)
Whistles
1 of 3
2
Flame
High
Estimated
12–15 min
Elapsed
0:03
3
PreviousNext
Only on the phone
1
The step
Where you are in the recipe, and the one instruction to follow now, same as the device.
2
Whistles or heat
The count for a pressure cooker, or the temperature against its target.
3
Flame and time
Burner level, the step's estimate, and how long it's been going.
The same moment on the device and on the phone. Count a whistle to see the reminder.
After the cook
One dish, one number
The device shows the score. The app shows the twelve slots behind it, with a limit turning red when the dish goes over. Switch who's eating and only the targets move.
On the device
One number, at the end of the cook
Cook / Dish score
9:41
Dal tadka
Cooked with Cravv
For a woman, 25 to 34
This dish
Health points
14
1
Breakdown
Macros
Protein82%
Carbs64%
Fat71%
Priority
Iron48%
Folate92%
Calcium35%
Secondary
Vitamin B1222%
Vitamin D10%
Fibre76%
Limits
Sugar24%
Sodium68%
Saturated fat106%
3
2
On the phone
1
The score
The device shows this number and nothing else.
2
Twelve slots
Four groups of three, in the same order for everyone.
3
Limits
Grey until the dish goes over, then red.
Same dish, same formula. Only the targets change.
One dish, scored for two people.
The day adds up
Dish scores feed a daily score, and the app shows which slots are still short. Meals cooked elsewhere go in with a photo or a line of text, and the estimate stays editable, because people stop logging when a wrong number can't be fixed.
On the device
Today's running score, when idle
Profile / Health points
9:41
Health points
Daily
Health points
18/ 46
Weekly
Health points
100/ 322
Longest: 28 days
Day streak
12
1
Health point goal
46 health points
Daily · Recommended: 50 HP
46 HP2
Weekly HP trend+15%
DailyWeeklyMonthly
3
On the phone
1
Daily and weekly
Dish scores and logged meals add up to today's points, against the daily goal.
2
The goal
Recommended from the profile, and editable.
3
The trend
Actual points against the target, day by day.
The phone and the device update together.
Log a meal eaten out and watch the day update.
Impact
Live on both stores. Installs aren't tracked yet, so these numbers describe the system, not adoption.
12
nutrient slots
24
archetypes
23
nutrients checked per dish
5
API contracts
I designed the scoring model and wrote its engineering spec: schemas, formulas, five API contracts, four test cases. Before it shipped I built a small tool that returns all 23 nutrients for any dish against the Indian RDA, so I could check the maths myself.
Next phase
Family mode is designed and hasn't shipped. One device feeds a household: servings per person in quarter steps, a flag when a dish conflicts with someone's condition, guests without full sign-up, and an end-of-day nudge for anyone who wasn't logged.
Reflection
The app taught me that the most important design decision can be the least visible one. Nobody sees the scoring model, but it decides whether a number feels fair. Keeping one formula and moving the personalisation into the targets is what lets the app explain a score when someone asks why theirs changed.
It also taught me to design two surfaces as one product. Deciding what the device should never show did more for the app than any single screen, because it told me exactly what the app had to do well.