Services02 / 08

App development

iOS, Android, and cross-platform apps people keep on their home screen. We shape the flows, build the app, and take it through store review.

Start a project

Try it

A working concept

Use it the way a visitor would. It runs in your browser on sample data, and nothing you enter leaves the page.

Concept demo, sample data

fieldline.example

FieldlineConcept

A field service app that keeps saving when the signal drops. Try the whole loop on the phone.

  1. Start the next job
  2. Tick off the checklist
  3. Turn on offline mode
  4. Add a note
  5. Go back online and watch it sync
OnlineEverything is synced

Today

2 of 6 stops done

Next stop

Walk-in chiller fault

Cold store, Unit 4, Quarry Road

Arrive
10:40
Drive
6.3 km
Booked
90 min

All stops

WO-2291Stop 3 of 6

Walk-in chiller fault

Cold store, Unit 4, Quarry Road

Start the job to use the checklist.

Notes

All synced

Quick note for WO-2291

  • Filter changed. Next service in six months.

    WO-2289, 09:48Synced

  • Flue reading normal. Logged on the sheet.

    WO-2287, 08:52Synced

Next: start the next job

Dispatch console

What the office can see

Van 3 connected

  • 1Boiler serviceDone
  • 2Rooftop unitDone
  • 3Walk-in chiller fault10:40
  • 4Oven extraction12:15
  • 5Clinic fridge14:00
  • 6Pump inspection15:30

Notes received

  • WO-2289, 09:48Filter changed. Next service in six months.
  • WO-2287, 08:52Flue reading normal. Logged on the sheet.

Outcomes

What changes

  • People keep it installed

    The everyday task takes a few taps, so the app earns its place on the home screen.

  • iPhone and Android stay in step

    One product plan and, where it suits, one shared codebase, so new features reach both platforms together.

  • It works on a weak signal

    Where the job needs it, key screens load from the device and changes sync when the connection returns.

  • Updates go out safely

    Automated builds, test releases, and staged rollouts get fixes to people without a risky launch day.

Deliverables

What you get

  • Product brief and user flows
  • Clickable prototype of the key journeys
  • Interface design for iOS and Android
  • Tested app, with source code in your repository
  • Backend, API, and admin panel where needed
  • Analytics and crash reporting
  • App Store and Google Play listings
  • Release pipeline and handover documents

Process

How it runs

  1. Scope

    We map who uses the app, what they need it for, and what the first release must do.

  2. Prototype

    You tap through the key flows on a real phone before they are built, and we change what does not work.

  3. Build

    We work in short rounds. After each one, a test build lands on your phone for review.

  4. Release

    We prepare the listings, handle store review, roll out in stages, and hand over the code and documents.

Questions

Worth asking

Should we go native or cross-platform?

It depends on the app. Cross-platform suits most business apps: one codebase, and both platforms move together. Native makes more sense when the app leans heavily on the camera, sensors, or graphics. We recommend one during scoping and explain why.

Do you handle App Store and Google Play submission?

Yes. We prepare the listings, screenshots, and privacy details, submit the builds, and deal with any review feedback. The developer accounts sit in your company's name, so the app stays yours.

Can the app connect to systems we already use?

Usually, yes. If your booking, stock, or customer system has an API, the app can work with it. If it does not, we look at what access is possible and may build a small service in between. We check this during scoping, before you commit to the build.

What happens after launch?

Apple and Google keep changing their platforms, so an app needs regular care. You get the code and documents to run it yourselves, or we can agree ongoing support separately.