Enterprise mobile app: design principles for field teams

A maintenance technician stands next to a faulty machine in a warehouse. He has a tool in one hand and a phone in the other. He opens the fault form, sees twelve fields, fills in two of them, puts the phone in his pocket and decides to finish the rest in the evening at a desk. By the evening he can no longer remember exactly which part was replaced, and the record goes in incomplete.

The problem is not the technician; it is the design. An enterprise mobile app is a business application in which field teams carry out tasks, data, documents and approvals from a phone or tablet, connected to the central systems. It should not be treated as a shrunken copy of a desktop system, but as a separate flow built for field conditions. In this article we explain which principles an app designed for the field should rest on, and what those principles look like in practice.

A shrunken desktop does not work in the field

Squeezing a desktop screen onto a phone does not make a mobile app. A user sitting at a desk gives the screen their full attention, has a wide keyboard and is in no hurry. A user in the field is standing, doing a job and often working with one hand. Before you start designing, the answers to these questions should be clear:

• Where does the user do the work: in the warehouse, on the construction site, at the customer’s office, in a vehicle?
• Can they use only one hand, are they reading the screen in sunlight, are they wearing gloves?
• Is the connection strong everywhere; how should the form behave when it is weak or intermittent?
• How much time can they spare for one task; do they need to finish it quickly, on their feet?

Four design principles

1. Understand the context

The first step is not drawing screens but working out the user’s real working conditions. Watch a field employee at work; note when they pick up the phone, what they are forced to type, and what they skip and leave for later. This observation decides which fields are mandatory and which are optional, and removes unnecessary fields from the start. The different roles that will use the same app should also be considered separately: the needs of a sales representative on a visit, a technician fixing a fault and a manager monitoring the field remotely cannot be met by the same screen. Find the most frequent task for each role and build the home screen around it.

2. Shorten the flow

Few steps, a clear status and fast data entry are the foundation of a field app. Use selections instead of typing and smart defaults instead of empty fields; keep the status of the job visible on every screen. If a form cannot be finished standing up and with one hand, it should be shortened or split into two separate steps. Ask the user only for the information needed at that moment; move fields that are not needed into the background. Error messages should also be short and guiding: they should say what is missing and should not force the user to start over.

3. Use the device’s capabilities

A phone carries tools a desktop does not have: a camera, location and a barcode reader. Photographing a faulty part, scanning a product label with a QR code or barcode, and confirming a visit with a check-in are all faster than typing and leave a more reliable record. What matters is connecting them in a controlled way: the user should know why each permission is requested, and location should only be used at the moment it is relevant to the job. When evidence such as photos and barcodes is linked directly to the record, the statement “I did this job” becomes a record that can be verified later; the manager can also see what is behind the number.

4. Send data back to the centre

Information collected in the field has no value if it stays on the phone. The app should be built to feed data to the ERP, the portal and reports. Otherwise the field employee enters the data into the app, the office employee types the same data into the system again, and the two sides’ numbers drift apart over time. Decide the direction of the data flow from the start too: which information goes down from the centre to the field (work order, customer information, documents), and which goes up from the field to the centre (status, photo, measurement, approval)? Notifications connect these two directions; when they reach the right person within the context of the task, they reduce delays.

Which flows does a mobile app include?

The scope varies from one business to another. In YazSis Mobile App work, the following areas are covered for field teams:

• Field operations: plan, task, visit, check-in and status flows.
• Employee self-service: leave, expenses, documents and access to company information.
• Sales apps: customer, quote, order and visit management.
• Mobile dashboard: critical indicators and alerts for managers.
• Camera, barcode and QR: fast, verifiable data collection from the field.
• Notifications: timely alerts to the right person, in the context of the task.

A good field app does not ask users to do more work; it asks them to record the work they already do in fewer steps.

You can read about our approach to enterprise mobile apps for your field and employee operations on the Mobile App page.