Mobile apps
Apps built for thumbs, not for screenshots
iOS and Android apps designed for one-handed, half-attentive, slightly-late-for-the-bus use. Which is to say: real use.
What we start with
A list of what the app must let someone do in the first thirty seconds after opening it. If that list is longer than three items, we keep trimming. The prototype comes next, on your phone, within the opening weeks.
How we build
- Cross-platform frameworks for one shared codebase when the app suits it.
- Native modules for heavier device work: Bluetooth, camera pipelines, background tasks.
- Offline-tolerant data with sensible syncing when the signal returns.
- Notifications that ask permission at a sensible moment, with settings users can find.
- Accessibility: screen-reader labels, dynamic type, contrast and touch-target sizing.
- Testing on real devices across sizes and operating-system versions.
Things we will raise early
- Does it need to be an app?
- Sometimes a mobile web app is quicker, cheaper and easier to update. We will say so.
- What does it store?
- Device storage, server storage and personal data are agreed and documented up front.
- Who maintains it?
- Operating systems update yearly. Someone needs to keep up; we can, or we can hand over cleanly.