Service

Mobile applications

Mobile applications for people who work away from a desk: field sales, service technicians, delivery, warehouse stock. Where the signal drops and the app has to keep working.

Signs this is for you

  • Your field team writes on paper and somebody types it up later.
  • You need to capture signatures, photos or location at the job site.
  • Your existing app was pulled from the store or has not been updated in years.
  • You want customers to check orders or balances from their phone.

What it includes

Cross-platform apps

Android and iOS from a single codebase, using Flutter or React Native depending on what fits your team and project best. Lower build cost and, more importantly, lower maintenance cost: every change is made once, not twice.

Offline operation

A local database on the device and synchronisation when the signal returns, with conflict resolution rules agreed with you. Work does not stop because coverage does.

Field capture

Photos, on-screen signatures, barcodes and QR codes, geolocation, and forms that adapt to the type of visit or task.

Integration with your systems

The app is not an island: it connects to the ERP, the invoicing system or the database you already run, with authentication and role-based permissions.

Publishing and updates

Managing developer accounts, preparing store listings, handling review, and shipping new versions. Internal distribution too, if the app is not for the public.

How we approach it

  1. Usage definition

    We shadow the people who will use the app through a real working day. A field app is designed by watching the work, not by reading a requirements list.

  2. Clickable prototype

    Real screens you can walk through before any code. Changing a flow here costs an afternoon; changing it once the app is built costs weeks.

  3. Build and on-device testing

    Regular builds installed on your team’s actual phones, not just an emulator. Connectivity and battery problems only surface in real use.

  4. Launch and adoption

    Store submission, support during the rollout to your team, and adjustments based on feedback from the first weeks.

What we use

  • Flutter
  • React Native

What you get

  • Source code and signing credentials in your hands
  • App Store and Google Play accounts in your company’s name
  • Documented API and a staging environment
  • User manual for the field team
  • A written procedure for shipping new versions

Frequently asked questions

Does supporting Android and iOS cost double?

No. Cross-platform development shares almost all the code, separating only what each system genuinely requires. Adding iOS to an Android project is usually a small increment compared with building it twice.

Does offline really work?

Yes, if it is designed for from the start. The app stores locally and syncs when the signal returns. What we need to agree with you is what happens when two people change the same record while disconnected.

Do I need my own developer accounts?

Yes, and in your company’s name. Publishing under a provider’s account is a common mistake that leaves the app hostage. We help you create and configure them.

How long does store review take?

Google Play usually clears within hours or a few days. The App Store is stricter and may request changes. We plan for it rather than discovering it on launch day.

Have a project in mind?

Tell us what you need and we will tell you honestly whether we can help, how long it would take and what it would cost. No strings attached.