Skip to content

Building a mobile app

An app is the right choice when people will use it often, especially if it needs notifications, the camera or to work offline. We build and run several apps of our own, and this is what we've learned about going from an idea to something people actually use.

App or website?

Something that's used once a month or so usually works best as a website. An app pays off when the user comes back often, when you want to be able to send notifications or when it has to work without a signal. Sometimes the answer is both: an app for your loyal users and a web page for people who are just dropping by.

Start small

The apps that succeed do one thing well from the start. The first version should solve the main problem and nothing more. After that, your users show you what's missing, and it's almost never what you guessed.

We build for iPhone and Android from the same code. You get an app that feels at home on both, without paying for two.

What tends to get forgotten

The app itself is only part of the job. These also need to be in place before launch.

  • Developer accounts with Apple and Google, in your company's name
  • Login, and a way for users to delete their account
  • Payments or subscriptions, if the app is going to charge
  • A privacy policy and details of what data the app collects
  • The store listing: text, screenshots and keywords

After launch

Apple and Google release new versions of their systems every year, and the app needs to keep up. Expect ongoing maintenance. We do it for our own apps every week, and we're happy to do the same for yours.

Common questions

A small first version often takes a few months from start to store. What decides it is the number of features and how much has to be built on the server side.