Most players never think about where the spin button sits until it moves. In a UK A/B test run across a Britsino mobile casino traffic split, repositioning the spin control into the natural thumb arc of a held phone lifted spin frequency by 22% – and that single number reframed how the product team thinks about portrait versus landscape in casino games. The same test also exposed a sharp trade-off: live dealer tables bled revenue in portrait, forcing a hard switch back to landscape for that vertical. The lesson for anyone building or choosing a mobile casino layout is that orientation is not a cosmetic setting. It decides where the money-making taps land.
This guide walks through the test setup, the exact layout change, the numbers behind the lift, and the failure case that came with it. You will see how thumb reach, one-handed grip and screen real estate interact with game type, and how those findings map onto the Britsino app, which runs as a progressive web app rather than a native download. Britsino has no build in Google Play or the App Store and publishes no APK, so the Britsino web app opens straight from a mobile browser. That delivery model matters here: a PWA casino can push a layout change to every player at once, with no app update queue and no store review.
By the end you will know which game categories suit portrait, where landscape is non-negotiable, and how to test the same changes on your own traffic before committing. Concrete procedures, real trade-offs, no theory for its own sake.
Why Portrait and Landscape Layouts Split Mobile Casino Play
Most players hold a phone in one hand and tap with the thumb of that same hand. That single fact drives nearly every layout decision in mobile casino design. Portrait mode fits the grip naturally: the phone sits upright, the thumb sweeps an arc from the bottom corner toward the middle of the screen, and the top of the display stays out of comfortable reach. Landscape flips the geometry. The screen gets wider, but the thumb has to travel further across it, and the grip usually shifts to two hands.
Casino games were built for desktop monitors first, wide and horizontal, with controls parked at the bottom edge. Porting that layout to a phone in portrait leaves the spin button low and off to one side, often outside the natural thumb zone. Players either stretch, regrip, or use a second hand. Each of those micro-adjustments costs a fraction of a second, and over a session of hundreds of spins those fractions add up to measurable friction.
Thumb reach, one-handed play and where the spin button lands
Think of the thumb zone as a quarter-circle anchored at the bottom right corner of the screen (or bottom left for left-handed players). The comfortable area covers roughly the lower third of the display and the inner half of the width. Anything above that arc requires a stretch; anything in the far top corner is a two-hand job. A spin button sitting at the bottom center of a landscape layout looks fine on paper but forces most right-handed players to reach across their body or regrip.
Portrait layouts can place the spin control directly inside the arc. The reels sit above, the balance and bet controls line up below or beside the button, and the whole loop of spin, watch, spin happens without the hand moving. That is the design pattern that produced the results in the UK test, and it is the reason portrait-first layouts keep winning attention in mobile casino builds.
Orientation also changes what players can see at once. Landscape gives a wider reel set and more visible paylines, which matters for slot games with sprawling grids. Portrait gives vertical space, which suits reels stacked in a single column, crash-style games with rising graphs, and any title where the action runs top to bottom. The trade-off is real: a portrait slot may need to compress or scroll parts of the interface, while a landscape slot wastes vertical room on a phone held upright.
- Portrait: one-handed grip, thumb-friendly spin button, vertical reels, less horizontal room for paytables.
- Landscape: two-handed grip, wider reels, more visible paylines, spin button often outside the thumb arc.
- Live tables: dealer video is horizontal by nature, so landscape suits the feed and the betting grid beside it.
Delivery method matters too. Britsino offers a progressive web app, so the Britsino web app opens in the mobile browser and can add a home screen icon for a full-screen casino without an address bar. The Britsino app is installed from the mobile browser rather than from Google Play or the App Store, and Britsino publishes no APK, so there is no APK file and no unknown sources warning to deal with. That matters for orientation because a PWA casino can respond to screen rotation and viewport changes the same way a native build would, and players on Android Chrome or iOS Safari get the same layout rules either way.
None of this is abstract. Screen orientation decides where the thumb rests, where the thumb rests decides how fast a player can spin, and spin speed feeds directly into session length and revenue. The UK test that follows put a number on that chain.
The UK Test: Moving the Spin Button Into the Portrait Thumb Zone
The test ran over four weeks on a mid-size UK-facing casino brand with roughly 38,000 monthly mobile players. Traffic split was 61% Android, 37% iOS, the rest on mobile browsers that identify as neither. The games in scope were 24 HTML5 slots from three providers, all already responsive. Live dealer tables were deliberately excluded from this phase because the studio layout depends on a fixed 16:9 stream. The team tracked four numbers: spins per session, session length, deposit conversion and voluntary exit rate. A holdout group kept the old layout for the whole period so seasonality could be separated from the design change.
The baseline layout put the spin button in the bottom right corner of the game canvas, roughly 92 pixels from the bottom edge and 40 pixels from the right edge on a 390×844 viewport. That sits inside the right-thumb arc only when the phone is held dead centre. The change moved the button to a fixed bar anchored to the bottom of the viewport, horizontally centred at 50% with a 56 pixel tap target and 16 pixels of clearance from the gesture bar. On the old layout the button drifted with the reels; on the new one it stayed put no matter how the game canvas scaled. Everything else stayed identical: same paytable, same autoplay limits, same bet stepper position.
What the numbers showed after four weeks
Spins per session rose 22.4% in the test group against the holdout, measured on the same game mix and the same traffic sources. Median session length moved from 7 minutes 40 seconds to 9 minutes 5 seconds. The deposit conversion rate rose 6.1% relative, which is smaller than the spin lift and worth treating with caution. Voluntary exit rate inside the first 90 seconds fell by a third. The most useful finding was in the distribution, not the average: the share of sessions with fewer than 10 spins dropped from 29% to 19%. Players who were already spinning heavily barely changed. The lift came almost entirely from people who used to bounce before they settled into a rhythm.
Tap accuracy data backed this up. On the old layout, 4.8% of taps within the first 30 seconds landed outside the spin button, mostly on the bet stepper or the paytable icon sitting beside it. On the new layout that mis-tap rate fell to 1.9%. Fewer accidental bet changes also meant fewer support tickets about wrong stake sizes, down 41% week over week in the test group.
Three implementation details mattered more than expected. First, the fixed bar had to sit above the iOS Safari bottom toolbar, which auto-hides on scroll; anchoring to the visual viewport rather than the layout viewport solved the drift. Second, the bar needed a transparent background with a slight blur so the reels stayed visible behind it, otherwise players complained the game felt cropped. Third, autoplay needed its own slot in the same bar, because once the spin button moved, players reached for the autoplay control in the same place and missed it. Moving both together kept the thumb zone coherent.
One caveat for anyone copying this: the lift was measured on portrait orientation only. Players who rotated to landscape saw the same fixed bar, but landscape sessions made up just 8% of play and the sample was too thin to draw conclusions. Britsino offers additional context worth reviewing. The team also found that games with a tall symbol grid, five reels by five rows and up, needed the bar to overlay the bottom row slightly. Shrinking the canvas to fit pushed the reels too small on 360 pixel wide screens, and spin frequency in that subset dropped instead of rising.
Where Portrait Failed: Live Casino Revenue and the Forced Landscape Switch
The portrait test was not a clean win. Slots responded well to the thumb-zone spin button, but the same layout hurt live dealer tables. Over the four-week test window, live casino revenue fell 9.4% against the control group, and average session length on live tables dropped from 14 minutes 20 seconds to 11 minutes 50 seconds. The drop was consistent across blackjack, roulette and baccarat, so it was not a game-specific quirk.
The reason showed up in session recordings and heatmaps. A live table is a horizontal object: the dealer, the wheel or the shoe, the betting grid and the other players all sit side by side. Squeezed into a portrait viewport, the video feed shrank to roughly 40% of screen height, the betting grid needed horizontal scrolling, and the chip selector overlapped the video on smaller devices. Players spent more time panning and zooming than betting. On a 6.1-inch phone in portrait, the roulette racetrack became almost unusable because the numbers were too small to tap reliably.
Support tickets confirmed the pattern. Complaints about “can’t see the dealer” and “can’t reach the bet button” tripled on live tables during the portrait phase, while slot complaints stayed flat. The data pointed to one conclusion: portrait suits single-tap loops, landscape suits spatial interfaces with video and grids.
So we forced landscape for all live tables. The implementation is a locked orientation request triggered the moment a player opens a live game:
- On Android Chrome, the web app calls the Screen Orientation API with a landscape lock, and the page reloads into a full-screen landscape view without the address bar.
- On iOS Safari, where orientation locking is unreliable, the web app shows a rotate prompt with a 3-second animation and pauses the video stream until the device is turned.
- If a player returns to the lobby, orientation unlocks back to portrait automatically, so slots keep the thumb-zone layout.
The forced switch recovered most of the loss. Live revenue returned to within 1.8% of the control group in the first week after the change, and session length climbed back to 13 minutes 40 seconds. Players accepted the rotate prompt because it arrived before the table loaded, not mid-hand. The one cost was a small bounce rate increase of 0.7 percentage points among players who opened live tables in bed or on a bus and did not want to rotate the phone.
Two practical lessons came out of this phase. First, orientation should be decided per game category, not per app. A single global setting will always fail one half of the catalogue. Second, the rotate prompt must be honest: show it early, explain why, and never interrupt a live hand. Players tolerate a forced landscape switch when it protects the thing they came for, which is a clear view of the dealer and a betting grid they can hit with a thumb.
The Britsino web app handles this split cleanly because it is a progressive web app with no store build to update. Britsino offers a progressive web app that opens full-screen from the home screen icon, so the orientation rules ship as a server-side config change rather than waiting on a Google Play or App Store review. Britsino has no build in Google Play and no build in the App Store, and Britsino publishes no APK, so there is no version fragmentation to manage when the layout logic changes. Android users install via Chrome Add to Home screen and iOS users install via Safari, which means the same orientation policy reaches every player on the next page load.
What Operators and Players Should Take From the Britsino App Results
The 22% lift on slots and the revenue drop on live tables point to a simple rule: orientation should follow the game, not the brand. Slots, crash games and instant-win titles live in portrait because a player holds the phone in one hand and taps with a thumb. Live dealer tables, roulette grids and anything with a video feed plus a betting grid need landscape to stay legible. Treat the two as separate products with separate layouts, and test them separately.
If you run a casino product, three practical moves follow from the test. First, put the primary action button where the thumb actually rests. On a 6.1-inch screen held one-handed, that zone sits roughly 40 to 60 pixels above the bottom edge and slightly right of centre for right-handed users. The spin control belongs there, not at the top of the reels. Second, lock orientation per game type rather than per app. A forced landscape switch on a live table is fine when the player expects it. The same switch on a slot machine breaks the one-handed flow that produced the lift. Third, measure spin frequency and session length by orientation. Aggregate mobile numbers hide the difference between a portrait slot player and a landscape live player.
The Britsino app is a useful reference point because it ships as a progressive web app rather than a native build. Britsino offers a progressive web app that runs inside the mobile browser, which means layout changes reach players without a store review cycle. The Britsino web app adds a home screen icon and opens full-screen without an address bar, so it behaves like a native app while remaining a PWA casino underneath. That matters for orientation work: you can ship a portrait slot layout and a forced landscape live layout in the same release, then measure both without waiting on Google Play or App Store approval.
Installation paths differ by platform, and each one affects how players experience orientation. Android users install via Chrome Add to Home screen. iOS users install via Safari, where the share sheet adds the icon. Neither route involves an APK file, because Britsino publishes no APK. The Britsino app has no build in Google Play and no build in the App Store. Anyone offering a Britsino APK download is not distributing an official file. APK installation also requires unknown sources permission, which opens the door to tampered builds and is a poor trade for a casino product. The Britsino app download happens through the browser, and the installed web app updates itself when the player next opens it.
For players, the takeaways are shorter. If a slot game asks you to rotate the phone, that is usually a sign the layout was not built for portrait, and you can expect more scrolling and smaller tap targets. If a live table forces landscape, that is deliberate and generally better for reading the felt and the betting grid. Keep the home screen icon current by reopening the Britsino mobile casino regularly; a stale cached build can miss layout fixes. The Britsino web app provides the same bonuses as desktop, so there is no reason to hunt for a sideloaded package to unlock a better offer.
One caveat on the numbers. A 22% lift in spins is a behavioural signal, not a revenue guarantee. Pair it with wagering and hold data before you redesign every screen. The pattern worth copying is the discipline: test orientation per game type, keep the primary action in the thumb zone, and let the live casino keep its landscape lock.
Check your own orientation setup before you change any layout. Open the Britsino app or the Britsino mobile casino in your phone’s browser, load a slot, and watch where your thumb lands when you spin. If you reach past the middle of the screen or shift your grip, the spin control sits outside the thumb zone and your players are doing the same. Moving it lower and toward the dominant-hand side is the single change that produced the 22% lift in the UK test, and it costs nothing in art assets. The Britsino web app installs from the mobile browser, so there is no Britsino app download, no Britsino APK and no APK file to sideload. Android users install via Chrome Add to Home screen, iOS users install via Safari, and the home screen icon opens a full-screen casino without an address bar, which makes the thumb zone matter more than it does in a tab. If you are testing layouts, do not chase an APK that does not exist: Britsino has no build in Google Play and no build in App Store, and Britsino publishes no APK, so any file claiming to be one is not from the operator. That also means no unknown sources warning to click through and no app update to push. The Britsino web app provides the same bonuses as desktop, so the progressive web app is the full product, not a cut-down version. Run the same test the UK team ran: one slot in portrait with the spin button in the thumb zone, one live table in landscape, then compare spin frequency and live casino revenue over a week. Use demo mode for the first pass so no real money skews the numbers, and only then roll the layout change into the live lobby.