Web & Mobile Applications
Interfaces people choose to use instead of working around.
Adoption is the whole game. A system that is technically correct and miserable to use will be routed around within a month: back to email, back to the spreadsheet, back to the phone call. We build interfaces that hold up under speed: fast on a warehouse tablet, legible in a truck cab at dusk, keyboard-complete for the person who does this four hundred times a day.
- Largest Contentful Paint budget we build to
- <2.0sLargest Contentful Paint budget we build to
- WCAG 2.2 conformance target on every build
- AAWCAG 2.2 conformance target on every build
- First-class, not an error state
- OfflineFirst-class, not an error state
Sounds like
You might recognise one of these.
We rolled out the portal and customers still call us for status.
Our field crews gave up on the app and went back to paper.
It works, but it takes eleven clicks to do the thing we do most.
Nothing loads on the shop floor’s connection.
What this includes
The work, specifically.
Not every engagement needs all of it. This is the range we cover and what each part is actually for.
Customer & partner portals
Self-service that actually deflects calls: real-time status, documents, invoices, orders and the ability to change something without a phone tree.
Operator consoles
Dense, keyboard-driven interfaces for high-volume work. Command palettes, bulk edits, saved views, undo. Designed by watching your team work, not by guessing.
Field & offline-first mobile
iOS and Android apps that assume the network will fail: local-first data, conflict resolution, background sync, barcode and photo capture, and a battery budget.
Design systems
A component library, tokens and documented patterns so the tenth screen costs a fraction of the first and looks like it belongs to the same product.
Accessibility as a requirement
We build to WCAG 2.2 AA: keyboard paths, focus management, contrast, screen-reader semantics. It is a procurement requirement in most sectors and simply better software in all of them.
What you get
Deliverables, not documents.
- Production web application, responsive from 320px up
- Native or React Native mobile builds in your app store accounts
- Documented component library and design tokens
- Core Web Vitals budget enforced in CI
- WCAG 2.2 AA conformance report
- Analytics instrumentation on the flows that matter
Shapes
How this usually runs.
Interface audit
1–2 weeksWe watch real users, measure the real numbers, and come back with a prioritized list of what is costing you adoption and what each fix is worth.
Design & build
6–14 weeksProduct design and engineering in one team, shipping to a real environment every week from week two.
Design system foundation
4–8 weeksFor organizations with several applications drifting apart: one library, one language, adopted incrementally.
Tooling
What we build it with.
No tool here was picked because it was new. Where we do reach for something novel, it is in one place, for a stated reason, and it is written down.
- Web
- Mobile
- State & data
- Quality
Proof
Where this has been done.
- 2024About four weeks
The scanner read every barcode except theirs
They had no way to say who was holding what, and a barcode scanner that would not decode their own label format — the capability was licensed separately and they had declined to buy it. Writing the decoder in C cost less than the licence and made the rest of the system possible.
Read the case study- Trackable, in and out, by holder
- Every item
- Bought to read their own labels
- No licence
- 2023–202520 months, four phases
One codebase for the public site and the platform behind it
A public-facing site and an internal student-tracking platform, built years apart on stacks nobody still owned. We consolidated them into one application with one design system and one authorization model, and shipped it without a production regression.
Read the case study- Production regressions across the release window
- 0
- Unit and integration tests at handover
- 600+
Questions
Web & mobile, honestly.
React Native for most business applications: one team, one codebase, and the platform gaps that used to matter mostly no longer do. Native when you need deep hardware access, sustained background processing, or a demanding graphics path. We’ll tell you which case you’re in.
Yes. Product designers sit inside the engineering team rather than handing over files at a boundary. If you have an internal design team or an existing brand system, we work inside it.
Often the fastest win. An interface audit followed by six weeks of targeted work usually beats a rebuild, and we’ll say so when it does.
Further reading
What we think about this, at length.
Sources
Next step
Tell us what’s breaking.
Forty-five minutes, no charge, no deck. We’ll tell you what we’d do, what it would likely cost, and whether you should be building this at all.