Apps & Software
Mobile Apps for Field Teams: Needs That Are Often Missed
A field app prototype usually runs smoothly in the office and struggles on site. Seven needs should be decided before the budget is locked: signal, upload queues, location, lost devices, distribution, device variety, and updates.
SEO and Content Specialist
7 min read
Short answer: a mobile app for field teams most often fails on what a prototype does not show: working without signal, queues for sending photos and data, location use, lost devices, how the app is distributed to staff, device variety, and regular updates. Decide those seven things, written into the scope, before the budget is locked.
Inspection officers, service technicians, canvassing sales staff, and surveyors work where signal is unreliable, on a wide range of phones, while busy with other tasks. A field team mobile app that runs smoothly in a meeting room can stall in a warehouse, a mining area, or on a factory floor. This article lists the needs that are often missed when requirements are written. The choice of app form, whether native, cross platform, or web app, is covered in Native, Cross Platform, or Web App.
Mobile apps for field teams: seven needs that are often missed
| Need | Question to answer before building |
|---|---|
| 1. Working without signal | What work must still be possible when there is no internet? |
| 2. Upload queue | How do photos, signatures, and forms get sent when signal returns? |
| 3. Location | Is location needed only while the app is open, or also in the background? |
| 4. Lost devices | What happens to data and accounts if a phone is lost or an employee leaves? |
| 5. Distribution | How does the app reach staff phones, and who owns the app store account? |
| 6. Device variety | Which phone brands and versions must be supported? |
| 7. Updates | Who updates the app when Android or iOS changes version? |
1. Working without signal: decide what still works
Android documentation defines an offline-first app as one that can perform all or a critical subset of its core functionality without internet, and at a minimum it must be able to read data without a network. Writing data while offline is harder because it can conflict with data on the server. The same documentation distinguishes three write strategies:
- Online-only writes. Suitable for transactions that must happen right then.
- Queued writes. Suitable for non-critical data such as usage logs.
- Lazy writes. Data is stored on the device first and sent at the earliest opportunity. The documentation calls it the right choice when data is critical to the app, because it avoids the risk of data loss.
Inspection results or visit reports usually fall in the third group. Also decide who wins when two devices change the same data. A common approach in mobile apps is “last write wins”, but whether that suits your data is a business decision, not a technical one. Offline capability is something that can be discussed during requirements mapping. Do not assume it exists if it is not written into the scope.
2. Upload queue: photos, signatures, and forms
Evidence photos and signatures are large and are often sent from places with weak signal. For work that must keep running even if the app is closed or the phone restarts, Android documentation recommends WorkManager. Its scheduled work is stored and rescheduled after a restart, and conditions can be set, for example running only on an unmetered network or when the battery is sufficient. From the user’s side, what needs deciding: whether staff see a “not yet sent” status, what happens if sending fails repeatedly, and whether photos may wait for office Wi-Fi.
3. Location: only while open, or also in the background
The location requirement is often written briefly as “there is GPS tracking”. Yet there are two different cases. Android documentation advises requesting the narrowest kind of location permission that suits the feature, and most cases only need location while the user is using the app. Background location is only appropriate when it is critical to the app’s core functionality and obvious to the user. On Android 8.0 and above, an app in the background receives location updates only a few times each hour, so dense route tracking in the background needs a special design. Google Play policy also restricts background location access to apps that need it for core functionality. Decide from the start when location is recorded and who may see it, and tell the staff.
4. Lost devices and access rights
Field phones are dropped, left behind, and lent out more often than office laptops. NIST SP 800-124 Revision 2 covers the security of mobile devices in the enterprise, including company-issued and employee-owned devices, centralized management, and the whole device lifecycle from deployment to disposal. Practical questions for your app:
- Is a screen lock required before the app opens?
- Can a staff member’s session be revoked from the server when the phone is lost?
- How much data is stored on the device, and is that necessary?
- Can the account of a departing staff member be deactivated the same day?
Apps built by Legia use role-based login, an activity log that records who changed what and when, automatic server-side backups, and security checks on the system. The scope is agreed during requirements mapping.
5. Distribution: how the app reaches staff phones
An internal app does not have to appear in the public storefront. On Google Play, a private app can be restricted to specific organizations. Publishing requires a Google Play developer account, and if you later want to make it public, Google says you need to publish a new app with a different package name. So decide from the start whether the app will be public or private. As for accounts, apps built by Legia are published under your company’s account, not Legia’s, and the source code and signing files are handed over in full. Why this matters is covered in Source Code Ownership in App Development Contracts.
6. Device variety: test on the phones actually used
Field teams rarely use a single phone model. There are company phones, personal phones, and old devices that keep going. Write down the lowest Android and iOS versions that must be supported, and the few models staff use most. Testing on real devices across several brands and versions, not just in an emulator, is part of Legia’s process, and a device list from your team narrows what gets tested.
7. Updates and maintenance after release
A mobile app needs to be updated to follow the Android and iOS versions released every year. Without updates, an app can stop working or be rejected from the app store. There is also the developer account cost: Apple charges an annual subscription, Google a one-time fee. Ask who bears the updates after the warranty period, and whether there is a subscription maintenance scheme or an internal team taking over with documentation.
Checklist before the scope is signed
- A list of work that must be possible without signal, and the store-and-send strategy for each kind of data.
- A rule for when two devices change the same data.
- An upload queue for photos and forms, with a status display for staff.
- A location decision: not used, while open, or in the background, with a policy for notifying staff.
- A procedure for when a phone is lost or a staff member leaves.
- A decision on public or private app, and who holds the app store accounts.
- A list of supported Android and iOS versions and phone models.
- A yearly update plan and who bears it.
The server needs for storing and synchronizing the data are covered in Does a Mobile App Need Its Own Backend.
How Legia works on it
Legia’s Mobile App Development service covers Android and iOS apps, cross platform or native as needed, including field staff apps. Requirements mapping takes 1 to 2 weeks and produces a scope document. After that come a prototype that can be tried directly on a phone, test versions via TestFlight or Play Console on a regular basis, testing on real devices, then publishing and handover. A medium scope generally takes 3 to 6 months until it is published on the app store. Other services in this pillar are on the Applications & Software page.
Frequently asked questions
Is a web app enough for a field team?
It can be, if staff do not need the camera, GPS, or phone notifications, since web apps are updated faster. Field teams usually need at least the camera and location, so a mobile app more often fits. The comparison is in the article on choosing an app form above.
How long until a field app can be used by staff?
For a medium scope, generally 3 to 6 months until it is published on the app store. Test versions can be installed on phones earlier, so staff can try them before release.
What if staff use their personal phones?
That needs its own policy. NIST SP 800-124 Revision 2 covers employee-owned devices, and the core questions are the same as for company devices: what data may be stored, how access is revoked, and who manages it.
Sources
- Android Developers, Build an offline-first appdeveloper.android.com
- Android Developers, Persistent work (WorkManager)developer.android.com
- Android Developers, Background location accessdeveloper.android.com
- Google Play Help, Publish private appssupport.google.com
- NIST, SP 800-124 Rev. 2, Guidelines for Managing the Security of Mobile Devices in the Enterprisecsrc.nist.gov


