Skip to content
Mobile applications

An app for your teams in the field.

Forms, job tracking, photos, signatures: your teams capture information where it happens, and the office receives it immediately. Android and iOS, from a single application.

In practice

What a field app actually does.

Not a consumer app: a working tool, designed to be used standing up, outdoors, one-handed.

  • Data capture forms

    Your job sheets filled in on the phone instead of on paper, with required fields checked before submission.

  • Job tracking

    Every job with its status, history and details. The office sees progress without making a call.

  • Photos and attachments

    Taken in the app and attached automatically to the right record, with no manual transfer.

  • Client signature

    The client signs on screen at the end of the job, and the document goes out immediately.

  • Location

    Placing a job, guiding to an address or tracing a round — when it genuinely helps.

  • Syncing with the office

    What the field captures reaches the office, and what the office schedules reaches the field.

  • Notifications

    A new job, an urgent call-out, a schedule change: the right person is told.

  • Working offline

    Where signal is poor, the app keeps working and syncs when the connection returns. Worth building only if your sites justify it.

Sound familiar?

Signs an app would save you time.

These come up in almost every business with teams on the move.

  • 01

    Your teams fill in paper sheets that someone then re-types at the office.

  • 02

    Job photos arrive by messaging app and have to be re-filed by hand.

  • 03

    You cannot tell how a job is going without calling the person on site.

  • 04

    Information comes back at the end of the day, or the end of the week — never as it happens.

  • 05

    A lost sheet means an unbilled job.

  • 06

    Your teams sometimes work where the signal is poor.

How it works

From idea to the stores.

  1. 01

    We scope the use

    Who uses the app, in what conditions, and to do exactly what.

  2. 02

    I build it

    One application for both Android and iOS, which avoids paying for two builds.

  3. 03

    Your teams test it

    The app is tried in the field before release: that is where you find out what is really missing.

  4. 04

    Release and follow-up

    Publishing to the stores, a walkthrough with your teams, then improvements.

Proof

Apps already published.

Mobile projects delivered, including one live on the App Store and Google Play.

  • Emergency equipment

    ElectroCoeur

    Published on the App Store and Google Play, with an equipment map, alerts and reports readable on the phone.

    • Flutter
    • Dart
    • Cubit
    View project
  • White-label commerce & delivery

    CrysDelivery

    A delivery app coordinating customer, courier and back-office in real time.

    • Flutter
    • Dart
    • BLoC
    View project
  • Passenger transport

    SAFIRI

    A ride-booking app with automatic allocation to the nearest available driver.

    • Flutter
    • Dart
    • Provider
    View project
Common questions

What people ask before starting.

What does a mobile app cost?

A first usable version starts around €5,000. The budget depends on the number of screens, the features expected — offline mode and syncing are part of that — and the connection to your existing tools. A firm quote follows scoping.

Does it have to be built twice, for Android and iPhone?

No. I build one application that runs on both, which halves the cost and keeps the two versions identical over time.

Does the app work without a connection?

It can, and sometimes it must — but it adds work. If your teams operate where coverage is poor, we plan for it from the start. Otherwise there is no point paying for that complexity.

Who publishes the app to the stores?

I handle it: account setup, visual assets, store listing and release. The developer accounts are created in your name, so the app belongs to you.

How long until it is live?

Expect several weeks for a first usable version, plus store review, which usually takes a few days.

What if I also need a web part?

That is the most common setup: the field uses mobile, the office uses a tracking screen in a browser. Both are built together and share the same data.

Let’s talk about your app.

Describe how your teams work and what gets lost between the field and the office. I reply personally, usually within 24 hours.