Measure a mobile app’s value through completed tasks

Which work should become easier after installation?

An installation shows that an app has reached a device. It does not establish whether a service report was captured completely or a request handed over reliably. For a business app, it is therefore useful to anchor expected value in concrete tasks.

Android's core-value guidance emphasises the target audience's needs and main use cases. Our selection proposal is to weigh recurring work benefits alongside setup, updates and support.

Example: the same installation barrier, different use

The following plan is entirely fictional and contains no measured usage figures.

A permanently configured access route may suit the service team. For a single customer request, an extra setup step may lengthen the journey. This does not amount to a blanket choice of app or web offering. Check required device functions, connectivity and usability for the candidate options on the intended devices.

Observe the whole task

Plan a task trial with people from the relevant audience. Define beforehand when a started case counts as complete and correct. Also observe abandonment, questions and later rework. A submitted request may still be incomplete, for example.

GOV.UK includes support and operations when considering user needs. Clarify who handles setup, access and updates. Frequent use alone does not justify a particular technical form. What matters is whether the chosen solution reliably supports the actual workflow and its support effort fits that purpose.

Sources

• Android Developers: Core app value

• GOV.UK: Define user needs