What 82 field service apps taught us about building for technicians

Every field service app is judged twice. Companies choose it in a sales process, and technicians rate it in Google Play and the App Store after real days on site. Those public ratings are one of the most honest sources of insight into what works for people in the field.

We wanted to know what those ratings say about field service software as a whole. So we put together a corpus of 82 mobile apps used by field technicians, from enterprise platforms and specialised tools to apps that equipment manufacturers build for their own installers. The pattern we found is simple. Technicians judge the screen they hold in their hand, and that screen is where the biggest differences between apps appear.

How we built the corpus

We started with 85 field service, maintenance and aftersales apps from Europe and North America and ended up with 82 complete product files. For each app we collected the store listing, install counts and ratings in both Google Play and the App Store. The store data was collected in early September 2026, and ratings come from the store in each vendor's main market.

We then read the store descriptions of 78 apps and noted which capabilities vendors choose to highlight, such as offline work, photos, voice input and messaging. Ratings tell you how technicians feel about an app, and descriptions tell you what its makers promise. Putting the two side by side gives a fairly honest picture of the market.

One rule kept the comparisons fair. Wherever we compare scores, we only use apps with at least 15 ratings in each store, because an average built on five votes says very little.

Enterprise platforms: same category, very different apps

The big platforms score anywhere from 2.0 to 4.4 in Google Play. They compete for the same customers with broadly similar feature sets, which makes the spread in how technicians rate their apps all the more telling.

The learning here is that the mobile app deserves attention of its own. Companies usually choose the platform, the licences and the integration, and the technician app comes as part of the package. SAP and Oracle show that an enterprise system can have a mobile app technicians rate well, which suggests that the rating depends on how the app itself is designed and built.

The apps technicians love

At the other end of the scale sit specialised apps. Specialisation alone does not guarantee a good score, since UpKeep has 3.8 and mfr 3.5 in Google Play, but three apps stand out because they combine high scores with large numbers of ratings.

The market has noticed. In May 2026 Autodesk agreed to acquire MaintainX for about 3.6 billion dollars (The Next Web, 2026).

What these apps have in common shows up in how they describe themselves. MaintainX talks about technicians taking photos, recording voice notes and working offline. Praxedo presents photos with arrows and annotations as visual proof of the work done. PlanRadar organises everything around a ticket that people complete together with photos, text and voice messages. Each of them describes a technician's day on site, while the enterprise listings mostly describe what the system gives the back office.

Offline mode is a good example. Many apps, from enterprise platforms to specialised tools, list offline work among their features. Because the promise is so common, it cannot explain the differences in ratings on its own. A feature on the list is only the starting point, and technicians rate how it feels when the signal drops in a basement and they need to know their report has been saved.

Manufacturer apps: huge reach, uneven experience

The third group surprised us most. Equipment makers such as Viessmann, SMA, Fronius, Hilti, Festo, Liebherr and Wacker Neuson build their own apps for the installers and service partners who work with their products. The largest of them have more than 100,000 installs each, and their ratings vary widely.

For a manufacturer, this app is often the first piece of software an installer touches during commissioning, and it shapes how that installer feels about the whole brand. The learning for manufacturers is that this app is part of the brand experience, so it deserves the same care as the products it supports.

These apps are also hard to buy off the shelf. In our separate review of 135 field force startups funded or acquired since January 2025, only one of six aftersales startups had a confirmed mobile app. Manufacturers who want a better app for their installers usually have to build it.

The Android gap

In 16 of the 25 apps that have enough ratings in both stores, the Android version scores lower than the iOS one. Salesforce drops from 4.0 on iOS to 3.2 on Android, Viessmann's ViGuide from 4.4 to 3.6, mfr from 4.1 to 3.5 and UpKeep from 4.2 to 3.8.

Part of the explanation is technical. Android is harder to build well for than iOS, because an app has to run on a far wider range of devices and support older versions of the operating system, each with its own behaviour. Keeping performance smooth on cheaper phones takes extra work as well. Field service adds its own layer, since rugged devices often stay in use for years and run whichever Android version their manufacturer still supports.

Teams have tried different ways around this. Shopify moved its apps to React Native in 2020 so it could stop building every feature twice, once for iOS and once for Android. In September 2026 it announced a return to native development, because coding agents have cut the cost of building for each platform, and its Shop app went from proof of concept to a rebuilt native app in the stores in 12 weeks (Shopify Engineering, 2026). Whichever technology a team chooses, the learning for field apps stays the same: the Android version needs to be designed and tested on the devices technicians actually carry.

“Supporting Android hardware in field service requires extra care. Technicians tend to use rugged devices that stay in service for years, often running older OS versions, so these are the configurations we test on. They also work in places with limited or no connection, which is why we design with offline mode in mind from the start. Ultimately, the app needs to exchange data with sources ranging from ERPs to shared spreadsheets, and integrating them reliably is both the hardest part and the most important one.”
‍
Sebastian Ewak, CTO, nomtek

