Skip to content

Apps and software

Apps built in full, from the data to the screens.

Web, mobile and desktop apps with the data model, backend and admin behind them, built by one team so there is one system to run and change.

Discuss your app
An API is the shared back end every screen talks to, so a rule changes in one place.

What we do

What we build.

  • Web apps and SaaS

    Web apps, including multi-tenant SaaS: one product serving many customers, each with their own data.

  • Android and iOS apps

    Mobile apps for the people who use your service on the move.

  • Desktop apps

    Apps for Windows and macOS when the work happens at a desk.

  • Internal tools, payments and billing

    The tools your team runs on, and the payments and billing behind your product.

From plan to release

Tests and CI from the start.

We start with the architecture and data model, then build the API, apps and admin on top. A test suite and automated checks (CI) are set up as part of the build, not added at the end.

How we build it

Production deployment and app store releases come last, once the rest is in place.

What you get

  • Architecture and data model
  • API, apps and admin
  • Test suite and CI
  • Production deployment and store releases

Built before

Work you can look at.

  • Civic safety app

    Safer Streets

    Our own civic safety app: dark streets reported, taken to the agency responsible and followed until fixed.

  • Overseas recruitment platform

    The Healing Pouch

    A site that earns families' trust, and one system for candidates, employers and staff.

  • Therapy access platform and CMS

    Raahat

    A gentler way to ask for therapy, and the system that matches each request to a therapist.

Related services

Before you buildUI/UX design: flows and prototypes tested with people first.After launchMaintenance retainers: updates, fixes and small features.

How the engagement works

Progress you can see.

  1. Scope

    Agree what ships first and what it costs.

  2. Build

    Data model, API, apps and admin.

  3. Review

    Weekly demos on a live build.

  4. Release

    To production and the app stores, then keep improving.

Questions.

Can you work on an app someone else built?

Yes. We start by reading the code and how it runs, then agree what to change.

Do you build both the app and the backend?

Yes. We build the data model, the API, the apps and the admin, so one team knows the whole system.

Who looks after it after launch?

Your own team can, or we can on a maintenance retainer.

What should your app do?

Tell us who will use it, what it needs to handle and what you run today.

Discuss your app