Mobile development

How should our mobile app be built?

Short answer

First, check whether it should be an app at all. If it should, we choose native or cross-platform based on what the product needs, and build with privacy, accessibility and real-world connectivity in mind.

Does it need to be an app?

An app earns its place on someone’s phone when it is used often, needs device features such as the camera, location or notifications, or must work offline. If none apply, a well-built website may serve people better and cost less to maintain. We will say so if that is our view.

Note 1

Native or cross-platform

Native Swift and Kotlin give the deepest platform integration. Cross-platform frameworks let one codebase reach both stores. We write down the trade-offs for your product specifically and agree the choice with you.

Note 2

Data with purpose

We list every piece of data the app collects, why it is needed and where it goes. If we cannot explain a field’s purpose, it is not collected. This also makes store privacy declarations accurate and straightforward.

Note 3

Built for the real world

Patchy signal, older devices, large text settings, screen readers, interruptions mid-task. We test against these conditions, not only the ideal one.

Note 4

Measured against the question

Before launch we agree which signals will show whether the app is doing its job, and how they will be collected with appropriate consent. No vanity metrics.

A laptop and phone on a desk with code on screen — Illustrative stock photograph

Deliverables

Platform decision note
Data inventory for the app
Test builds for iOS and Android
Automated tests for core logic and journeys
Store-ready builds and draft listing copy
Source code and build instructions in your repository