02

Mobile app development

A mobile app is not finished when the code works. It is finished when it is published, accepted by Apple and Google, installed, and still working at the next OS version. We carry both halves.

What the build covers

How it runs

  1. 01

    Framing

    What the app does in its user's real life, and what it will not do in the first version.

  2. 02

    Screen design

    The main journeys drawn and approved before the build, because a screen corrected on a mockup costs a fraction of the same screen corrected in code.

  3. 03

    Build and on-device testing

    Installable versions throughout the project, tested on real phones and not only in a simulator.

  4. 04

    Publishing

    Submission to the App Store and Google Play, passing review, then watching the first installs.

Our own apps

We publish our own apps to the stores. What we sell, we push through the same doors you would.

Preview of Fleepflap

Fleepflap

Global connectivity in a traveller’s pocket.

Preview of GeoClock

GeoClock

Field management for cleaning teams: arrivals confirmed, presence verified, time tracked.

Common questions

Do I need Apple and Google developer accounts?
Yes, and they belong to you. We prefer to publish under your accounts rather than ours: it is your app, your listing and your figures.
Do I need an app, or is a website enough?
Often a website is enough. An app earns its place when you need notifications, offline use, the camera, location, or a presence in the stores. We say so at framing, even when the answer shrinks the project.
What happens after launch?
Apple and Google change their rules and their systems every year. A living app needs updates, and that is part of the conversation from the start.

Let’s talk about your project

A precise idea or just a hunch, both are workable. Write to us on WhatsApp, we usually answer within the hour.

Our offices

  • LongueuilQuebec, Canada
  • Port-au-PrinceHaiti

One hour between the two offices, and a team that answers in your time zone.