The whole room in a hand: three ways in

A casino lobby used to be a place you visited; now it is a tab, an icon or an installed web app that lives beside your messages. Three routes carry almost everyone in. The mobile browser needs nothing fitted: type an address, log in, and the catalogue loads in a tab you can close. The downloaded app sits on the home screen, opens straight into the account and holds a session between visits. The progressive web app, the third route, installs from the browser itself and behaves like an app without a trip to any store.

The model this page works from puts browser play at 54 per cent of mobile sessions, downloaded apps at 38 per cent and progressive web apps at the remaining 8 per cent. Those are modelled shares for a mid-market mix, an assumption built for arithmetic rather than a measured census, and the chart draws them exactly as set.

What the routes share matters more than what separates them. The account is the same whichever door you use: one balance, one bonus wallet, one set of wagering requirements, one expiry clock. A package claimed on a laptop follows the account onto the phone, and the phone’s session burns the same wagering down at the same rate. The route changes the packaging, meaning screen size, login method and how far notifications can reach. It does not change the terms, the payout window or the edge behind the games. That is why the route discussion here stays short and the arithmetic goes on the things a route cannot move: stake sizes, turnover, expiry and the licence standing behind the whole arrangement.

One practical difference deserves a flag before the next section. Browser play starts fastest and leaves nothing on the device. An app is quicker on the second visit and can use features a tab cannot. A progressive web app sits between the two, installed but lightweight. Readers who deposit rarely and play briefly model out comfortably on the browser alone; readers who settle into long sittings tend to value the resume. Neither preference moves a single number on this page.

App against browser: what actually changes

Run the same account through the app and through the browser and the terms do not move. Wagering multipliers, maximum stakes while a bonus is active, game weighting, expiry timers, minimum deposits: each of those is written into the offer’s terms and attaches to the account, not to the doorway. A package claimed on a desktop and played on the phone carries precisely the wagering it carried at the till. The reverse holds as well: claim on the phone, continue on the laptop, and the same clock runs.

Payouts follow the same logic. A withdrawal request enters the same queue whichever screen raised it, and what sets the wait is the operator’s processing routine and the licence behind the account, never the channel. The comparison below makes the split visible. The British rows in the cluster print one to two banking days on the quicker lines and one to three on the rest, while the offshore rows run one to five. Those are category-typical ranges compiled from published terms, not quotes of any single promotion, and the note under the table carries that warning in full.

Where the app genuinely differs is friction. Biometric login shortens the trip back in, a stored session resumes where it stopped, and updates arrive through the store rather than a browser refresh. None of that touches a wagering multiplier. What it touches is pace: an app makes it marginally easier to start again quickly, which matters when a session model like the one further down assumes you stop when the sitting ends. The terms never change; the pull to skip the stop can. That trade belongs to the reader, and the safer gambling note at the foot of the page names the tools built for it.

Figures are category-typical ranges compiled from operator-published terms at the time of writing, not quotes of any single promotion. UKGC-licensed rows are the British baseline shown for comparison; none of them are claimable at the offshore offers modelled on this page. Verify every term on the operator’s own page before you take it.

Payment rails on a phone: wallets, tokens and taps

Money moves on a phone across a short list of rails, and the comparison table lists them row by row rather than as promises. A debit card is the default on the British rows. PayPal appears on many of them, and the reason is structural rather than sentimental: PayPal requires gambling merchants to hold the licence for the markets they serve, so its availability tracks UK licensing instead of operator taste. Apple Pay shows up on several rows too, working as a device wallet that stands in front of the underlying card, confirming with a fingerprint or a face scan and handing the merchant a token rather than the raw number. The card’s own limits, statements and dispute routes still apply underneath the wallet.

The credit card is the rail to watch. GB-licensed operators have been barred from accepting them since April 2020, a Gambling Commission rule rather than a retailer preference. An offshore account sits outside that ban, and card acceptance that a licensed cashier cannot offer can still appear at the other end of the market. Read that as a difference in protection rather than a perk: the ban exists because borrowing to gamble was judged harmful, and a phone makes borrowing frictionless.

Tap payments compress a deposit to a fingerprint, which is convenient and deserves respect. The session model below assumes fifty-pence stakes partly for this reason: small units are the honest way to price play, and a wallet that strips out friction makes the small unit easier to hold to. Whichever rail you choose, the cashier page on the operator’s own site is where limits, fees and accepted currencies get confirmed, because rails shift more often than terms do.

A session modelled: fifty pounds, four sittings

