Jaimin Let’s talk
Back to work

Onahn Michelle / H&N Research

Health tracking,
brought together.

Meals, vitals, and a voice assistant in one iOS app. I was the sole product designer, from the first structure to the App Store.

See the shipped app
Onahn Michelle screens showing the dashboard, meals, health metrics, and voice assistant
One product, from daily check-in to conversation.
My role
Sole product designer
My scope
Research, structure, system, UI
Collaborators
3 engineers, a PM, a copywriter
Outcome
Shipped with paying customers

A daily check-in.
Not another chore.

Bring meal logging, health metrics, and food scanning into one useful routine.

Who I designed for

People managing a kidney condition and health-conscious professionals.

What I owned

Research, information architecture, and the interface, with a shared system for engineering to build on.

A decision that changed the scope

Knowing what
to leave out.

  1. The idea

    Edit scanned ingredients to match a customized meal.

  2. The constraint

    The team couldn’t technically support full ingredient editing.

  3. My call

    Remove editing and design around what we could build.

The tradeoff: less flexibility for customized meals.

Three screens.
Three design decisions.

Explore the actual interface and the choices behind it.

Daily dashboard with progress, health cards, insights, and a voice entry point

Daily dashboard

Start with today.

Daily progress, recent metrics, and insights share one starting point. The dashboard brings the product’s different jobs into the same view.

The interface choice
Repeatable cards separate information into readable groups. Persistent navigation keeps meals and health within reach.
The balance to get right
A useful overview can become crowded. Hierarchy has to make the first action clear without treating every metric as equally urgent.

The work before the pixels.

A shared map of the product’s scope, before design and engineering moved into screens.

Early information architecture mapping onboarding, home, meals, health, settings, and shared states
Early information architecture. A working scope artifact, not the final app navigation.Inspect full size

The main path was only part of it.

The map also records microphone permissions, scan retries, empty states, and failed payments. Those states belong in the design conversation before implementation.

How research informed the scope

Research included interviews and two personas, with outreach through Reddit and LinkedIn. Those activities helped frame who the product was for: people managing a kidney condition and health-conscious professionals.

One system.
Room to keep building.

Shared tokens, reusable components, and light and dark themes. A common language for design and engineering, with fewer decisions to repeat.

Explore the design system
Onahn Michelle design-system components and interface examples
The shared foundation behind the product.

The outcome

Out of Figma.
Into people’s hands.

A shipped iOS app with paying customers. My contribution spanned the structure, design system, and interface.

View on the App Store

What I’m taking forward

Check feasibility while the idea is still cheap.

Bring engineering into the conversation before a feature becomes an expectation.

Give new screens a foundation.

Shared tokens made consistency a practical part of the work.

What I’d investigate next

Where does logging feel difficult? What brings people back? How clearly do they understand the insights? These are next questions, not measured outcomes.

Want the story
behind a decision?

Let’s talk about it

I’m happy to get into the details. Fair warning: I care about the small ones.