Turning a nutrition app into a platform two people share.

When I came in, NutriFlow did one thing: generate a diet plan and hand it over. No nutritionist, no back-and-forth, no room to adjust once your body or your week changed. The interface was dated, and the everyday flows, like logging a meal or checking your day, took more taps than they should. People signed up, tried it for a week, and quietly stopped.

The brief looked like a redesign, but the moment you add a nutritionist it becomes a different product. A client wants their day sorted in a few taps. A practitioner wants to see how a week is really going and act on it. Serve one well and you can easily bury the other. The whole challenge was to make both feel light, on top of a lot more data than the old app ever carried.

The decision that shaped everything else: the client app and the nutritionist dashboard aren't two products that talk to each other. They're two ends of one loop. Right after signup, a client either goes app-guided or enters an 8-character code to link to a nutritionist. From then on, the practitioner's assigned meals flow straight into the client's plan, and the client's logs and vitals flow back into the practitioner's view. One source of truth, no copy-paste, no email attachments.

The client app is built around one honest question, what do I do next, with logging kept to seconds and the health signals that matter close at hand. The same plan structure carries both app-guided and nutritionist-guided users, so the product never splits into two apps.

This is where most of the design work went. The dashboard is where a nutritionist finds a client, reads how their week is actually going, and adjusts the plan on the strength of it. I designed it so monitoring and editing live in the same place, because a practitioner who can see a problem but has to leave to fix it will simply stop looking.

A single, hard-to-use app became a connected platform where clients track real progress and nutritionists can act on it. These are the wins that mattered most.

Cards, charts, log components, plan modules, and metric widgets: one set of patterns carrying across mobile and web, so the two sides feel like one product. The tone stays quiet and health-focused, motion earns its place, and the system is set up to grow toward Apple's newer iOS direction when the team is ready.

What I take from this one: product design pulls the most weight when it changes the product model, not just the surface. The app that existed was a closed loop: sign up, the algorithm decides, done. Redrawing those screens would have made a nicer version of the same dead end.

Adding a second user and a shared source of truth is what actually moved it. A client can now grow with the product, alone or alongside a real nutritionist. The rebuilt app, the dashboard, and one shared system gave the team something that holds up today and has honest room to grow into next.