In productionMidnight Health2026–Present

Midnight Health — One Product System Across Contexts

A secure daily health workflow designed as one system across iOS, desktop, tablet, and mobile web.

Outcome and status

One focused daily plan replaces the work of reconciling disconnected health signals across several products.

Public product. The diagrams omit personal health data and account details.

Context and user problem

Health-conscious users already generate useful information through Apple Health, wearables, and check-ins. The hard part is not collecting more data; it is turning what already exists into a small, understandable decision for today.

My role and collaborators

Role: Founder, product design engineer
Collaborators: Product strategy, Interface design, Engineering
Platforms: iOS, Desktop web, Tablet, Mobile web
Timeframe: 2026–Present

I founded the product and own the system end to end: product framing, interaction model, visual system, cross-platform implementation, privacy posture, and the feedback loop between shipped software and the next design decision.

Constraints

01
The same workflow has to remain coherent across native and browser contexts without forcing every surface into the same layout.
02
Health information requires clear consent, conservative defaults, and interfaces that never imply medical certainty.
03
The product must reduce daily effort rather than introduce another dashboard users are expected to maintain.

Key decisions and rejected alternatives

Design one decision, not another dashboard

The primary surface centers the next useful action and keeps supporting history available without making it the opening task.

Rejected: A metrics-first home screen that exposed everything the system could measure at once.

Adapt the composition, preserve the model

Navigation and density change by context while names, states, and the daily workflow remain consistent.

Rejected: Scaling the desktop interface down for mobile or treating native iOS as a wrapper around the web product.

Make trust visible in ordinary moments

Permissions, data provenance, and human-readable explanations live beside the actions they affect.

Rejected: A single privacy explanation during onboarding that users would have to remember later.

Artifacts and annotated flows

These diagrams document the real product logic while respecting the publication limits described above.

iOSTodayCheck-in

Mobile webTodayHistory

TabletPlanSignals

DesktopPlanTrends

One workflow, four contextsNavigation and density adapt to the device; the product model stays recognizable.

TodayOne useful planDo less, understand why.

Review what changed

The day resolves to one planExisting signals are reduced to a short plan with supporting context available on demand.

SourcesApple HealthDaily check-in

Explicit consentSource and scope stay visible

Limited outputDaily planPersonal history

Trust is part of the workflowConsent, source, and scope are shown where the user makes a decision.

1 / 3

Shipped result and verified outcomes

Cross-platform by design

The product now has a shared interaction model that can be expressed natively on iOS and responsively on the web.

Less daily administration

The interface is organized around the next useful action rather than the maintenance of a health-data archive.

A system that can keep learning

Product language, states, and components are shared closely enough that findings on one surface improve the others.

Reflection and what changed

The durable design work was not a single screen. It was deciding what must remain stable across contexts and what should be allowed to change. That distinction now guides both the product system and the codebase.