LabNotes · B2B SaaS · Life sciences
Moving the lab record from paper to the bench
I designed the desktop web app, with its iOS companion and the design system supporting both. Idea was to allow scientists capture bench work on the step itself instead of a paper and scribbles notebook and relying on their memory.

Industry
Biotechnology · B2B SaaS
Tools
Figma, Jira, Confluence
CONTEXT
The record was written after the work
Scientists work at the bench, away from the computer: notes on paper or gloves, photos on personal phones, everything re-typed later. The web MVP served planning at the desk on browser, but didn’t focus on what happens at the bench. Investors pushed for adoption and paying subscribers, and competitors only offered desktop web apps, so iOS became the clearest competitive advantage.

Before: notes on paper, re-typed later. After: captured on the step, during the work.
Who the record serves
MOBILE
Bench scientist
Proves a finished step with a photo or note in seconds, without re-typing from paper.
DESKTOP
Lab manager / PI
Sees what is running, what is late and what is running out, to unblock the team.
DESKTOP
QA / Reviewer
Needs a complete, tamper-evident trail per step, so audits take hours, not weeks.
IMPACT
iOS v1.0 shipped, with a redesigned web app
What shipped, how long it took, and what moved for the business.
18
months, from web redesign to iOS v1.0
26
active scientists in 2 labs captured bench work on iOS
418%
growth in paying subscribers, churn down from 22% to 12%
APPROACH
Key decisions
Four decisions kept the phone fast at the bench and the record complete on desktop. Two needs pulled against each other. At the bench, scientists need speed with gloves on. At the desk, managers and reviewers need a complete record. Every decision had to serve both.

DECISION 01
Mobile captures and views. Desktop plans and edits
I kept iOS purposely lightweight: just follow the protocol, capture what is going on, check what is due. Editing belongs on desktop.

DECISION 02
Every capture is cataloged, even if unsorted at first
The capture sheet opens on the active step of the protocol or experiment. Photos or notes that don’t get cataloged, just live in Unsorted.

DECISION 03
One protocol, the same views everywhere
List, diagram and board on desktop, iPad and iPhone, from shared components. Android coming next.
INSIGHTS
What the bench taught us
Source: client testing with 26 scientists, 4 different teams (biotech, agritech).
20/26
The record is written after the work
Scientists finish bench work first and re-type notes at the desk later.
18/26
Photos get lost on personal phones
Evidence ends up in personal camera rolls, away from the step it proves.
11/26
Paper does not disappear on day one
Handwritten notes stay part of bench work, even with a digital tool.
4/25
Scientists switch devices mid-protocol
One protocol is opened at the desk, on a tablet and on a phone.
SOLUTION
Solution highlights
Three moments from the final design.

A protocol you can read as a map
Every step, branch and decision in one diagram. Statuses of all tasks also visible as done, in progress or still untouched.

Every step, accountable
Substeps, captures and comments sit inside the step, so the record is written during the work.

Six ways to stay on the right step
Search, substeps, alerts, comments and a mini-map keep scientists oriented in protocols with hundreds of steps.

The dashboard shows what to prioritize, today
Pending reviews, steps blocked and materials going thin appear on top so the team knows how to prioritize.
LEARNINGS
What really stroke me
LEARNING 01
The mobile app got better when it got lighter
Limiting iOS to reading and capturing, instead of mirroring the desktop, kept the bench flow fast
LEARNING 02
Designing two platforms together protects one mental model.
Redesigning the web app while building iOS let me define steps, statuses and captures once, instead of reconciling two versions later.
LEARNING 03
Twice-weekly engineering syncs turned constraints into design input.
Reviewing with the CTO early showed what was possible with the backend, hosting, photo uploads and storage, before those limits could become late redesigns.
LEARNING 04
Building on open source made the system easier to maintain.
After v1.0, I rebuilt the components on top of Ant Design, moved typography to variables and adopted Lucide icons for mobile, so the team maintains less custom code.

