Overview
One home for every wearable’s data.
Serious athletes own several devices, each strong at something different, and each platform shows the same run or night’s sleep its own way, at its own depth. obseed is the platform that aggregates every device’s performance data in one place, so it can be read in full detail and compared over time.
On top of that, the obseed algorithm reduces misinterpretation. The brief itself was one line, for a early-stage team and an open brief, across a dashboard, body-composition statistics, the activity detail and a calendar.
The problem
Scattered data, and some of it wrong.
We started by interviewing triathletes, and turned what they said into the brief. Three things pulled at once.
Split across devices
Every device is best at something different. Oura for sleep, Garmin for activities, another solid everywhere but great at nothing, and each platform shows the same data its own way, at its own depth.
Misread on the device
The numbers can mislead. A device sees one uphill mile and reports that spike as the heart rate for the whole run. Read straight, the data tells the wrong story.
An open brief
One line, and a young team. The mandate was open enough to sprawl into an endless build, so the first job was deciding what the product actually needed to be.
The approach
Layered depth, not a dumbed-down summary.
One number at a glance, three numbers with effort, the full multi-axis correlation on click. The same vocabulary across every surface, so a click down reads as a depth change, not a navigation change. Three layers, one screen.
Progressive disclosure: one number at a glance, three with effort, everything for those who want it.
And clean the data before showing it.
A device averages the spike from one uphill mile across the whole run. The obseed algorithm attributes it to the section, so the number means what the athlete thinks it means.
Device reads
one climb skews the lot
obseed reads
heart rate by section, not by workout
My contribution
From open brief to a system.
Interviewed the athletes
Ran qualitative interviews with triathletes and turned what they said into the brief, so every surface traces to a real need rather than a guess.
Designed the four surfaces
Dashboard, statistics, activity and charts, plus the drill-down that ties them, all in one vocabulary so a click down reads as a depth change, not a navigation change.
Designed the company website
Designed obseed’s public site in the same visual language as the product, one voice from landing page to dashboard.
Shipped it with engineering
Partnered directly with the engineer on the live product: recurring UX pain points became shipped fixes through a direct direction-to-code loop, no formal handoff.
The system
One vocabulary, four surfaces.
The same tokens, spacing and components compose every screen of the app. These are the live values, pulled straight from the prototype below.
Foundations
Colour, by role
#16171B
#F9C536
#EF7A7A
#191B20
#6A707B
#9DA4AF
#EDEEF1
#F7F8FA
#FFFFFF
Sport palette, Kalender
#6E93B8
#6E9B79
#C97D72
#C2954A
#8A7FB0
#5C9A95
Spacing & radius
Typography, Inter
Layout grid
A fixed 240px dark sidebar beside a fluid 12-column content area, 20px gutter. Vital cards span 4; the Health Index and AI read span the full 12. The same grid on every surface.
Components
The rebuild
The dashboard, depth on demand.
The daily check-in: a Health Index, three vital signs, an AI-generated read on the trend, the full series a click away. One of four surfaces, Dashboard, Statistik, Aktivität, Charts, all sharing the same vocabulary.
The athlete logs in to the dashboard with every surface one tap away, picks Aktivitäten, scans the list, and opens a single session in full, the route, the splits and the multi-axis read.
Tap a vital to drill into its full series, depth on demand.
Impact
What it added up to.
Shipped
The analytics surface shipped
Built from the interviews that set the brief, the four surfaces and their layered drill-down shipped to the team.
Shipped with engineering
Pain points fixed in the live product
Design direction turned straight into shipped code with the engineer, recurring UX pain points resolved in the running product.
Coherent system
Four surfaces, one product
Dashboard, statistics, activity and charts in one vocabulary, so moving between them reads as a depth change, not a different app.
Reflection
What it taught.
Design isn’t finished at handoff. The fastest path from a UX problem to a shipped fix was working straight with the engineer, direction in words and the change in code, with no round-trip in between.
An open brief needs a user, not a guess. The mandate was one line; the athlete interviews are what turned it into surfaces worth building.