Mobile UI2024
Rebuilding a regional transit app around one thumb
Four counties, six years of feature creep, and a home screen that answered every question except the one riders were actually asking.
Northbound TransitRead case study
01Selected work
Nine projects, and what actually changed
Every case study below describes the product we walked into, the decisions we made, the components we built, and what happened after release. Filter by the kind of work if you are looking for something specific.
Showing 9 of 9
Mobile UI2024
Savings goals that survive a bad month
A savings app that treated every missed deposit as a failure, told in red, to people who were already having a difficult month.
VesselRead case study
Mobile UI2023
Care team messaging built for a twelve-hour shift
Clinicians were using a consumer chat app because the compliant one took too long to say something urgent.
Halo HealthRead case study
Web UI2025
An invoicing dashboard that stops burying the money
Fourteen widgets, six charts, and no answer to the only question a finance lead opens the product to ask.
LedgerlineRead case study
Web UI2024
A type foundry storefront that shows the type properly
A shop selling typefaces where you could not set your own words in one before buying.
Foundry TypeRead case study
Web UI2025
A query workspace for people who are not afraid of SQL
A data tool that had been simplified so thoroughly that its expert users had started working around it.
QuarryRead case study
Design Systems2024
One design system across six insurance products
Six products, four front-end stacks, and eleven different buttons that all did the same thing.
Meridian InsuranceRead case study
Design Systems2023
A retail design system that survives a seasonal rebrand
Four brands, one codebase, and a merchandising team that changes the look of everything twice a year.
GroveRead case study
Design Systems2025
Component documentation developers actually read
A well-built component library with adoption problems that turned out to be documentation problems.
SignalRead case study
05Start a project
Recognise your product in any of these?
Most of the projects above started with a message describing a symptom rather than a solution. That is the right way to begin. Tell us what is going wrong and we will tell you what we think it is.
- Prefer email
- studio@baseline.design
- Current availability
- Taking on two engagements for the coming quarter.
- Typical reply time
- Two working days, from a partner rather than a form.
