Article6 min readUpdated
Field Staff App Design for Delivery and Sales Teams
Field staff app design for delivery partners and sales reps: one hand use, sunlight, offline entries and fast screens that work on a busy route.
Picture a delivery partner in Kolkata at 1 pm in May. He holds a parcel in his left hand and the phone in his right. The sun is on the screen. The lift has no network. He needs to mark the parcel as delivered, take a photo and collect cash. If the app asks him to scroll, zoom or type, he will skip steps and fix the record later. Field staff app design is the practice of designing for exactly this situation: people who work away from a desk, with little time, one free hand and a poor connection.
The same principles apply to delivery partner apps, sales rep apps, meter readers, service technicians and survey teams. The screen is a tool they use in 20 second bursts, between real work.
Where and how do field staff use their phones?
Field staff use their phones standing, walking or sitting on a bike, usually with one hand, often in sunlight, rain or a crowded market. They look at the screen for a few seconds, then back at the road, the shop or the customer.
Common facts about their phones: they are often mid-range Android devices, sometimes company issued, sometimes personal. The battery drains by afternoon. Mobile data is patchy in lifts, basements, villages and narrow lanes. Many workers speak a regional language and read English only partly. For this reason, read designing for low end phones and slow networks and regional language app design in India alongside this article.
This is also work where the screen sits between two people: the worker and the customer. A customer may look over the worker's shoulder, so personal data should be shown only when needed.
What does one hand and sunlight use need from the interface?
One hand use needs controls within thumb reach, and sunlight use needs strong contrast and large, plain shapes. Put the main action at the bottom of the screen and avoid pale colours.
Concrete rules:
- Place the primary button at the bottom, full width and tall. The thumb reaches it without a stretch.
- Keep the top of the screen for information to read, not for buttons to press.
- Use dark text on a plain light background, or a dark theme with bright text. Avoid mid grey tones.
- Do not use colour alone to show status. Add words: "Delivered", "Failed", "Pending".
- Avoid small toggles and sliders. Use big two choice buttons.
- Make photos and signatures easy: a large camera button, no cropping step unless needed.
My post on thumb friendly mobile design covers reach zones, and colour contrast in UI design explains why glare makes contrast matter more than usual. Gloves, wet fingers and vibration on a bike all reduce tap accuracy, so give buttons extra space and confirm only the risky actions.
How should the task list and next action look?
The home screen of a field app should answer one question: what do I do next? Show the next stop or visit at the top, with the address, the customer name and one big action button.
A delivery partner screen can follow this order:
- The next delivery card, with address, phone tap-to-call and a "Navigate" button.
- A short list of remaining stops below, in route order.
- A small count at the top: "6 of 14 done".
- A clear separation between pending, done and failed.
A sales rep screen is different. It needs today's visit list, the last order of each shop and one "Start visit" button. Place "Add new shop" in a secondary spot. For the logistics side of tracking and routes, my post on logistics and delivery tracking app design covers the customer view, while this article is about the worker's view.
Keep the list in the same order the work happens. If the worker has to sort or search, you have already lost time. See lists and cards in mobile UI for layout detail.
How should offline entries work?
Offline entries should save instantly on the phone and sync when the network returns, without asking the worker to do anything. The worker should never see a spinner that blocks work.
Design these states clearly:
| State | What to show |
|---|---|
| Saved on phone | A small label: "Saved. Will upload when online" |
| Uploading | A quiet status, not a blocking screen |
| Uploaded | A simple tick and the word "Uploaded" |
| Failed | A visible retry button and a plain reason |
The worker needs to trust the app. If a delivery shows "Saved" they should be able to move on. At the end of the day, show one summary: how many records are waiting to upload, with an "Upload now" button. Warn before logout if any record is unsent, because a logout can lose work.
Conflicts need rules. Suppose two workers update the same order while offline. Decide in advance which version wins and tell the worker plainly. This is a product decision as much as a design one, so agree it with the developers early. The empty and error screens in empty states, loading and error screens help here.
How do you keep data entry short in a field app?
Keep data entry short by using taps instead of typing, prefilled values and defaults. Every typed character on a moving bike costs time and mistakes.
- Use buttons for reasons: "Customer not home", "Wrong address", "Refused", "Delivered".
- Use number pads for quantities and cash amounts, with big keys.
- Offer scan options for barcodes or QR codes where the business uses them.
- Prefill date, time and location automatically, and let the worker correct them.
- Use voice or photo notes as an option, not a requirement.
- Split long forms into steps, each fitting one screen.
For cash and UPI collection, show the amount in very large type and the confirm action only after the amount is correct. See cash on delivery and payment options page and UPI payment UX. Read form design best practices for field labels and error messages.
On the Sokoni seller app, where I worked on seller onboarding, verification and listings, I kept a close count of how much a person must type on a phone. The same thinking applies even more strongly to someone who is standing on a street.
What mistakes should you avoid in field apps?
Avoid anything that needs two hands, a stable connection or careful reading. These are the mistakes that make workers abandon the app and use paper or WhatsApp instead.
- Forcing a network call before each step.
- Hiding the "Call customer" button in a menu.
- Using small text for addresses.
- Asking for the same data twice.
- Showing a popup in the middle of a delivery.
- Resetting the form if the app goes into the background.
- Giving no sound or vibration after a successful save.
Workers also care about fairness. If the app tracks them, say clearly what is tracked and when. Surveillance wording that feels hostile will push people away. Check the rules for employee location tracking with a legal adviser.
How do you test a field staff app?
Test on the route, in daylight, with real workers, using their own phones. A desk test hides almost every real problem.
- Ride along or walk a short route, with permission from the worker and the company.
- Give the worker a normal day's tasks, not a script.
- Turn on airplane mode for a section, to see how offline works.
- Time the key task, such as marking a delivery, and look for slow steps.
- Test at the end of the day, when the battery is low and the worker is tired.
- Ask what they do on paper or WhatsApp instead, because that shows the gaps.
The guide to user research for startups explains how to observe without leading. If your team needs help turning this into screens, you can look at my mobile app design service or get in touch.
Frequently asked questions
Do field staff apps need a dark mode?
+
A choice helps. Bright sun favours a light screen with strong contrast, while night shifts favour a dark one, so let the worker switch.
How do I design for poor network in a delivery app?
+
Save every action on the phone first, show a small saved status, and upload in the background when the network returns.
Should a field app use maps inside the app?
+
Often it is simpler to open the phone's own maps app with the address, because the worker already knows it. Keep the in-app view for the route list.
What is the most important screen in a sales rep app?
+
The visit screen. It should show the shop, the last order and the pending payment, with one clear button to start an order.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.