Chapter 4 of 11
Apps that fit in a pocket — and a life
A phone is the most personal computer anyone owns. We build apps that respect that: quick to open, clear at a glance, gentle with battery and data.
Cross-platform or native?
For most products a single cross-platform codebase (we usually reach for Flutter or React Native) gives you iOS and Android at once without doubling the cost of every change. When an app leans heavily on the camera, Bluetooth, background location or platform-specific widgets, separate native builds in Swift and Kotlin can be the kinder choice in the long run.
We'll explain the trade-off for your app in a short written note — including what it means for future hiring and maintenance — rather than defaulting to whichever tool we used last.
What we look after while building
- Offline first moments. What happens on the Tube, in a lift, in a field.
- Accessibility. Dynamic text sizes, screen readers, colour contrast and touch targets checked on real devices.
- Notifications with manners. Asked for at the right moment, easy to tune, never spammy.
- Privacy by default. Only the permissions the app genuinely needs, explained in plain words.
Seeing it on your own phone
From the first fortnight you'll have a test build on your device through TestFlight or Google Play's internal testing track. You'll comment on the real thing, not screenshots. Each build comes with short release notes listing what changed and what we'd like you to try.
When the app needs a back end
Most apps need somewhere to keep accounts and data. We design simple, well-documented APIs and pick hosting that matches your size — managed services for small teams, more control when you need it — and write down every account, key and renewal date in a handover document that belongs to you.
Questions people ask
How long does an app take?
It depends on scope, and we won't guess before we've talked. After a first conversation we send a written estimate with ranges and the assumptions behind them.
Can you take over an app someone else built?
Often, yes. We start with a paid review of the code and accounts so that we can tell you honestly what shape it's in before committing to changes.
Will you sign an NDA?
Yes, happily, before you share anything sensitive.
Who owns the code?
You do. Repositories live in accounts you control, or are transferred to you on request at any point.