An inspection-only mobile mechanic app, built for both sides of the job
Customers book a mechanic who comes to the car; mechanics go on duty, work a 17-point checklist and file the report. Forjwell is designing and building one Flutter app for both. Still in build.
01The challenge
Getting a used car checked, or a fault diagnosed, usually means a garage visit and a waiting room. Mechanics on Duty sends a vetted mechanic to the car instead. The client narrowed the product to inspection only: MOD inspects and reports, and any repair is arranged directly between customer and mechanic.
02Our approach
One rule shapes everything
Inspection only. There is no quote builder, no parts-and-labour invoice and no use of the word repair anywhere in the interface.
One app, two roles
A single Flutter app with a role picker. Customers book, track the mechanic live and read the report; mechanics flip an on-duty switch, take jobs and work the checklist.
The car is the interface
A wireframe car with tappable markers on eight zones. Mechanics inspect area by area, and customers see exactly where each finding sits.
Rules enforced in code
Every point is rated Good, Monitor or Failing, a failing point needs a photo, reports follow the VIN rather than the booking, and mechanics need admin approval before they see jobs.
03Inside the work
04Both sides of the inspection
- CustomerBook, track, approve time, read the report
- MechanicDuty switch, jobs, checklist, report
- Live trackingRoute and arrival time on a map
- Inspection reportGood, Monitor and Failing by zone
- VIN reportsHistory follows the vehicle
- Client viewerExpiring links, watermarked screens
05The outcome
Alpha builds of the iOS and Android app run end to end on demo data, with a design system and a token-gated viewer for client review. The backend and admin console are not built yet. Mechanics on Duty is still in build, and this case study says so.
06Services used
