TodayUser1 / 6
Diet Plans
A plan a dietitian actually wrote, a log the client can keep in ten seconds, and an honest picture of adherence for the conversation between them.
- From
- $749
- Function
- 23
- User types
- 2
- Platform
- iOS & Android
React Native · TypeScript · PostgreSQL · Expo
Inside the app
What it does out of the box
23 connected functions on one schema across 2 user types. Everything below is in the template before a line of customisation.
Today
The client opens on the next meal and how the week is going. Adherence is shown as a number, not a streak with a flame on it.
Plan
The plan as prescribed, with portions and the swaps the dietitian explicitly allowed. A swap outside that list is recorded as off-plan rather than silently accepted.
Log
Ten seconds to log a meal, including the ones that were not on the plan. A log people abandon by Wednesday is worth nothing to either side.
Clients
Every client with adherence, last review and a flag on whoever has stopped logging, which is the earliest signal that a plan is not working.
Plans
Templates you build once and prescribe many times, with the clients on each and a record of when it last changed.
Review
A queue ordered by who is actually due, with the adherence and notes needed to make the call, so a review is preparation rather than improvisation.
User types
Two apps, one system.
The client is outside your practice and the dietitian is inside it. The split matters more here than in most apps, because one side is writing a prescription and the other is following it.
User, the client
Sees the plan their dietitian wrote, logs what they actually ate, and can say when something did not work. Their record is theirs alone.
- The plan as prescribed, day by day
- Log a meal in seconds, including off-plan
- Swap within the options your dietitian allowed
- Flag a food that disagreed with you
- Message your dietitian between reviews
Dietician, the practitioner
Writes plans, reviews adherence and adjusts. Sees the client list, who is drifting, and the notes behind every change, with a record of who changed what.
- Build a plan from your own templates
- Set allowed swaps rather than a fixed menu
- Adherence by client, not just weight
- Review queue ordered by who needs it
- Every plan change is dated and attributed
The limits
What this is not.
The same list we give for every app in the catalogue, because the fastest way to a bad project is a promise made in a meeting that nobody wrote down.
It is not clinical or dietary advice
The plan is what your registered practitioner wrote. Nothing here generates, suggests or validates a plan, and the app never presents itself as a substitute for a qualified dietitian.
It does not diagnose, and it does not calculate for you
No algorithm sets targets. Numbers come from the practitioner, and the app records them.
We do not certify your regulatory compliance
Health data rules where you practise remain yours to satisfy. We build to the controls you specify and host in your own cloud, which is usually the harder half.
We do not process payments
Consultation fees are recorded and chased; money moves through your own provider.
Questions
Questions, answered plainly.
If yours is not here, ask it on the call rather than guessing from a pricing page.
Where does client health data live?
In your own cloud account, in the region you choose. For anything health-adjacent that is the main structural argument for owning rather than renting: residency and retention are yours to set rather than somebody else’s roadmap.
Does it suggest plans or calculate macros?
No, deliberately. Everything prescriptive comes from the practitioner. An app that generates a plan is making a clinical decision, and this one does not.
Do I get the source code?
Yes. The repository transfers on delivery, both apps, API, schema, migrations and deployment configuration. No licence key, nothing that calls home.
How does it handle a client eating off-plan?
It records it as off-plan without editorialising. Hiding or punishing off-plan meals is the fastest way to make a food log dishonest, and a dishonest log is useless at review.
Can it link to the Personal Trainer App?
In a fitted build, yes, one client record across training and nutrition is a common request from practices that do both. They ship separately because most buyers need one.
Can it be changed to match our practice?
That is the usual route. A fitted build sets up your plan structure, review intervals, swap rules, consent wording, branding and up to two integrations, typically in one to three weeks.
Related
More on-demand builds.
Click through it before you spend anything.
The preview is the real app with sample data. Open it and judge the software rather than the pitch.