Mobile applications — iOS and Android

Design, build and release on the stores — with the source and the store accounts handed over in your name.

We build Android and iOS applications for business and hand them over live on the stores. What is different about the handover is that the source, the store accounts and the publishing rights are in your company's name, with documentation another team could pick up from.

What you get

  • An Android and an iOS app from one team, behaving the same way.
  • A Google Play and an App Store account in your company's name — not ours.
  • The full source, in a repository you own.
  • Build and release documentation: the steps another team needs to carry on.
  • An agreed support period, written into the contract.

It is written down here because the opposite is common in this market: an app published under the developer's own account, which leaves the client unable to update or move it without them. We do not work that way.

How the work runs

  1. A call first: what the app does, for whom, and why an app rather than a website. If the answer is a website, we say so.
  2. A written scope listing the screens and the integrations, a fixed price in the currency you choose, and delivery stages.
  3. The screens are designed and approved by you before any code. A change on a drawing costs far less than a change on an app.
  4. Test builds on your own phone while the work runs, not a demo at the end.
  5. Release on the stores from your accounts, and handover with the source and the documentation.

Native, or one codebase for both?

Decided per project, not by a fixed rule. An app whose screens are forms, lists and content is built from one codebase for Android and iOS, which saves time and maintenance. An app that leans on the camera, heavy graphics or something specific to the operating system is built native. Both are handed over the same way.

What we need from you

  • A Google Play and an Apple developer account in your company's name — we help you open them, but they are on your email and your documents.
  • The logo and the colours, if they exist. If they do not, we say so before the price.
  • If the app talks to a system you already run: somebody who knows that system and can answer questions.

After launch

The stores change their rules and the operating systems update, and an app that is never updated is eventually removed. That is why the support period is written into the contract, and after it you are free: continue with us, or hand the source and the documentation to any other team.

What determines the price

  • How many screens, and how complex each one is.
  • Integrations: payment, delivery, sign-in, notifications.
  • Whether it needs an admin panel or talks to a system you already run.
  • Offline or online, and if offline, how it syncs.

Tell us what's holding you up.

No need to write a full brief. Write what you know, we'll ask about the rest.

Tell us what you need