Skip to content

For the phones people here actually carry

Mobile apps

An app tested only on a new iPhone on office wifi will fail in a queue in Polokwane. We build for the other case first.

What you get.

Android first, iOS alongside

Most of the market here is on Android, much of it mid-range and a few years old. That is the device the app is built and tested against.

It survives a weak signal

Work is held and sent when the connection returns rather than lost with an error toast. Nothing important depends on a perfect bar of reception.

Payments that clear into a local bank

Yoco, Payfast and Paystack take a card payment in rand and settle here. We do not build a checkout on a processor most South African businesses cannot open an account with.

On the store, and updatable

We handle the listings, the review process and the release pipeline, so a fix reaches users without a month of paperwork.

How this one runs.

  1. Decide what belongs on a phone

    Not everything does. The things people do standing up, in a queue or on a site belong in an app. The rest is usually better on the web.

  2. Build the slow path first

    We develop against a throttled connection and a mid-range device, so performance is a starting condition rather than a fix at the end.

  3. Test on real handsets

    Real devices in real conditions, not only a simulator on a fast laptop.

  4. Ship, then watch

    Crash and performance reporting from day one, so the first week tells us the truth rather than the reviews telling us three months later.

Questions about mobile apps.

Do we need an app, or is a website enough?

A website is enough more often than people expect. An app earns its cost when you need the home screen, push notifications, the camera, or reliable use with a poor connection. If none of those apply, we will tell you to spend the money on the web app instead.

One codebase for Android and iOS, or two?

One, in almost every case. One shared codebase covers both, which halves the ongoing cost of every change. Two native codebases are worth it only for heavy device work, and that is rare in business apps.

Who owns the store listings?

You do. The Google Play and Apple developer accounts are registered to your business, not to us. This matters more than it sounds: an app published under a supplier account is very hard to get back.

What about users on very old phones?

We set a floor and tell you what it is, in real terms, before we start. Anything below the floor gets the mobile web version, which we make sure actually works rather than treating it as a consolation prize.

Tell us what your business is running on right now.

Thirty minutes, no charge, no slide deck. We will tell you whether this is something we can build and roughly what it would take. If it is not a fit, we will say so on the call.