A field technician completes a visit in a basement, taps Save and closes the app. Upstairs, the dispatcher still sees an unfinished job. Before asking how much a mobile app will cost in Jordan, decide what each person should see during that gap. Two suppliers can quote for the same screens while making very different assumptions about the work behind the Save button.
Describe the visit from the technician’s point of view
Fictional example. A maintenance team in Amman issues Android phones. Each technician downloads assigned visits before leaving the office. At the site, the technician needs the job reference and checklist, records the outcome in Arabic or English, and saves it without a signal. The office needs to know when that report reaches its system. Photos and iPhones are options for a later phase in this example.
Give every bidder the same starting conditions. Specify the supported phones, how far in advance assignments can be downloaded, how long a technician may be offline and what happens if a new assignment arrives during that period. Decide whether a downloaded visit stays readable after the app closes. On the quote, separate reading a downloaded checklist from creating or editing a visit report offline.
Agree what “saved” means on each screen
For the sample visit, use three visible states. Saved on this phone means the technician can reopen the report. Received by the office means the receiving system has acknowledged that specific visit. Needs review tells a named person to resolve a disagreement or rejection. Ask the supplier to show how the technician finds an outstanding report the next morning and what the dispatcher sees before the first acknowledgement.
Android’s architecture guide describes storing data on the device, queueing changes and reconciling them when connectivity returns. WorkManager supports scheduling a uniquely named background task. A supplier should also demonstrate how the office system recognises a repeat submission of the same visit. Checking the scheduler alone would miss a duplicate created after the server saved a report but its reply never reached the phone.
Give each bidder the same three acceptance tests
- Close the app without a signal. Load a fictional visit, turn on airplane mode, enter a note and save. Close and reopen the app. The note and the visit reference should still be visible, with the report marked as awaiting delivery.
- Interrupt the acknowledgement. In a test environment, let the office system accept the report, then have the supplier interrupt its reply and retry. Find the visit in the office system, count the final reports and check the phone’s status. The agreed result for this example is one report linked to the original visit.
- Edit the same job in two places. While the phone is offline, have dispatch cancel the job. Reconnect after the technician records it as completed. In this example a supervisor reviews the cancellation and the technician’s note before choosing the final status. Agree who makes that decision and how both people see its outcome.
Ask for the work behind each quoted amount
Request separate amounts for the Android app, changes to the dispatch system, testing on the agreed devices and post-launch support. Ask whether the supplier controls the receiving system and can test its retry behaviour. If a third party owns it, have the bidder identify the access or changes that its quote assumes. Ask for the currency and any recurring charges so you can compare proposals on the same basis.
Then price one change. If iPhones join the fleet, request a separate iOS estimate and demonstration of those same three outcomes. If technicians need photographs, specify the maximum file size and what they see when the text arrives before the photo. For help drawing up the visit and test sheet, bring a blank checklist and a sample job reference to Lava’s custom software team or discuss your mobile app brief.
