Mobile players scroll past RTP filters roughly three times faster than desktop players do. That's the headline finding from session recordings of 1.2 million casino lobby visits collected between January and March 2024, and it holds across game types, jurisdictions, and stake levels. The practical upshot: a filter that works as a discovery tool on a 27-inch monitor is, on a 6-inch screen, mostly decoration.

Why the same feature behaves differently on a phone

RTP filters aren't hard to use. They're hard to notice on mobile, and noticing is the whole job.

On desktop, the filter usually sits in a persistent left rail alongside provider, volatility, and theme. Your eye passes it every time you scan the lobby. On mobile, the same control collapses into a horizontal chip row or a "Filters" button tucked under the search bar. The player has to decide to look for it before they can use it.

Session data from the same study puts a number on that: 68% of mobile sessions never opened the filter panel at all, versus 31% on desktop. And of the mobile players who did open it, the median time before tapping anything was 1.4 seconds — barely enough to register that a panel appeared, let alone read the labels inside it.

The thumb-zone problem

There's a physical constraint underneath the behavioural one. Filter chips placed near the top of a mobile viewport sit outside the natural thumb arc for one-handed use. Players either reach awkwardly, or they don't reach at all. A control that requires repositioning your grip is a control most people will skip.

What players actually filter on — and what they don't

Here's where the RTP filter's mobile problem gets sharper. Operators tend to bundle it with volatility and max win, assuming players treat all three as a single "how risky is this?" decision.

The recordings suggest otherwise. When mobile players did engage with filters, the top three taps were:

1. Provider (41% of filter interactions)
2. Game category — slots, live, crash (29%)
3. Volatility (17%)

RTP-specific filtering accounted for under 6% of interactions on mobile, against 14% on desktop. Same games, same player pool, different device, less than half the engagement.

That gap is worth sitting with. It isn't that mobile players care less about return-to-player — the audience skews toward the same experienced players who use RTP as a rough guide. It's that on mobile, the cognitive cost of finding the filter exceeds the perceived benefit of using it. When the payoff is a marginal sorting improvement and the cost is a scroll, a tap, a panel read, and another tap, the maths stops working.

The design assumption that's quietly wrong

Most lobby templates are built desktop-first, then responsively compressed. The filter logic survives the compression; the discoverability doesn't. A chip row that reads cleanly at 1440px becomes a truncated label at 390px, and truncated labels don't communicate "this sorts by RTP."

Some operators have started surfacing RTP directly on the game tile instead — a small percentage badge, no filtering required. Early A/B data from two European brands showed a 22% lift in tile-level engagement when the RTP figure was visible without interaction, though it's too early to say whether that translates into longer sessions or just more taps.

The question operators haven't answered

If three-quarters of your mobile traffic never touches the RTP filter, is it a feature or a checkbox?

The honest answer is that nobody's measured the counterfactual. Removing the filter entirely might cost nothing on mobile. Keeping it might cost a little, if it adds visual noise to an already crowded lobby. And building it differently — tile-level badges, a swipeable RTP sort, a persistent toggle — is a real engineering cost with an unproven return.

What's clear is that the current setup serves desktop habits on a device that has none of them. The next round of lobby redesigns will either fix that or quietly drop the filter and hope nobody notices. Given how few mobile players are using it, most won't.