What we build, and how.

Mobile apps, web apps and the backends behind them, for founders and small software companies. You work directly with the people doing the work.

Build the product

Usually all four together, so the app, the dashboard and the API are designed as one thing.

  • 01

    Mobile apps

    • React Native
    • Expo

    iOS and Android apps from one React Native codebase, built to work on a job site with patchy signal.

    • One codebase for both platforms
    • Offline-first job data and sync
    • Camera, photo capture and GPS
    • App Store and Google Play releases
  • 02

    Web apps

    • Next.js
    • React

    The office side of the same product: what your team works in, and what your customers see.

    • Owner and admin dashboards
    • Customer booking flows
    • Marketing sites
    • Shared accounts and data with the app
  • 03

    Backends

    • Node
    • NestJS
    • Python
    • PostgreSQL
    • AWS

    APIs, databases and infrastructure designed around the apps that depend on them.

    • APIs the mobile and web apps share
    • Database design and migrations
    • Integrations with the tools you use
    • Deploys and hosting on AWS
  • 04

    Field-service features

    • Mobile
    • Web
    • Backend

    The parts that field-service and home-service products keep needing, and that are easy to get wrong.

    • Scheduling and dispatch
    • Crew apps with clock-in and GPS
    • Photo capture and checklists
    • Automatic updates to customers
A phone mounted in a vehicle showing turn-by-turn navigation on a map

Built for work away from a desk

Some of what we build gets used in a van, on a driveway, or in a basement with one bar of signal. These are the parts we've built more than once:

  • Scheduling
  • Dispatch
  • Crew apps
  • GPS check-in
  • Photo capture
  • Offline sync
  • App Store releases
  • Play Store releases

Keep it fast and running

For products that already exist, ours or someone else's.

  • 05

    Mobile performance audits

    • React Native

    For a React Native app that's slow to open, heavy on battery or unreliable offline. We profile it and tell you what to fix first.

    • Profiling on real devices
    • Startup time, rendering and memory
    • Offline behaviour and sync
    • A list of fixes in priority order
  • 06

    Ongoing support

    • Mobile
    • Web
    • Backend

    We stay on after launch, so bugs and new features go to the people who already know the codebase.

    • Bug fixes and small changes
    • New feature development
    • OS and store-policy updates
    • Monthly or as needed
Lines of code on a dark monitor lit by blue and red light

A small stack we know well

We stick to a few tools so we can go deep on each: one language across mobile, web and most of the backend, and one database.

Mobile
React Native, Expo
Web
Next.js, React
Backend
Node, NestJS, Python
Data
PostgreSQL
Hosting
AWS
Stores
App Store, Google Play

Most builds take 4 to 8 weeks

Less for a focused first version, more for a bigger platform with integrations. Either way you get a real date up front.

  1. 3 to 5 days

    Discovery and scope

  2. 1 week

    Design and architecture

  3. 3 to 6 weeks

    Build

  4. 3 to 5 days

    QA and release

See it in practice

All of the above, in one product

Sanitavia is the mobile app, the web side and the backend behind it, built and released by the same team.

Read the Sanitavia case study

Tell us what you're building.

We'll give you a straight answer on scope, timing, and whether we're the right fit.

Get in touch