The calculator below runs a session model, and the prefill comes straight from the brief this page was built on: a £50 bankroll, £0.50 stakes, a 3 per cent house edge assumption and four sessions. None of those numbers is advice. They form a deliberately small frame chosen to show what the arithmetic does.

The assumptions deserve stating plainly. The bankroll is the total you are prepared to put at risk across the four sittings. The stake is the unit per spin or per hand. The house edge is the modelled share of each pound staked that the games keep on average over the long run; 3 per cent is a mid-range assumption for a mixed lobby, heavier than blackjack, lighter than many slots, and a statement about the mix you play rather than a measurement of any catalogue. A session, in this model, means turning the bankroll over once: a hundred half-pound stakes.

Run it forward and the totals are unglamorous. One session stakes £50. Four sessions stake £200. At a 3 per cent edge, the expected cost of the four sittings is £6. That is the modelled price of the play, not a prediction of any single evening. Individual sittings scatter far and wide around the line, some finish ahead, and the purpose of pricing the average is to stop a good evening being mistaken for a system. The edge does not negotiate, and it does not hurry either.

What the model buys is a unit of comparison. Wagering requirements arrive as multipliers of a bonus or of winnings, and a multiplier only means something once a stake size turns it into time. At £0.50 a stake, £100 of wagering is two hundred spins; at £2 a stake, the same requirement is fifty. The multiplier is fixed, the stake is a choice, and the choice is where this model earns its keep.

Reset the prefill to your own figures and the same arithmetic follows. Keep the edge assumption honest: adjust it if your mix runs heavier or lighter than the mid-range, and resist the temptation to set it at zero, since the edge is precisely what the model is pricing.

Notifications and the expiry clock

A phone can buzz, and the buzz is the newest part of this chain. Operators with apps, and some with progressive web apps, can send push notifications: deposit nudges, promotion announcements and, occasionally, a countdown reminder as a bonus expiry approaches. The reminder is real and the countdown is real. What the notification is not is the source of either. Expiry lives in the bonus terms, printed before you opt in, and the screen that buzzes has no power to extend it. The honest habit is to read the expiry line at claim time and diarise it yourself, treating any notification as a courtesy copy.

The direction of the channel deserves equal honesty. A push feed is a marketing rail first and a service rail second. The offers it carries sit under the advertising rules that govern gambling promotion in Britain, including the CAP Code’s requirements on protecting minors and presenting bonuses honestly, but those rules govern how an offer is described, never whether taking it suits your model. A countdown that arrives by push is still a countdown to a term you should already have read in the terms.

There is a quieter effect too: availability. A lobby that lives on the home screen and pings on a Friday evening makes restarting easier than a bookmark buried in a browser tab. The session model above prices a sitting at a hundred stakes; the notification feed knows nothing of the sitting and will happily suggest a fifth. Deciding in advance how many sittings the bankroll covers, then letting the model rather than the buzz set the boundary, is the entire trick. Notification settings live in the operating system and in the app, both configurable, and switching the marketing ones off costs nothing at all.

Route by route: the three-line check

Whichever way in you choose, the same three lines do the work. The first is identity: whose site is this, and does the name on the page match an entry you can find on the public register of licence holders. The second is money: minimum deposit, currencies, the rails set out in the comparison table, and the payout window you are being asked to model. The third is the offer: wagering multiplier, maximum stake while a bonus is active, game weighting, and the expiry clock the previous section discussed. The table compresses the route-specific version of that check into three rows, one per way in.

None of the three lines needs a download, a deposit or an account, and all three can be run from the phone itself in the time a store page takes to load. The rows are deliberately blunt. They form a checklist, not a review, and they exist so the comparison happens before the deposit rather than after it.

What the licence conditions do on a small screen

Every mechanic described so far runs identically on every screen, and the licence conditions behind an operator travel the same way. Operators serving British customers under a Gambling Commission licence must follow the Licence Conditions and Codes of Practice, which carry social responsibility requirements on customer interaction and product design. Those requirements are channel-blind. They bind the operator rather than the doorway, so the interaction thresholds and the product-design expectations apply to a phone session exactly as they apply at a desk. The practical traces are the ones readers already recognise: deposit-limit tools inside the account and a self-exclusion facility the operator must offer alongside the national scheme.

An offshore app or site brings no equivalent. Whatever licence it claims, wherever it is issued, it imposes no such code, and the protections in the previous paragraph do not transfer. The page keeps that asymmetry visible rather than burying it: the licence note printed beside this article states the trade-off plainly, and the comparison table splits its rows so the two licence classes never blur. A reader weighing a two-day modelled payout on a British baseline row against a five-day one at the offshore end is weighing processing speed. The licence column is where the rest of the difference lives.