Serving two distinct user types on web and mobile without any prior design foundation.

The client app opens on finding a nutritionist, which is the first step of the whole flow.
NutraHive provides a nutrition service tailored for working professionals in metro cities. A client selects a certified nutritionist who crafts a personalized diet plan week by week, while meals are prepared at NutraHive's own cafe.
No design assets existed when I joined the project, requiring me to create every screen from the ground up.
I designed both the client application and the nutritionist management portal across web and mobile platforms. Additionally, I created the custom watercolor illustration style used in the product.
I maintained full ownership of the UX, UI, and visual illustration style while collaborating directly with engineering during implementation.
Whenever interactive flows broke during development, I resolved them directly alongside the engineering team.
The onboarding screens feature original watercolor illustrations, finalized after exploring multiple creative directions.
In the absence of existing designs or historical user data, my responsibility focused heavily on making strategic proactive choices.
These represent four key areas where choosing the obvious design path would have created operational issues later.
Clients select from four plan durations spanning one, two, four, or eight weeks. Single meals cost ₹200, with longer plans offering progressively larger discounts.
Standard pricing displays present total upfront costs for each duration. However, because overall costs scale with duration, users struggle to evaluate relative value across options.

₹14,280
Four week planThis option shows the full cost for all the meals.

₹3,780/week
Two week planThis option shows the cost for one week of meals.
I formatted every plan using a normalized weekly rate to make the most cost-effective option immediately obvious.
The eight week plan costs ₹3,528 a week and the two week plan costs ₹3,780 a week, so the better deal is clear. As totals, a client would have to compare ₹28,224 with ₹7,560. That comparison is much harder to judge.
The four-week plan allows split payment into two installments, with the second payment due after two weeks.
Simply splitting total plan cost in half created an exploit where a client could pay the first installment, consume meals for two weeks, and leave. Doing so resulted in paying ₹420 less than the standard two-week plan price.
A client can pay the first part, eat for two weeks and leave. The two week plan costs ₹7,560, so that client pays ₹420 less for the same two weeks.
I adjusted the initial installment to match the standalone cost of a two-week plan so that leaving early offers no financial shortcut.
The second installment is reduced accordingly to maintain the overall total, and this structural rule is applied identically to the eight-week plan.

At checkout, the client sees ₹7,560 due today and ₹6,720 due later.
Nutritionists require client details including height, weight, activity levels, goals, and health conditions to formulate diet plans. The key challenge involved determining the optimal collection point.
Asking for this data during initial account creation forces new users through two comprehensive forms before viewing any food options.
A new client fills in two forms before seeing a single meal.
A new client can browse and order first. The body details come in only when they book a nutritionist.
I postponed these input fields until the client actively books a nutritionist, aligning data collection with the exact moment it becomes necessary.
Prior to booking, clients retain complete freedom to explore the platform and order meals. The interface surfaces popular items alongside past purchase history, while also prompting for body metrics after a client completes two or three orders.

Sign up asks for an account and nothing else.

The body details form asks for height, weight, activity level, goals and health concerns.

Booking a nutritionist is the one place these details become required. The continue button stays off until they are filled.
Nutritionists construct plans through a four-step process: selecting the client, choosing the plan duration, assigning specific meals, and adding final notes. Because chosen plans dictate which meal templates load, step order remains critical.
I designed the interface to reveal steps progressively because the logical order was already established by system dependencies.
Nothing opens until a nutritionist chooses a plan.
Meal template selection and client note fields remain locked until a plan is selected, while the submission trigger stays disabled until at least one meal is assigned to the weekly schedule.
I implemented subtle structural safeguards across the product to prevent user error before it impacts clients or nutritionists.

Plan submission includes a 10-second undo window that allows nutritionists to catch and correct mistakes before updates reach the client.

Nutritionists can mark personal unavailability directly, while previously booked time slots automatically lock with contextual explanatory notes.

Nutritional metrics recalculate dynamically as clients add custom toppings and add-ons.

Credits from cancelled meals apply directly toward checkout balances, reducing total payment to zero when credits cover the full amount.
Clients can track their order on its way from the cafe.

The client sees this screen once an order is placed.
Because NutraHive remains in pre-launch development, quantitative metrics are not yet available.
Following release, my primary priority will focus on tracking the percentage of new clients who place meal orders prior to completing their nutrition profiles.
This key metric will validate whether relocating profile questions outside the primary registration flow worked.
Designing a whole product alone taught me to look beyond the screen I was working on.
I learned that a designer has to check the numbers behind a screen, not only the layout. The pricing loophole only showed up once I worked out how the plans added up.
I also learned to design the client side and the nutritionist side together. A choice on one side often changed the other. The body details a client fills in are a good example, because they exist for the nutritionist.