JournalBuilding products

What a mobile app brief needs before anyone writes code

Most overruns start as questions nobody asked in the first week. Here are the ones worth asking.

An old junction box with loose wiring on a weathered blue wall.

We build mobile apps in Flutter or React Native, usually over 12 to 20 weeks. We have not published a public mobile case study yet, so this is guidance, not a story.

Settle these first

  1. Who is the user, and what is the single thing they open the app to do?
  2. Does it need to work without a connection, and for how long?
  3. What does it connect to: payments, accounts, a back end that already exists?
  4. Which phones and system versions must it run on?
  5. What happens to the data, and who may see it?

Choose the approach on purpose

Flutter and React Native both produce an app that feels native, from one codebase. The right one depends on your team's skills, what you need from the device, and what you already run on the web.

Plan the release, not just the build

  • Store accounts are set up in your name, early, because review takes time.
  • A small first version tests the idea before the long list of features.
  • Someone is named to answer users after launch.

Photograph from Unsplash.

Bring us the account that is stuck.

A real person reads every message and replies, usually within 6 hours. Remote, working across UK, EU and US Eastern hours from UTC+1.