Title I · Mobile app development
Small screens, long attention
An app lives a few centimetres from someone's face, often for years. We build them to be brief where brevity helps and patient where patience is needed.
Choosing the binding
For most commissions a cross-platform framework — usually Flutter or React Native — lets one codebase serve both iOS and Android, so every correction is made once. Where an app depends heavily on the camera, Bluetooth, background location or platform widgets, separate native builds in Swift and Kotlin are often the kinder long-term choice. We set out the reasoning for your particular app in a short note, including what it means for future maintenance and hiring, before a line is written.
What we read for
Type that respects the reader's chosen text size. Contrast that survives sunlight. Touch targets a thumb can find. Offline behaviour that tells the truth about what has and hasn't been saved. Permissions asked for only when needed, with an explanation in ordinary words. Notifications that are useful, adjustable and few.
An app is read with the thumb. Set it accordingly.
Proofs on your own phone
From early in the build you receive test versions on your own device, each accompanied by short notes describing what changed and what we would like you to try. You correct the proof, we set the corrections, and the next proof arrives. It is an old rhythm and it works.
Behind the page
Most apps need a server for accounts and data. We design small, documented interfaces between app and server and choose hosting proportionate to your size. Nothing important lives only in our heads or in our accounts.