Field team apps: what they need and how to distribute them

Maintenance technician, field sales rep, delivery driver, inspector. People who work on the road usually get through the day with WhatsApp, spreadsheets, and paper. The work order arrives by message, the photo gets lost in the gallery, and the office only learns what happened at the end of the day, when someone types it all in again.

An internal app fixes this, and the decision to hire usually stalls on three questions: what goes into the first version, how to install it without putting it in the public store, and what changes with the new Android rule. The third is recent. On September 30, 2026, Brazil became one of the first four countries with developer verification on Android, and that affects the most common way of distributing an internal app.

When a field app is worth it

The app pays for itself when field information turns into office work. Ask three questions:

1. Does someone retype what the team brings back? If so, you pay twice for the same data.
2. Does a field mistake cost a second visit? Wrong parts, wrong addresses, and missing customer history show up here.
3. Customer asks “where's the technician?” and nobody knows? You lack real-time visibility.

If the field work is simple and the team is small, off-the-shelf software may do the job. I compared these paths in custom system or off-the-shelf software. Custom wins when your process doesn't fit the packaged product, or when the app has to talk to a system you already have.

What the app needs

The list changes by operation, but these items show up in almost every field project:

• Works offline. This is the most important item. The technician has to open the order, fill it in, and save it in a basement, a rural area, or the back of a warehouse.
• Schedule and daily orders. Each person sees only their own, with address, history, and instructions.
• Job log. Forms, photos, customer signature, and barcode scanning, as needed.
• Automatic sync. When the signal returns, the data uploads without anyone pressing a button.
• Integration with the company's system. Without it, the app is one more place to type. Your ERP, CRM, or internal system gets the data directly.
• Office dashboard. Coordinators see what's pending, what's done, and what's stuck.

Why offline mode drives the project

The Android documentation points out that a connection is never guaranteed: there's limited bandwidth, dropouts in tunnels and elevators, and only occasional access. Outside cities, it gets worse. According to Anatel, in data published by Teletime in July 2026, about 26,400 remote localities in Brazil still have no 4G and no obligation to get it.

Offline is an architecture decision, not a last-minute tweak. The app stores data on the device and later has to reconcile it with the server. If two technicians change the same order with no signal, someone has to define which data wins. The documentation itself warns that this conflict must be resolved before syncing.

So ask for a quote that says what works offline, screen by screen. It's one of the items that moves the price most, along with the others I listed in how much it costs to build an app.

How to install without the public store

An internal app doesn't have to appear in App Store or Google Play search. But each platform has its own route, and that route has to be in the scope.

On iPhone. The usual route is a private app, released only through Apple Business to the organizations you name. “Unlisted” distribution is something else: the app leaves search, but anyone with the link can reach it. One detail to watch: after approval, the distribution method doesn't change, and going from public to private means creating a new app.

There's also the Apple Developer Enterprise Program, which costs US$299 a year and requires 100 or more employees, among other criteria. Apple itself says the standard program is the right choice for most organizations. Don't start there.

On Android. The equivalent route is to publish a private app in the managed store, Managed Google Play. The app stays restricted to the organizations you name and is available for distribution within minutes of publishing. This requires managing the devices, which fits company phones better.

What changed on Android on September 30

For years, many companies distributed internal apps the easy way: an APK file sent over WhatsApp. Google's developer verification took effect in Brazil on September 30, 2026, and reaches the rest of the world in 2027.

In this first phase, the system checks installs from seven stores, including Google Play and the Samsung and Xiaomi stores. But Google says the requirements apply to apps on certified devices, wherever the download comes from. The FAQ page is blunt: an unregistered app only installs or updates through the advanced flow or ADB, the command-line tool for developers.

In practice, the advanced flow doesn't work for a team. According to 9to5Google, it requires turning on an option in developer settings, reading the warnings, and sitting through a one-time 24-hour wait, device by device. Picture that on 40 phones on a Monday morning.

You have three ways out:

1. Verify the company and register the app. The organization proves its identity and website and registers the package name. The fee is US$25 on a Full Distribution account, and the user experience doesn't change.
2. Use the organization's store on managed devices. Google says these apps don't need verification because the IT admin has already reviewed them. Even so, it recommends registering.
3. Limited distribution. It needs no identity verification, but it stops at 20 devices and was designed for students and personal use. It's not for a company's operation.

If you already run an app through APKs, check this now: updates also depend on registration.

Field GPS: data that can become a lawsuit

Tracking the team seems like an obvious feature, and it's often the most requested. Before adding it to the scope, look at two risks.

Labor law. Article 62 of Brazil's labor code (CLT) exempts from work-hour control anyone doing external work “incompatible with setting working hours.” An app can change that status. In 2018, the Second Panel of Brazil's top labor court (TST) awarded overtime to a furniture assembler, based on routes, scheduling, trips to the company, and a tablet it supplied. In 2025, the First Panel denied a claim from an employee with a tablet and GPS, because the devices didn't record visits or time at each one, and she set her own route. What matters is what the system actually records. Settle this with your labor lawyer before designing the screen.

LGPD and the store. An employee's location is personal data, and the LGPD (Brazil's data protection law) calls for a stated purpose and a limit to the minimum needed. Tracking only during a job is easier to justify than tracking all day. On Google Play, background location still depends on approval and a clear notice inside the app. Without them, updates can be blocked.

What this means for you

Before asking for a quote, bring these answers:

1. Company phone or employee phone? That defines distribution.
2. Android, iPhone, or both? If the fleet runs one system, the project gets smaller. I compared the formats in native, hybrid, or PWA.
3. What has to work offline? List the screens.
4. Which systems does the app talk to?
5. What gets recorded about the employee? Time, location, and why.

At the Studio, these answers go into discovery, before the fixed price. The deadline is written into the contract, the dev team is our own, and code, developer accounts, and access stay in the client's name. That matters here: Android verification is tied to the identity of whoever registers the app, and that has to be your company.

If your field team still runs on WhatsApp and spreadsheets, see how we handle app development projects and bring your operation to discovery.