PL. 022026product · interface · system
A medication record someone can read in one glance
An Android adherence app rebuilt onto a single design system, so every screen states the same things in the same voice.
Addressed by name, not by accountOne score, stated before it is explainedAdherence is the first row, alwaysUntracked reads as untracked, never as zeroThe next dose, and nothing after itFive destinations — the whole app- Addressed by name, not by account
- One score, stated before it is explained
- Adherence is the first row, always
- Untracked reads as untracked, never as zero
- The next dose, and nothing after it
- Five destinations — the whole app
Constraint
Adherence apps are opened in the ninety seconds around a dose, often by a carer rather than the patient, often one-handed. The screen has to answer "what is due, did it happen, is anything wrong" without being read. The app had grown a second visual vocabulary as it went, so the same question was answered differently on different screens.
Decision
We built the design system first and migrated every screen onto it as a separate track from feature work, then deleted the compatibility alias layer outright rather than leaving it to rot (ADR-052). The home surface states one score and one next action; everything else is a tab away.
Consequence
Every screen now renders from one system, the pre-v2.4 alias layer is gone, and the design-fault register closed at zero open rows. The migration is held at verification rather than complete, because the design-authority visual review has not happened yet.