What Makes a Good Mobile App? The 9 Things Users Judge Immediately

A good mobile app is fast to open, obvious to use, and works when the network does not. Most apps are deleted within the first week, and the reasons are rarely exotic — they are slowness, confusion, and being asked for too much too early.

Here are the nine things users judge, roughly in the order they judge them.

1. It opens fast

Cold start should be under two seconds. Beyond that people assume it has hung. This is the first impression and it is entirely technical — no amount of onboarding polish compensates for a slow launch.

2. It does not interrogate you on arrival

The worst opening sequence in mobile software: create an account, accept notifications, allow location, rate us. Every one of those before any value has been delivered.

Better: let people use the thing first. Ask for an account when there is something worth saving, and ask for a permission at the moment it is needed, with the reason attached.

3. It feels native to the platform

iOS and Android have different conventions — navigation patterns, back behaviour, share sheets, typography. An app that ignores them feels like a website in a box, and users notice even if they cannot articulate why.

The tell: does the back gesture do what you expect? Does the keyboard cover the field you are typing into?

4. It works offline, or degrades honestly

Phones lose signal — lifts, trains, basements, rural roads. A good app caches what it can, queues actions taken offline, and syncs when the connection returns.

Where it genuinely cannot work offline, it says so clearly rather than showing a spinner forever.

5. It responds instantly, even when the network is slow

Every tap should acknowledge within about 100 milliseconds — a state change, a highlight, a skeleton. Optimistic updates matter here: show the message as sent, reconcile in the background, and roll back visibly if it fails.

Perceived speed is a design decision as much as an engineering one.

6. It respects the battery and the data plan

Background location, aggressive polling and uncompressed images drain batteries, and users do check which app is responsible. An app in the top three of the battery screen gets deleted.

7. Notifications are worth receiving

The rule: a notification should be about something the user asked for or genuinely needs to know now. Marketing pushes dressed as alerts are the fastest route to being muted, then removed.

Give people real controls — categories, not just on and off.

8. It is accessible

Dynamic type support, so people who need larger text can still use it. Screen reader labels on every control. Tap targets at least 44×44 points. Contrast that works in sunlight.

Test it: turn your system font size up two steps. Does the layout survive?

9. It gets updated

Apps decay. Operating systems change, devices change, libraries need security patches. An app last updated two years ago signals abandonment to users and to the app stores.

Native, cross-platform, or web?

The right answer depends on what the app does:

• Native (Swift, Kotlin) — best performance and platform fidelity. Choose when the app is heavy on device features: camera, sensors, background processing, offline-first.
• Cross-platform (React Native, Flutter) — one codebase for both platforms. Choose when the app is mostly screens, forms and data, and speed to market matters more than squeezing the last frame.
• Progressive web app — no install, no store review. Choose when reach beats capability and you do not need push or deep hardware access.

Most business apps are well served by cross-platform. Reach for native when there is a specific reason, not by default. We build mobile apps both ways and the choice is worth arguing about at the start rather than discovering later.

The honest test

Give your app to someone who has never seen it, say nothing, and watch. Do not explain, do not help. Where they hesitate is your backlog, in priority order.

That single exercise finds more real problems than a month of internal opinion.