When should a primary button be the only one on the screen?

A primary button should stand alone when the view has one clear action you want users to take and any competing button would dilute it. The test is simply whether there is truly one main action; when several actions carry similar weight, the right answer is one primary plus quieter secondaries, not two or three buttons all styled to dominate. One primary per view keeps the path obvious, because emphasis is a finite resource and giving it to a single action is what makes that action feel like the next step.

The logic is that a primary style works by contrast, so its power comes from being the only thing on the screen wearing it. The instant a second button is styled with the same prominence, the two cancel: the eye cannot tell which one the design considers the goal, and the visitor has to stop and decide what the page should have decided for them. Emphasis spread across many buttons is emphasis spent, and the result is a screen that looks busy and decisive while actually being undirected. A single primary, by contrast, reads as a recommendation, and a recommendation moves people forward.

A checkout summary makes the case plainly. The whole view exists to get the customer to place the order, so “Place order” should be the lone primary button, bold and unmistakable, while “Edit cart” and “Add promo code” sit quietly as secondary or text links. If all three were styled as primary, the customer’s eye would bounce between them and the momentum toward purchase would stall, because three equally loud buttons make the customer pause to choose where to look when the design should have already chosen for them. The same holds on an onboarding step or a sign-up form, where “Continue” or “Create account” is the one action the screen is built around and everything else, like “Skip for now” or “Log in instead,” belongs at a lower volume. Contrast all of this with a record-detail screen where editing, duplicating, and exporting are roughly equal, ongoing tasks; here there is no single main action, so one primary would misrepresent the screen, and the honest design is a set of evenly weighted secondary buttons with no primary at all, or one primary only if the product really does want to push a particular path.

Here is the exception: “one primary” is a rule about emphasis, not a quota of buttons. A view can hold many buttons and still have one primary, because the other buttons are demoted, not deleted. And a view can legitimately have no primary when no action genuinely outranks the rest, since inventing a primary where none exists is its own kind of distortion. The failure to avoid is styling several buttons as primary so they all stand out, which guarantees that none of them does.

When you lay out a view, ask whether there is one action you most want the user to take. If there is, make that the only primary and demote everything else to secondary or quiet. If two or three actions are genuinely equal, give them all secondary weight rather than promoting them all, and accept a screen with no single primary when that is the truth of the task. Spend your emphasis on one action at a time, and the path through each view will stay clear.