Field-service mobile app built cross-platform against an existing Laravel API

Engineers recorded jobs on paper and re-typed them in the evening, so the office worked from data that was always a day old and frequently incomplete.

Engagement

Role: Cross-platform MVP build.

Shape: Prototype validated on site, then a fixed-scope build and store launch.

Duration: Five to six weeks for the MVP tier.

Stack: React Native · TypeScript · Laravel API · SQLite offline store · App Store & Google Play.

What was wrong

  • Jobs were written on paper and re-keyed later, so the office data was always at least a day behind.
  • Sites frequently had no usable mobile signal, which ruled out an online-only form.
  • The existing API exposed data shaped for the web admin, not for a low-bandwidth mobile client.
  • No release process existed for either app store.

What was built

  1. Flow-level prototype tested with the people who would use it on site, before any production code.
  2. React Native app for iOS and Android sharing one codebase, authenticating against the existing Laravel API.
  3. Offline-first job capture with a queued sync that resolves conflicts explicitly instead of silently overwriting.
  4. Store submission for both platforms, including privacy declarations, release signing and a documented build pipeline.

Architecture after the work

One codebase, two platforms — React Native with TypeScript covers iOS and Android from a single codebase, so a fix ships to both without duplicated work.

Offline-first capture — Job data is written locally first and queued for sync, with conflicts surfaced for a human decision rather than resolved silently.

Mobile-shaped endpoints — A thin set of endpoints returns only the fields the app renders, cutting payload size and round trips over poor connections.

Repeatable releases — Signing, versioning and store metadata are scripted and documented so the client's own developer can ship the next release.

Trade-offs and what was left out

  • Push notifications were deferred to a second phase; the first release used pull-to-refresh, which was sufficient for a daily job list.
  • The back-office UI was left untouched — replacing it was not needed to remove the paper step.

Outcome

Jobs are captured once, on site, and appear in the back office after sync — with a release process the client's own developer can run.

Frequently asked questions

Is cross-platform good enough, or do we need native apps?
For form-driven business apps, cross-platform is usually the better trade: one codebase, one release cycle and access to the device features these apps need. Fully native is worth it when the product depends on heavy graphics, sustained background processing or platform-specific hardware APIs.
Can the app work with our existing backend?
Usually yes. Where an existing API is shaped for a web admin, the cheaper route is a thin mobile-facing layer over it rather than a rewrite of the backend.

Related services