On a phone, a desktop banner becomes a takeover. It covers the article, the product, sometimes the entire first screen, and offers a giant accept button and a grey whisper of alternatives. Every usability instinct the visitor has says tap the big thing and make it stop.
Mobile consent design is where dark patterns stop being theoretical. The constraints are real, screen space is scarce, but the honest version fits fine when someone designs for the phone first instead of shrinking the desktop banner and hoping.
Size and placement that respect the screen
A bottom anchored sheet that occupies a third of the screen or less lets the page stay visible behind the decision. That visibility matters: the visitor can see what they are deciding about, and the site does not feel held hostage.
Leave the close and scroll behaviour honest. A banner that follows the reader through the whole page until answered manufactures consent through exhaustion. Present it clearly on arrival, then get out of the way of the content for people who defer.
Equal choices under one thumb
Accept and reject should be the same size, in the same row or stacked with equal weight, reachable in the same number of taps. On mobile the tap count is the whole argument: one tap to accept and three to reject is a steering pattern, whatever the desktop version looks like.
Manage options can sit behind a clearly labelled settings button of similar prominence. What it cannot be is the only route to saying no, hidden in smaller type under a wall of reassuring copy.
Copy that survives small screens
Mobile banners need shorter text, which forces honesty. Two sentences: what is collected, and where the full detail lives. If the short version cannot say it plainly, the long version was hiding something anyway.
Type size is an accessibility issue here, not a style one. Consent text that needs pinching to read is not informed consent in any practical sense. Set a readable minimum and let the banner grow a little instead of shrinking the words.
Testing on real devices
Test the banner on the smallest common phone in your analytics, in landscape and portrait, with the keyboard of real life: one hand, sunlight, a train. Check that nothing overlaps, that the reject path works by thumb, and that the banner never covers its own buttons.
Also test what happens after the choice. A settings link buried in a mobile footer menu is a promise nobody can keep. The change my choice path needs the same device testing as the original banner.
Related reading
These earlier guides go deeper on connected questions: SMS Marketing Consent: Keeping Proof That Survives a Complaint Text message marketing runs on stricter consent rules than email in many markets. What proof to capture at signup, how double opt in helps, and records that answer a complaint., How Consent Travels When You Switch Email Platforms Migrating an email list is a consent problem disguised as a data problem. Which records must move, what must never be imported, and warming up without burning trust., and Cookiebot Alternatives: A Practical Comparison A practical way to compare consent platforms side by side: blocking, records, pricing units, design control, and support, with a shortlist method any team can run..
Frequently asked questions
Can a mobile banner have accept on the first screen and reject in settings?
That imbalance is a recognised steering pattern. Reject should be available at the same level and with the same effort as accept. Settings can hold granular categories, but the plain no must sit beside the plain yes.
How much of the screen can a consent banner cover?
There is no magic percentage, but it should leave the page visible and usable in context and never block its own controls. Bottom sheets covering roughly a third of the screen are a common workable pattern. Full screen takeovers invite challenge and resentment.
Should mobile consent remember the choice across devices?
Choices are normally stored per browser or device, so a visitor may be asked again on a new phone. That is acceptable and expected. What matters is that each ask is honest and that choices are respected and easy to change on each device.
Does a sticky banner that follows scrolling count as pressure?
It can. A persistent banner that obstructs content until answered leans toward coerced choice, especially if it covers content or controls. A compact banner presented on arrival, with a persistent settings link afterwards, is the calmer pattern.