The primary action button is not a decorative element at the bottom of the screen. It completes the user’s decision and tells them what will happen when they tap it. If the label is vague, the colour doesn’t stand out from other elements or the loading state is unclear, the interface creates doubt at exactly the critical moment — before paying, submitting a request or confirming a booking.
In audits we see that button problems rarely have to do with colour, the thing people argue about most. Far more often they lie in the label, the states and the behaviour on a slow network: duplicate orders, “dead” buttons with no explanation, entered data disappearing. Below is how we design the primary action, which numeric benchmarks we use and what we always test.
One action, one emphasis
It should be clear on every screen what the main outcome is. If two buttons look equally prominent, the user spends time comparing them. If there is a secondary action, it should be visually quieter — an outlined or text button — but not invisible. Destructive actions such as “Delete” or “Cancel order” should be separated from the primary one and marked with the error colour.
Material Design 3 builds hierarchy through button types: filled for the primary action, tonal or outlined for secondary ones, text for the least important. Apple’s Human Interface Guidelines follow the same logic: a screen should have no more than one strongly emphasised button, and its style signals how important the action is.
The label: a verb and a consequence
“Pay ₴450”, “Book for 14:30”, “Send request” describe the consequence far better than a generic “Next” or “OK”. The user sees exactly what will happen and doesn’t have to re-read the screen.
- Start with a verb: “Save”, “Add”, “Confirm”.
- Add the object or amount if it removes doubt: “Pay ₴1,200”.
- Avoid technical terms: “Submit”, “Execute request”.
- Keep it short — two or three words — so it isn’t truncated with large fonts or long translations.
- Keep the label consistent with the heading and confirmation: if the button says “Book”, the message says “Booking confirmed”.
Size, contrast and placement
Buttons come with concrete numeric requirements, and they belong in the design system rather than being checked by hand on every screen.
| Parameter | Benchmark | Source |
|---|---|---|
| Touch target on Android | at least 48 × 48 dp | Android accessibility guidelines |
| Touch target on iOS | at least 44 × 44 pt | Apple Human Interface Guidelines |
| WCAG 2.2 minimum target size (AA) | 24 × 24 CSS px or sufficient spacing | WCAG 2.5.8 Target Size (Minimum) |
| Button text contrast | at least 4.5:1 for normal text | WCAG 1.4.3 |
| Button boundary contrast against background | at least 3:1 for UI components | WCAG 1.4.11 Non-text Contrast |
| Spacing between adjacent actions | 8 dp or more | Studio benchmark |
On mobile we usually anchor the primary action at the bottom, within easy reach of the thumb, and make sure the keyboard doesn’t cover it. If the form is long, the button can stick above the keyboard or appear once the user scrolls to the end — what matters is that nobody has to hunt for it.
Button states
| State | What the user sees | Typical mistake |
|---|---|---|
| Enabled | Accent colour, clear label | Looks like other elements on the screen |
| Disabled | Muted appearance and an explanation of what is missing | A “dead” button with no hint at all |
| In progress | An indicator inside the button, repeat taps blocked | Button stays active, the request is sent twice |
| Success | Confirmation and the next step | A silent screen change with no feedback |
| Error | A clear message, data preserved, retry possible | A cleared form and a technical error code |
There are two schools of thought on disabled buttons. One disables the button until the form is complete. The other keeps it active and shows errors after the tap. For long forms we more often choose the second: the person taps, sees which field was missed, and focus moves there. A disabled button with no explanation forces people to guess.
Slow networks and double taps
Don’t change a field or button in a way that leaves the user unsure whether the request has already been sent. For file uploads or slow networks, block repeat taps, keep the data and show progress. On the API side, pass an idempotency key: even if the request does arrive twice, the server creates one order, not two. In our experience, double payments and duplicate requests are the most expensive consequence of a poorly designed “in progress” state.
Step-by-step check
- Read only the button labels in a scenario in sequence: do they make clear what is happening?
- Check that every screen has one distinct primary action.
- Turn on a slow network and tap the button several times quickly.
- Cut the connection mid-request: what does the user see, and is the data preserved?
- Go through the scenario with TalkBack and VoiceOver: the button has a clear name and state.
- Set the system font to maximum: the label isn’t truncated and the button doesn’t disappear.
- Check visible focus when navigating with a keyboard or switch access.
Common mistakes and checklist
- Several equally prominent buttons on one screen.
- A generic “Next” where the action has consequences: payment, submission, deletion.
- A destructive action next to the primary one with no confirmation or undo.
- An icon without text as the primary action.
- A button covered by the keyboard or the system navigation bar.
Before release we check that: the label describes the consequence; the touch target is at least 48 dp / 44 pt; contrast meets WCAG; repeat taps are blocked during a request; an error doesn’t wipe data; and the screen reader announces the button correctly. If the button completes a form, check the form itself too — see “Mobile forms: how to reduce data-entry errors”.
Android quality guidance recommends consistent standard patterns. Test not only taps but errors, slow responses, resubmission and going back — we covered back behaviour in our article on navigation. A good button doesn’t just lift conversion — it reduces uncertainty and accidental actions.
Sources: Android Developers: What a great user experience looks like; Android Developers: Make apps more accessible; Apple Human Interface Guidelines: Buttons; Material Design 3: Buttons; WCAG 2.2: Non-text Contrast; WCAG 2.2: Target Size (Minimum).
Originally published on the Mosmox journal: The Primary Action Button in Mobile UI: How to Make It Clear

Top comments (0)