BIOS APp · 2022
I turned a disconnected wearable and app into one product.
— Took over a system with no design foundation. Built the frameworks first, then delivered a UI that outperformed market leaders within FDA constraints.
Role
UX/UI Lead
TEAM
Team of 3
stage
Series B
duration
6 months
What I did here
my focus
Ecosystem audit
Mapped touchpoints & integrations — before touching any UI
Onboarding & device setup
Designed the physical-to-digital bridge for first-time sensor insertion and pairing
Friendlier UI within FDA constraints
Delivered a friendlier, clearer interface than Dexcom and Freestyle Libre — with the same structural requirements
the outcome
A cohesive wearable experience built from a system that didn't exist before.
The situation
I inherited a wearable health product where the device and the app had never been designed as one system.
GraphWear had a clinically validated CGM device and a mobile app. They were connected by Bluetooth and nothing else. No design system. No interaction logic between hardware and software. No shared visual language.
UI, UX, and brand existed as three separate layers that had never been reconciled.
GW's early stage BIOS app
GW's CGM device
The call
Before I touched a single screen, I built the scaffolding the screens were supposed to hang on.
The obvious move was to start redesigning UI. I didn't.
I drafted every framework, flow, and map first — the full ecosystem of how the wearable and the app were supposed to behave together, how users would move through setup, how the brand would show up across hardware and software. All of it on paper before any pixels.
This wasn't research-for-research's-sake. It was a refusal to execute on one layer until I knew what the other two demanded of it.
Then I built the revamp architect with 3 distinctive layers interconnected from each other.
Layer 1
UX Scaffolding
Goal:
Connecting the device and app into a seamless experience
Layer 2
Brand Framework
Goal:
Create a unified design system that's scalable.
Layer 3
Final UI Finish
Goal:
Evolving the brand to feel more human, less clinical
layer 1 — the experience architecture
Onboarding and the wearable-app relationship had to be designed as systems, not screens.
The hardest moment in any wearable product is the first one — putting a medical sensor on your body. The existing flow treated it as a software task. It wasn't. It was a physical-to-digital handoff that had no framework guiding it.
I mapped the full setup flow end-to-end, then the ongoing interaction logic between the device and the app — what the wearable communicates, when, and how the app responds. This became the backbone everything else attached to.
Initialization flow mapped to user flow chart
layer 2 — the identity system
The brand had to live on the device, in the app, and in the space between them.
I ran competitive analysis against Dexcom and Freestyle Libre — not for trend-matching, but to find the positioning gap BIOS could actually own. The existing brand read as clinical where it should have felt human.
I built the visual identity around the device's physical form — so the brand didn't start in the app and try to reach the hardware. It started with the object on your arm and worked outward.
layer 3 — the interface, built last
Communicate clarity and emotional value through UI under regulation constraints.
Dexcom, Freestyle Libre, and BIOS all share the same bones — glucose reading, trend, chart. FDA Class II compliance dictates that and that's the constraints I havce to work within.
So I focused on the margin: how the interface talks to you within those constraints. A natural language status line — "Your glucose is steady" — that gives reassurance without crossing into medical guidance. A vibrant palette against the clinical whites competitors default to. Navigation that signals depth without overwhelm.
Same structure. More value. That was the design solution.
Dexcom G6
Freestyle Libre
Our Design
The result
A wearable ecosystem that behaved as one product — because I built the system before the screens.
Dashboard, alerts, TIR, and log each serve a different moment — monitoring, reacting, understanding, recording. I designed them to feel like one conversation with the user, not four separate features. Same visual logic, same tone, same warmth. The system I built upstream finally had a face.
