A Dietitian App That Shows You a Client Is Slipping Before They Quit

The client is committed in week one, stops sending WhatsApp photos in week two, and never shows up for the week-three check-in. Meanwhile you are leafing through three paper measurement logs, trying to remember who was where. A dietitian app turns that silent drop-off into a visible signal while there is still time to act on it.

How many separate apps does this need?

  • 01

    Client Mobile App (iOS + Android)

    Daily meal plan, meal check-offs and a photo food diary, water and weigh-in entry, reminders tied to each meal time, measurement charts, appointment booking and direct messaging with the dietitian.

  • 02

    Dietitian Mobile App

    Client list ranked by adherence risk, meal-plan building from the food database, anthropometric measurement entry, quick feedback on incoming meal photos, and the day's appointment calendar.

  • 03

    Admin Panel (Web)

    Client files and intake-history archive, package and remaining-session tracking, payment collection with e-Arşiv (Turkey's mandatory electronic invoice archive) document flow, client assignment across a multi-dietitian clinic, and management of KVKK (Turkey's data protection law, aligned with GDPR) disclosure and consent records.

What the app includes

  • Portion entry in household measures: ladle, tablespoon, tea glass
  • Meal swap that keeps the same macros (exchange list logic)
  • Voice or short text feedback on a submitted meal photo
  • Waist, hip and neck circumference plus bioimpedance device results
  • Fixed weigh-in day with a fasted morning weighing reminder
  • Flagging weight swings with water-retention and menstrual-cycle notes
  • Plan warning when a meal hits an allergy or disliked-food entry
  • Alternate meal schedules for shift work, fasting and travel
  • Uploading lab results and filing them in the client record by date
  • Pre-visit progress summary compared to the previous measurement
  • Growth percentile curve tracking for child clients
  • Separate calorie targets for training days and rest days

State of the sector

Nutrition consulting is no longer confined to a single city; a client can find and choose a dietitian who works over video through social media. That is where the competitive pressure comes from. A practice running follow-ups on WhatsApp and Excel only learns what a client ate during the day at the next check-in appointment, while a colleague with an app sees the drop-off on day three and intervenes. The difference shows up not in a single session but in how many months the client stays. Loyalty in this field also grows with results: a client who watches their measurements change on a chart tells people about it, and new clients arrive by referral.

Metrics that matter here

  • Client retention length (which month they drop off) — Because falling adherence becomes an early signal, the dietitian intervenes before the client is fully gone, and follow-up periods get longer.
  • Food diary / meal check-off completion rate — The easier daily entry becomes, the more data accumulates; plans are then revised against actual intake rather than guesswork.
  • Check-in appointment no-show rate — Reminder notifications and one-tap rescheduling reduce wasted session hours and the revenue lost with them.
  • Package renewal rate — A client who sees progress with their own eyes on weight and waist-circumference charts is far more likely to buy a second package.

Common mistakes in this sector

  • Reducing the app to a PDF meal-plan distributor An app that sends plans but collects no feedback is just expensive email. Without data flowing back from the client - meal check-offs, weigh-ins and photos - there is no follow-up at all; the value sits precisely in that return flow.
  • Sending frequent, generic notifications A client who gets five reminders a day turns notifications off and then deletes the app. Notifications must be tied to that client's own meal times and actual behaviour; a “don't forget to drink water” message blasted to everyone at once does nothing.
  • Tracking progress by weight alone Weight fluctuates through the day and demoralises clients. If waist circumference, body fat percentage and measurement changes are not shown alongside it, progress stays invisible - and a client who cannot see progress usually quits in the second month.
  • Leaving package and session rules out of the software If cancellation, no-show and refund rules are not defined in code, every case gets argued over the phone. Remaining sessions, the 24-hour rule and forfeiture must be visible in the app; only then do disputes and lost revenue go down.

Regulation and compliance

