RiteFood
The problem
Diet apps are not abandoned because logging is hard. They are abandoned because the second week has nothing new to say — the numbers go in and nothing comes back out.
The solution
The macro ring and calories-remaining figure sit at the top of the home screen so every log immediately changes something visible. Products carry prices and health context, so the app is useful at the moment of buying, not only after eating.
The result
Live on Google Play with a 5.0★ rating across 24 reviews.
01
Overview
RiteFood is a personal diet assistant: a macro and calorie profile, meal logging across breakfast, lunch, snacks and dinner, an exercise diary and timer, health goals, curated product recommendations, and a community feed.
02
Context
This category is crowded and the differentiator is not features — it is whether the app is still open on day fifteen. Retention is a design problem long before it is a marketing one.
03
Challenge
Every logging app asks for effort up front and pays it back later. Shorten that gap or people leave. And the payback has to be visible on the same screen as the effort, not buried in a weekly summary.
04
Approach
The macro ring and calories-remaining figure are the first thing on the home screen, so a logged meal changes something you can see immediately. The regimen line gives the day a single instruction rather than a dashboard to interpret. Product recommendations carry price alongside nutrition, which moves the app into the moment of purchase — the point where a diet is actually decided.
05
What I did
- 01UX flows: diet profile, meal logging, exercise diary, recommendations
- 02Interface design across the app's core screens
- 03Data-visualisation treatment for macros and daily progress
- 04Store listing design — screenshots, feature graphic and listing narrative
- 05Retention-oriented patterns: streaks, daily regimen, visible feedback
Live
See it working.
This project is live. The best version of any case study is the product itself.
Next project
Ecstatic Explorers