Apple’s age-rating questionnaire used to let a lot of bingo operators off the hook. You ticked “gambling” or you did not, and if your cashier lived in a webview the answer was often a fudge. That has changed. The questionnaire now asks about simulated gambling and real-money gambling as two separate things, and the wording is precise enough that a bingo app showing free demo reels next to a paid bingo bonus can end up with a 17+ rating even when no real money changes hands inside the app itself. For anyone building or reviewing UK bingo apps in 2026, this is the single most consequential ratings change since Apple started enforcing its gambling declarations properly.
What Apple’s questionnaire now separates, and why it matters for bingo
The old model was blunt. If your app contained gambling content, you declared it and took the rating hit. If it only contained a free-play bingo game with no cashier, you could argue it was a game and rate it 12+ or even 9+. The new questionnaire splits the question in two: does the app contain simulated gambling, and does the app contain real-money gambling? Those are separate ticks with separate consequences, and Apple’s review team reads them against what the app actually does, not what the operator says it does.
For a bingo app this matters because the two features sit next to each other by design. A typical UK bingo app opens on a lobby with demo reels, a free ticket, a practice room, or a “try before you deposit” flow. Two taps later you are in the cashier, or in a webview that hands off to the operator site to complete a deposit. Under the old questionnaire an operator could tick “no gambling” on the grounds that the money side lived in a browser. Under the new one, the simulated gambling tick alone is enough to trigger scrutiny, and once a reviewer sees a paid bingo bonus advertised alongside the free reel, the real-money tick follows.
The practical result is a 17+ rating for apps that never take a card inside the binary. That is not a mistake in Apple’s logic. Simulated gambling is treated as a gateway experience, and the review team is not interested in the technical boundary between a native screen and a webview. If a user can move from free bingo to paid bingo inside the same app session, Apple treats the app as containing both.
How the two ticks interact in review
Reviewers do not assess the ticks in isolation. They open the app, follow the lobby, and check whether the free-play content is a genuine standalone game or a funnel into the cashier. A demo reel that sits behind a “play for real” button, or a free ticket that expires into a deposit prompt, reads as real-money gambling with a simulation wrapper. The operator gets the 17+ rating and, in some cases, a follow-up question about whether the webview cashier is disclosed in the app description.
Native apps are installed from the App Store or Google Play, and both stores now expect the age rating to reflect the worst-case path through the app, not the most innocent one. If a reviewer can reach a deposit screen from the home tab in under three taps, the rating should assume they will. Operators who argue otherwise tend to lose the argument and the review slot.
The gap between native apps and mobile sites, and what reviewers actually see
This is where the ratings change collides with how UK bingo operators have built their products. Some run full native apps, some run a mobile site with a home screen bookmark, and some run a native shell that loads the operator site in a webview. Apple’s questionnaire does not care which architecture you chose. It cares what the user experiences, and a webview cashier is still a cashier.
Take the split across the market. 888 Ladies offers an iOS app, built as a native download with the lobby and cashier inside the binary. Betfred Bingo offers an iOS app on the same model. Betfair Bingo offers iOS and Android apps. Barbados Bingo offers a mobile site rather than a store download, which sidesteps the App Store rating question entirely but pushes the age-gate responsibility onto the browser and the operator’s own T&Cs. Each route has a different exposure to the new questionnaire, and the native operators carry the most.
The webview-only operators are the interesting case. Their app contains simulated gambling in the form of demo reels, and it contains real-money gambling in the form of a cashier that loads in a browser frame. A year ago the argument “the cashier is not part of the app” might have held. It does not now. Apple’s reviewer sees a screen that takes a deposit, and the ratings questionnaire has a specific tick for that. The 17+ rating is the correct outcome, and the operator has to accept it or strip the cashier out of the app entirely.
Why the free demo reel is the trigger, not the cashier
Operators tend to assume the cashier is what pushes them to 17+. In practice the simulated gambling tick does most of the work. A free demo reel is exactly what Apple means by simulated gambling, and once that box is ticked the reviewer starts looking for the real-money counterpart. If they find it, the rating is 17+. If they do not find it, the app can sometimes sit at 12+ with a simulated gambling declaration, but that outcome is rarer than operators expect because most bingo apps, as covered at https://bingodaily.uk/bingo-apps/, monetise somewhere.
The cleanest position for a bingo app that wants a lower rating is to separate the free-play product from the paid product at the app level, not just at the screen level. That means no deposit prompt in the demo flow, no cross-sell from the free reel to the cashier, and a clear statement in the app description about what the app does and does not contain. Few operators take that route because the funnel is the business model.
What the 17+ rating changes in practice for UK bingo apps in 2026
A 17+ rating is not a death sentence. Plenty of bingo apps carry it and rank well. What changes is the surrounding compliance work. Apple expects the app description, the screenshots, and the in-app disclosures to be consistent with a 17+ gambling product, and it expects the operator to have safer play tools visible rather than buried. Deposit limits are set in the player’s account, and reviewers will look for the path to that setting. Links to BeGambleAware, GamStop, and GamCare are treated as a positive signal, not a box-ticking exercise.
The ratings change also affects how operators market the app. A 17+ rating restricts the app from appearing in some family and kids categories, and it changes how the app can be promoted in search. Operators who rely on broad discovery through the App Store need to plan for a narrower audience. The upside is that a 17+ rating is honest, and honest ratings tend to survive review cycles without the back-and-forth that costs weeks.
There is a knock-on for promo codes and welcome offers. A code like WELCOME2026 is used as a promo code in bingo apps to unlock a welcome offer, and the offer terms need to be visible before the user reaches the cashier. Apple’s reviewers check that the T&Cs are reachable from the offer screen, not just from the operator site. The same applies to codes like GOLD50 and BINGO100, which are common entry points in UK bingo apps 2026 and which reviewers will test if they appear in the screenshots.
Storage, updates, and the cost of getting the rating wrong
An incorrect age rating is one of the few review failures that can pull a live app from sale. If Apple decides your declared rating does not match the content, the app can be removed pending a resubmission, and the resubmission queue is not fast. For an operator with a deposit-driven funnel, a week off the App Store is a measurable revenue hit. The fix is unglamorous: audit the app against the questionnaire, tick simulated gambling if there is a demo reel, tick real-money gambling if there is a cashier or a webview deposit, and accept the 17+ rating.
The other practical cost is device-side. Native apps take storage space, and app updates push through the store on Apple’s schedule, not the operator’s. A mobile site with a home screen bookmark updates instantly and takes almost no space, which is one reason Barbados Bingo and similar operators stick with the mobile site model. The trade-off is that a mobile site does not get the App Store distribution, and it does not get the ratings question at all. Operators weighing the two routes should be clear that the native app buys distribution at the cost of a 17+ rating and a slower release cycle.
Mobile data allowance is a smaller factor but worth noting. A native bingo app with animated reels and lobby assets can chew through data on a 4G connection, and reviewers do test on cellular. A lean app that loads the lobby quickly and defers heavy assets is more likely to pass a first review than one that stalls on a slow connection.
For anyone reviewing bingo apps, the ratings change is a useful filter. Bingo Daily reviews best bingo apps UK and treats the age rating as a signal of how the operator has handled the simulated-versus-real question. An app rated 17+ with a clear safer play section and visible deposit limits is usually a better-run product than one that has squeezed into a lower rating by hiding the cashier in a webview. The rating is not a mark of quality, but it is a mark of honesty, and honesty tends to correlate with the rest of the operation.
The practical takeaway for operators is to stop treating the ratings questionnaire as a formality. Read the simulated gambling and real-money gambling ticks as two separate questions, answer both honestly, and design the app so the answer is defensible. If the demo reel feeds the cashier, the app contains both and the rating should say so. If the app is a standalone free-play game with no deposit path, say that too, and be prepared to show the reviewer the absence of a cashier. For players, the advice is simpler: check the age rating before you download, read the T&Cs on any welcome offer before you enter a code like WELCOME2026, set a deposit limit in your account on day one, and use GamStop or BeGambleAware if the free-play side is doing more work than it should. A 17+ rating is a label, not a warning, but it is a label worth reading.