A client's weight, medical history, lab results and body photos are special-category personal data under KVKK (Turkey's data protection law, aligned with GDPR); processing them requires explicit consent and additional security measures. The disclosure notice must be presented inside the app, consent records stored with timestamps, access logged, and a working flow provided for deletion requests. If you are subject to VERBİS (Turkey's registry of data controllers) registration, the app's processing activity falls within that scope too. On the payment side, self-employment receipts or invoices are issued through the GİB (Turkish Revenue Administration) e-Arşiv system, and the payment flow must be wired into that document process.

The real challenges in this sector

  • Food database and portion matching

    A client writes “a ladle of lentil soup”; the system expects grams. You need a portion dictionary built around Turkish home cooking (ladle, tablespoon, thin slice, tea glass), with every unit mapped to grams and macros. Packaged products need barcode scanning, and unmatched entries need a queue the dietitian approves. Without this, daily diary data is never comparable.

  • Producing genuinely personalised plans, not templates

    A plan is built around calorie targets, allergies, disliked foods, chronic conditions, fasting or shift patterns, and budget limits. The app needs exchange-list logic, so a meal can be swapped for an equivalent that keeps the same macros. An automatically generated plan that reaches the client without dietitian approval is a clinical liability.

  • Turning falling adherence into an early signal

    No meal check-offs for three days, weigh-ins stopped, messages unanswered: that trio predicts a drop-off. The system should compute an adherence score per client, flag it red in the panel, and offer a personal reminder in one tap. Notification dosage matters just as much; an app that fires five alerts a day gets muted, and then tracking goes completely blind.

  • Handling health data as a special category

    Weight, medical history, lab results and body photos are special-category personal data under KVKK. These fields need separate encryption, photos should open only through signed, time-limited links, and every dietitian's access to every file must be logged. When a client closes their account, there must be a real deletion or anonymisation flow behind it.

  • Tying video consultations to session entitlements

    Out-of-town clients need video calls; the real breaking point is matching payment to entitlement. Remaining sessions on an eight-session package, the 24-hour cancellation rule, forfeiture on no-shows and the refund path all need to be defined explicitly in code. The calendar must also prevent double-booking the same slot in a two-dietitian clinic.

Required integrations

  • Package payments, instalments and auto-renewal via iyzico or PayTR (Turkish payment providers)
  • e-Arşiv invoice and self-employment receipt integration compliant with GİB (Turkish Revenue Administration)
  • WebRTC-based video consultations (Jitsi or similar)
  • Barcode scanning to look up nutrition data for packaged products
  • Step, activity and weight data from Apple Health and Google Health Connect
  • Appointment reminders and win-back messages via WhatsApp Business API or SMS

Who this page is for

  • Solo dietitian whose clients are mostly online

    Phase 1 is enough: client app, diet plan, meal confirmation and measurement tracking. Barcode lookup, multi-user roles and video consultations wait until client volume justifies them.

  • Nutrition clinic with three or four dietitians

    Priority is client assignment, role separation and preventing double bookings. The package and session-credit rules engine plus the e-invoice document flow belong in the first release, with adherence scoring right after.

  • Nutrition unit inside a gym or health center

    Members are already inside, so retention matters more than acquisition. Separate training and rest day calorie targets, a shared client record with the membership system, and shared measurement history come first.

A phased plan that splits the budget

  1. 1

    Phase 1 — Core follow-up for a single dietitian 5-7 hafta

    Delivers the intake form, client record, diet plan sharing, meal confirmation, photo diary, weight and circumference charts, appointment calendar, and consent records under KVKK, Turkey's data protection law. At this point the practice can drop WhatsApp and spreadsheets entirely; later phases build on this data flow.

  2. 2

    Phase 2 — Food database, portion matching and adherence signals 4-6 hafta

    Adds a Turkish-cuisine portion dictionary, barcode lookup for packaged foods, an approval queue for unmatched entries, macro-equivalent meal swaps, and an adherence score. The order matters: clients must first log consistently, then the layer that interprets that data and flags drop-off can be built on top.

  3. 3

    Phase 3 — Clinic scale, video consultations and billing rules 4-5 hafta

    Brings multi-dietitian roles and client assignment, video consultations, a rules engine for packages and session credits, cancellation and forfeiture handling, payments tied to e-Arşiv (Turkey's electronic invoice archive), and health-device sync. These pay off only once client volume and team size grow, so they come last.

Typical scope and timeline

A client app, a dietitian app and a web panel; food database and portion matching, photo food diary, anthropometric measurement tracking, diet plans built on exchange-list logic, appointments with package and session-entitlement management, payments and the e-Arşiv document flow, KVKK consent and access logs, plus store assets and the release process are all included in scope.

Estimated timeline: 10-16 weeks

Off-the-shelf or custom build?

Topic Off-the-shelf Custom build
Portion dictionary and food database Ready-made platforms ship with a broad food database that works from day one; that is a genuine advantage, with no data entry to start. A custom build loads a base data set, then grows with your own portion measures and frequently used recipes; unmatched entries accumulate under your approval.
Getting your own method into the software A ready-made system imposes its own plan logic; your exchange-list approach, package steps and follow-up rhythm must fit the shape the platform accepts. A custom build follows your practice; separate tracking schemes for athletes, children and pregnant clients can live in the same app.
Per-client monthly subscription versus a one-time build With few clients a subscription is clearly cheaper; for a newly opened practice that wants to test the waters without upfront spend it is a sensible start. Subscription cost grows with client count and per-seat fees; with a one-time build the ongoing spend is limited to maintenance and store publishing.
Ownership of client records and measurement history The platform handles backups and security, taking that load off you; in return, measurement history and food logs usually export only as a flat table. In your own system the database is yours: you can host in Turkey and run access logs and deletion requests by your own rules under KVKK, Turkey's data protection law.

Sector glossary

Exchange list
A system that groups foods by macronutrient content so they can substitute for one another. A client swaps a disliked meal for an equivalent in the same group without breaking the calorie and macro balance.
24-hour dietary recall
Walking the client through everything eaten in the past day, with times and portions. It is the backbone of the first session; in an app it is captured as structured meal and portion fields rather than free text.
BIA (bioelectrical impedance analysis)
A device analysis of body fat, muscle mass and fluid balance, taken at follow-up visits. Logged into the record with a date, it shows progress even when the scale number has not moved.
Nutrition intake history (anamnesis)
The background taken at the first session: chronic conditions, medication and supplements, allergies, sleep and bowel habits, working hours. This record is the medical and legal basis of the plan.
Growth percentile
The curve showing where a child's height and weight sit among peers. In pediatric nutrition the goal is not weight loss but keeping the curve in an age-appropriate band, followed as a chart.

Frequently asked questions

Let us talk about your project

A free 30-minute call to scope it out, then an itemised quote within 48 hours.

Get a Free Quote

This page explains the problems an app must solve in this sector. We share references and comparable projects during the call.

Other sectors

All sectors →