Book a call
← Services · 03 / 06

Mobile apps

Apps for staff on the floor, teams in the field and your customers, built to work on real phones in real conditions.

  • Operate
  • In production: Trax, Vijaya, Zesty
  • Expo · Flutter

Why it matters

A mobile app is judged in a dim warehouse, on an old Android phone, with one bar of signal. That is where we test it.

Trax staff scan cartons wearing gloves, so the app has torch control, a large scan target, a sound on success and manual entry when a label is torn. Vijaya patients come from every age group, often on older phones.

We decide what "offline" means for each app, ask for permissions only when they are needed, and keep a deliberately slow Android phone in testing.

What we build

01Staff and scanning appsBarcode scanning, gate passes and stock movement for teams on the floor.
02Field team appsVisits, checklists, photos and signatures that sync when signal returns.
03Customer appsBooking, ordering, payments and reports in an app customers keep.
04Payments in the appUPI and card payments confirmed by the server, with a clear return path when the payment app closes.
05NotificationsPush and WhatsApp messages that tell people what to do next, not just that something happened.
06Store releaseSigning, testing tracks, screenshots and updates that ship fixes without waiting days for review.

How we build mobile apps

  1. 1Lock the decisionsTarget devices, the offline job, roles, how types sync with the web app, token storage and the hotfix path.
  2. 2Pick the stack honestlyExpo when the app shares rules with a web product and ships often. Flutter when the app is the product or your team knows Dart.
  3. 3Done means the whole flowEvery screen handles empty, loading, error, denied permission and reconnect states, not just the happy path.
  4. 4Sign-off on real devicesPreview builds, smoke tests and screenshots from a budget Android phone and an iPhone before every release.
  5. 5Launch and stayDeployed with a runbook, a tested backup restore and error tracking watched after release. The same team keeps it patched and running.

The stack we reach for

Expo · React Native
Most appsOne team owns web, API and mobile with shared types, and JavaScript fixes ship over the air.
Flutter
App-first productsConsistent interfaces on low-cost Android phones, when the app is the product.
Shared API
One set of rulesThe app calls the same server rules as the web app, so money, stock and permissions never drift.
Built forStore staffSecurityField teamsPatientsCustomers

Apps in production

See all work →

On phones in stores, clinics and restaurants.

01TraxUse case →
02ZestyUse case →
03Vijaya Mobile AppGoogle Play ↗

Questions

Something else on your mind? Ask it on the free 30-minute call.
01Expo or Flutter?

We choose on ownership and release pace, not benchmarks. If you have, or will have, a React web product, Expo lets one team share rules and ship fixes faster. Flutter suits apps that are the product on their own.

02Will it work offline?

We define the offline job first: read cached data, record and sync later, or fail gracefully. Each app needs a different answer and we design for it.

03Do you publish to the App Store and Play Store?

Yes, including signing, testing tracks, store listings and screenshots. We also set up over-the-air updates for quick fixes.

04Who maintains it next year?

We name that on day one. We can keep it updated through new OS and SDK versions, or hand over with documentation.

02Web apps →The dashboard and API behind the app.05CRM & booking →Bookings and payments customers make from their phone.Use caseTrax →Mobile scanning, transfers and gate passes in production.

An app your team will actually use.

A free 30-minute call. Tell us who will hold the phone and where.
Pick a dayMon – Sat
Request Wed 4 Nov →