The Android version can also be the one with far more users. Salesforce has almost 6,000 ratings in Google Play and about 800 in the App Store. Many field teams work on rugged Android devices or on phones chosen by the procurement department, so the Android version deserves at least as much attention as the iOS one. If your technicians carry Android phones, the App Store rating of the software you are evaluating tells only half the story.

What vendors promise

Store descriptions show which capabilities vendors consider worth highlighting, and they also show what is still missing from the conversation.

Offline work comes up in about four in ten descriptions, across the whole range of ratings. Photos appear in many listings as well. The best rated apps describe them as part of the work record, with annotations, a link to the right job and a place in the final report. The learning is that these capabilities matter most in the details: whether a photo carries the time and place it was taken, whether it is attached to the right job and whether the technician can see that the data is safely stored when the network is gone.

Voice looks like the real gap. Only 6 of the 78 descriptions mention dictation, voice notes or voice messages: MaintainX, PlanRadar, UpKeep, pds Service, Mobility Work and GuideTI. Two of them, MaintainX and PlanRadar, are among the best rated apps in this article. Every job ends with a report that someone has to write, so this is one of the clearest opportunities in the market.

Investors see the same opportunity. In the first half of 2026 the number of funding rounds for technician tools almost doubled, led by copilots that use the camera and voice and by tools for field reports. Yet only two of the ten technician copilots we reviewed have a confirmed mobile app.

What this means for your field team

In our data, the size of the system behind an app does not predict its rating. Enterprise platforms already have the data, the workflows and the offline features, and their brochures list them all. Our reading is that the difference between a 2.0 app and a 4.7 app lies in the layer the technician actually touches: whether the app saves the work when the signal drops, whether a photo becomes proof of what was done, and whether a technician can dictate a report on site and skip typing it up in a hotel room at night.

"When we talk to service teams, the same request comes up at every level, from the COO to the technician on site: fewer clicks. One company cut its fault report from about fifteen fields to five, and the back and forth with its clients simply disappeared. The most expensive problems we hear about rarely sit inside the machine. They sit between the technician, the office and the warehouse, when a missing detail sends someone to a site without the right part."
‍
Łukasz Kincel, Chief Strategy & Innovation Officer, nomtek

The good news is that this layer can be built without replacing the system underneath. If your technicians use an app with a weak rating, the back end can stay and the front end can change. If your service runs on a system that has no app for technicians at all, the same logic applies, because the data and processes you need are already there. And if your technicians still work on paper, spreadsheets and private phones, you can start with the three things the best apps do well: offline work that technicians can trust, photos that serve as evidence, and reports they can dictate.

Before you choose your next field service tool, it is worth reading its reviews in both stores. They are written by the people who will use it every day.

Key insights

1. Platform size does not predict the rating. Salesforce, Oracle and SAP compete for the same customers, and their technician apps score 3.2, 3.9 and 4.4 in Google Play.
2. The best apps are built around a day on site. MaintainX, Praxedo and PlanRadar score between 4.4 and 4.7 and describe what the technician does, from photos and voice notes to messages on a job.
3. Offline mode is common, so execution makes the difference. About four in ten apps list offline work among their features, across the whole range of ratings, and technicians judge how it behaves when the signal drops.
4. Manufacturer apps are part of the brand. Apps from Viessmann, Fronius and SMA each have more than 100,000 installs, so they shape how many installers experience the brand.
5. Android deserves equal attention. In 16 of 25 apps the Android version scores lower, and it can be the version with far more users.
6. Voice is the open opportunity. Only 6 of 78 store descriptions mention dictation or voice notes, while investors are funding technician copilots that rarely have a mobile app yet.

What we build for people in the field

At Nomtek we build the apps that technicians, operators, sales reps and dealers use every day, usually on top of the systems our clients already run. For Pilatus, GelSight and Vialytics we have built tools for technicians and service teams, including remote video support for Pilatus. We also work with Siemens Healthineers on apps for field sales. That experience is why the patterns in this analysis looked so familiar to us.

Sources

• Google Play and App Store listings of 82 field service apps, including ratings, install counts and descriptions, collected in early September 2026.
• Nomtek, review of 135 field force startups funded or acquired between January 2025 and September 2026, internal analysis, September 2026.
• Gergely Orosz, Why has Shopify dropped React Native?, The Pragmatic Engineer, 29 September 2026. https://newsletter.pragmaticengineer.com/p/shopify-native-mobile
• Autodesk buys MaintainX for $3.6bn to push from design into operations, The Next Web, May 2026. https://thenextweb.com/news/autodesk-maintainx-36bn-acquisition

‍

‍