Award-winning mobile app UX: the patterns that score, and the ones that don't
What award-winning mobile app UX has in common: one-handed reach, interruption tolerance, honest permissions, offline behaviour and motion that means something. Written from the scorecard.
Award-winning mobile app UX rarely wins on its visual design. Phones are used in the dark, one-handed, on a train, at 4% battery, by someone who is also talking to a child. Apps that score well are the ones designed for that person rather than for the simulator.
Six things editors keep finding in the entries that score highest.
1. Everything important is inside the thumb's reach
Phone screens keep growing; thumbs don't. On a modern handset, the comfortable arc is the bottom third and the middle of the screen. Primary actions in a top-right corner are a desktop habit that survived a port.
- Primary action at the bottom, always. If it must sit in a header, duplicate it.
- Destructive actions deliberately out of reach — the one time distance is a feature.
- Sheets over full-screen modals: they keep context visible and their controls land where the thumb already is.
- Nothing critical in the very top corners on a large device, unless there is a second way to get it.
2. It survives interruption
A mobile session is interrupted by definition. A call arrives, an app is swiped away, the network drops in a lift. The question an editor asks is: what happens to half-entered work?
- 01
Draft is kept
Locally, immediately, without a save button.
- 02
State is restored
Same screen, same scroll position, same field focused.
- 03
Conflicts are explained
If the server moved on, say so in words and offer a choice.
- 04
Nothing is lost silently
The worst outcome is data disappearing with no message.
This is the single most common gap between apps that feel professional and apps that feel fragile. It's also invisible in screenshots, which is why it needs to be in your case study.
3. Permissions are asked for at the moment they make sense
Three permission dialogs on first launch is a pattern from 2014 and it still costs apps their best users. The apps that score well ask in context: the camera permission when the user taps to add a photo, notifications after the user has set something worth being notified about.
Costs you
- Every permission requested at launch
- A system dialog with no explanation first
- Notifications requested before any value is delivered
- No path back after a denial
Earns you
- Each permission at the moment it's needed
- One sentence of why, before the system prompt
- A working app for people who say no
- A clear way to change their mind later
4. Offline is a designed state, not an error
For travel, field-service, transit and health apps, offline isn't an edge case — it's Tuesday. The strongest entries treat connectivity as a spectrum: full, degraded, queued, offline. Each has its own affordances and its own honest message.
Queued actions with a visible queue, cached content with a timestamp, and a sync indicator that distinguishes "saved on this device" from "saved for everyone" will lift interaction and feedback scores more than any animation.
5. Motion carries meaning
Motion in a scoring app does one of three jobs: it shows where something came from, it holds attention across a change of context, or it confirms that an action landed. Motion doing none of those is decoration, and decoration in the path of a frequent task is a tax.
- Navigation transitions4200–300ms, interruptible, directional — they teach the structure.
- State confirmations4Under 150ms. A confirmation that takes a beat feels like a lag.
- Skeletons3Only when the wait is genuinely over ~300ms; otherwise they add flicker.
- Decorative flourishes1Charming once, then permanent. Never on a task done daily.
6. It works with the accessibility settings already switched on
This is where most mobile entries lose points, and it takes an afternoon to find out. Turn on the largest dynamic type setting and open the app. Turn on the screen reader and try the main task. Turn on reduce motion. Increase contrast.
- Dynamic type: does the layout reflow, or does text clip? Fixed-height rows are the usual culprit.
- Screen reader: are icon-only buttons labelled? Is the tab bar announced with position? Do sheets trap focus correctly?
- Reduce motion: are transitions replaced with fades, or ignored entirely?
- Touch targets: 24×24 CSS pixels is the WCAG 2.2 AA minimum; 44pt is the platform guidance, and closer to what thumbs need.
Entering a mobile app
Mobile Experience has subcategories for consumer, fintech, health, commerce and productivity apps, and editors install the app rather than judging screenshots — so store links matter as much as the screens you send.
Send the states, not the marketing shots: the first-run empty screen, the offline state, a permission prompt in context, and the app at the largest type size. That last one alone puts you ahead of most entries. Enter your app.
Notifications: the most abused surface on the phone
Notifications are the one part of a mobile product that reaches into someone's life uninvited, and the entries that score well treat that as a design responsibility rather than a growth lever.
Loses trust
- Re-engagement pushes with no new information
- One notification per event, unbatched
- All-or-nothing permission with no granularity
- Marketing disguised as a transactional alert
Keeps it
- Only what the person would act on now
- Batched digests at a time they chose
- Per-category controls, in the product not the OS
- Clear separation between service and marketing
App store presence is part of the experience
Editors install from the store, which means the listing is the first screen of your product. Screenshots that show real states rather than slogans, a description that says what the app does in its first line, and an honest "what's new" all set expectations that the app then has to meet — or not.
It's also where the accessibility and privacy labels live, and editors read them. A privacy label that contradicts what the app asks for in its first session is a finding.
The one-handed audit
Before you enter, do this: hold the phone in your non-dominant hand, stand up, and complete the main task while walking. It sounds silly and it finds more real problems than a heuristic review — reach, target size, accidental dismissals, text too small at arm's length, and the moment where you need a second hand.
Questions we get asked
Do we need to submit both iOS and Android?
Submit the platform where the design work happened, and say what's different on the other. If the achievement is genuine parity across both, say that explicitly — it's a harder claim and editors will check it.
Does a mobile web app count as a mobile entry?
Yes, if mobile is how it is used. Mobile Experience is about the experience on a phone, not about the packaging technology.
How do editors test an app that needs a real account?
Tick reviewer access on the entry and we arrange test credentials. For apps with a paid tier, a sandbox account with the paid features enabled is the most useful thing you can give.
How much does the app store listing matter?
It matters as the first screen. Editors install from it, so the gap between what it promises and what the app delivers shapes the first impression — which shapes everything after it.
Is dark mode expected?
Not required, but if you ship one it will be tested — and a dark mode with contrast failures costs more than no dark mode at all.
- mobile
- ios
- android
- patterns
Written by
The UXE editors
The team that selects the work, uses it, scores the seven criteria and writes every verdict on this site.
Keep reading
Craft & practice5 min read
Interaction design that earns its motion
Interaction and feedback is one of the seven UXE criteria — and the one most often mistaken for animation. What editors score: response times, state changes, undo over confirmation, and motion that does a job.
The UXE editors
Accessibility6 min read
Accessibility scoring: exactly what editors check, in the order they check it
Accessibility is one of the seven criteria on every UXE entry, in every category. The tests editors run in the first ten minutes, what an honest conformance claim looks like, and why disclosed gaps raise a score.
The UXE editors
Craft & practice6 min read
What separates the best SaaS dashboard UX design from the rest
The patterns behind the best SaaS dashboard UX design: default views that answer a question, density that respects real data, states that are designed, and the performance budget nobody talks about.
The UXE editors