Top Mobile casinos for Australian readers

The two ways a mobile casino reaches your phone

Two routes exist, and the marketing language used to sell them does not separate them. The first is the browser lobby: you open the operator in whichever browser ships on the handset, sign in, and play inside a tab. Nothing is installed, the address bar stays on screen, and the lobby shares vertical space with the browser’s own controls. The second is the home-screen route: the same site, added as an icon through the browser’s own menu, which then launches the lobby full screen with no address bar in view. Both load the same pages from the same domain, over the same connection, into the same account. What differs is how the operating system frames them, and that framing is what this page is about.

The installed icon is a progressive web app. The operator publishes a small manifest file describing an icon, a name, a start address and a display mode, and the browser uses it to create a launcher that opens the site without browser furniture. There is no package to approve, no publisher record, no version string a reader can quote, and no review queue between a change on the operator’s servers and the thing that opens when you tap. An operator can replace the lobby shell, the cashier layout, the login flow and the icon itself overnight, and nothing on the handset marks that it happened.

A third route gets advertised and is excluded from this page outright: an installer file offered for download from an operator’s own page or a link in an email, outside either store. That is not the same category of object. It is an unreviewed executable asking for install permission on the device that also holds a banking app, an authenticator and a mail client, and the convenience it offers is already available through the home-screen route without that grant. Where an operator’s mobile page leads with a download button rather than an add-to-home-screen instruction, treat the button as the finding.

Where the add-to-home-screen control sits depends on the browser rather than on the casino. On the iOS browsers it generally lives in the share sheet; on Android it generally lives in the browser’s overflow menu, and some sites additionally raise their own in-page prompt asking you to install. Those locations move between browser releases, so the reliable instruction is to look for the browser’s own wording — add to home screen, install app, or similar — inside the browser’s menus, and to distrust any in-page button that claims to install something without handing you back to the browser’s own control.

Neither route changes the thing underneath. The account is the same account, the terms are the same terms, the promotion conditions are the ones published on the operator’s live promotion page, and the operator is offshore in both cases. An icon is a shortcut, not a product, and nothing about the shortcut alters wagering conditions, payout conditions or who you are contracting with. Payment rails, withdrawal stages and identity checks behave as they do on a desktop and are covered on pokiescashout.com (payments, withdrawals, KYC, bonus-term arithmetic) rather than here.

The admission test a mobile build has to pass

The test used on this page has six conditions, all of which a reader can check in a single sitting, none of which requires a deposit. Condition one: the lobby can be added to the home screen through the browser’s own control, with no downloaded installer involved. Condition two: launching from that icon opens full screen, with no address bar, into a logged-in state rather than onto a sign-in page. Condition three: the cashier opens inside the same shell, on the same domain, and states the methods and per-transaction limits applying to an Australian account before anything is confirmed.

Condition four: the session survives an ordinary interruption — a phone call, a lock, a switch to another app and back — without silently discarding the login or the open game. Condition five: the account’s own controls, meaning deposit limits, session reminders, time-outs and self-exclusion, are reachable from the mobile build in the same number of taps as the deposit button, and not only from the desktop site. Condition six: the build works on mobile data at the quality you actually get, not only on home wi-fi.

Those six are chosen because each one is observable, each one fails in a way you can see, and none of them requires trusting a figure somebody else collected. A seventh condition that readers often expect — that the mobile lobby carries the same number of titles as the desktop lobby — is deliberately absent, because catalogue counts are a property of licensing deals between operators and studios and change weekly, and because a shorter list of titles with touch builds behind them is a better lobby than a longer list half of which will not load.

What the test excludes is as important as what it includes. It says nothing about how any individual game behaves, what its designed return is, or how volatility feels over a short session; that subject belongs to pokiesalmanac.com (game mechanics, RTP, volatility) and the authoritative figure for any particular title is the info panel inside the loaded game itself. It says nothing about deposit rails, withdrawal stages or verification queues, which live on pokiescashout.com. This site’s own subjects are operator shortlists, bonus and payout conditions, licensing claims and the Australian legal position, and the six conditions above are written to stay inside that boundary.

The test is also not a ranking instrument. Six conditions give a pass or a fail per condition on one handset at one moment, which is a snapshot and not a score. Anything presenting itself as a numbered league table of mobile casinos is either ranking something else — bonus headline, affiliate placement, review volume — or is ranking builds that have since changed. The pass or fail you produce on your own phone is narrower than a score and considerably more useful, because it describes the device you will actually be using.

What an app store reviews, and what it never sees

The phrase no official app gets read as an accusation, and it is mostly a description of store policy. Both mainstream stores publish their own rules for real-money gambling software, and those rules generally require the publisher to be an identified business entity and to demonstrate that it is authorised to offer the product in each country where the listing is available. Those policies are revised regularly and the current wording lives on each store’s own developer policy pages, which is where to read them rather than here. The consequence for Australia follows from the legal position rather than from the stores: online casino services cannot lawfully be provided to people in Australia, so there is no authorisation for an operator to demonstrate, and no listing appears.

It helps to be precise about what a store review would have given you, because the list is shorter than people assume. A review process nominally establishes who the publisher is as a legal entity, what device permissions the package declares, that the package does what the listing says, and that an age rating is attached. It also gives you a version history, an update channel, a user review thread the publisher does not control, and a removal mechanism that works across every installed copy at once. Those are real things to lose.

What a store review has never established is the part readers most want vetted. It does not check bonus terms, wagering multiples, maximum cashout clauses, payout timetables, the contribution rates that decide whether a requirement can be cleared, or whether an operator’s complaints process leads anywhere. It does not assess the designed return of any game. It does not confirm that an operator will pay. A store badge on a gambling app in some other country is evidence about packaging and about that country’s licensing position, and is not evidence about any of the clauses that decide what happens to a balance.

The absence of a listing therefore removes a specific and limited set of protections. There is no publisher name attached to the icon unless you go and find it in the site footer. There is no permissions screen, because a home-screen web app does not request native permissions at install time. There is no version number to quote when support tells you the problem does not reproduce. There is no store-side refund or dispute channel, which for a casino was never going to be the useful channel anyway. And there is no mechanism that removes the thing from every handset at once if it turns out to be a lookalike.

The flipside is genuine and worth stating in the same breath. Because the installed icon is a web app rather than a package, it does not receive the access a native install would. It cannot read a contact list, it cannot run in the background when it is not open, it holds no location grant it was not individually given, and deleting the icon and clearing the site data removes it completely. For a category of software nobody should be granting broad device access to, the route that grants none is the better route, and the missing store listing matters less than the phrase makes it sound.

Special offer

WinCrown

+500% bonus offer

Play with bonus at WinCrown

The install flow, step by step, and the one screen that decides everything

The sequence is short. Open the operator in the handset’s browser. Read the address bar and confirm the domain character by character. Open the browser’s own menu or share sheet. Choose the browser’s add-to-home-screen or install item. Accept or edit the name offered. The icon appears on the home screen. Close the browser entirely, then launch from the icon. Six taps and one piece of reading, and the piece of reading is the only step that cannot be undone later by changing a setting.

That one screen is the address bar at the moment of installation, because it is the only verification the whole process performs. Nothing in the flow checks who published the manifest. The icon artwork, the display name and the start address all come from the site itself, so an icon can carry an operator’s exact logo and brand name while pointing at a domain that is not the operator’s. Once it is pinned, the address bar is gone and the domain is no longer in front of you at any point, including the point where you enter a password or open the cashier.

The arrivals most likely to put the wrong domain in that bar are the ones people actually use: a shortened link from a message, a redirect from an advertisement, a link in a promotional email, a QR code on a printed ad, or a search result for the brand name sitting above or below the operator’s own entry. None of those is inherently malicious and all of them hide the final destination until the page has loaded. The habit that costs nothing is to type the operator’s domain directly, or to arrive by your own saved bookmark, specifically on the occasion when you intend to install.

Two checks survive the install and are worth running once. First, open the same operator in a normal browser tab and compare the domain in the bar against what you expected; if the icon and the tab disagree about where you are logged in, you have two different sites. Second, on Android long-press the icon and open its app or site settings, which name the origin the shortcut points at; on iOS the equivalent is to open the installed app and use the share or page-information control where the browser exposes the current address. If the origin cannot be surfaced at all, delete the icon and add it again from a tab you typed yourself.

Removal is the easy part and worth knowing before you start. Deleting the icon removes the launcher. It does not necessarily clear the site data the browser holds for that origin, which is a separate action in the browser’s site settings, and on a shared handset that distinction is the one that matters. Do both if the point of removing it was to put distance between yourself and a logged-in casino, and do them in that order, so that the icon disappears before the stored session does.

Session length, the lock screen and the logged-in state

A session on a phone is interrupted constantly, which is why condition four exists. The login that persists is a token the browser holds for the origin, and whether the installed icon and a normal browser tab share that storage varies by platform and by browser release — on some combinations the installed app has its own storage partition and therefore its own login, on others they share. The practical test is two minutes long: sign in through the icon, then open the same operator in a tab and see whether you are already signed in. Whichever answer you get is the one that applies to your handset, and it is not a property of the casino.

Session expiry is set by the operator and is not published as a number anywhere worth trusting, so measure it rather than look it up. Sign in through the icon, lock the handset, and come back after five minutes; if you are still signed in, repeat at fifteen, then at an hour, then after an overnight gap. Four observations bracket the real timeout closely enough to plan around, and the figure you want is not the exact value but which bracket it falls in: a build that holds a session overnight behaves very differently on a shared phone from one that drops it in ten minutes.

Both outcomes have a cost and the costs point in opposite directions. A long session makes the icon convenient and makes the handset a logged-in casino that anyone holding it can open; a short session is safer on that axis and is the single most common reason people abandon the home-screen route, because a password prompt on a phone keyboard every time defeats the purpose of the shortcut. Decide which cost you prefer before you install, rather than discovering it on the fourth attempt, and if the answer is that you would rather not hold a logged-in casino at all, the browser tab route exists for exactly that reason.

Interruptions mid-game are the other half of condition four. What happens to an unfinished round when a call arrives, the screen locks or the connection drops is decided by the game’s own round-handling rather than by the lobby shell, and that mechanism is pokiesalmanac.com’s subject rather than this site’s; the loaded game’s info panel is where its own behaviour is described. What belongs here is the lobby-level observation: after any interruption, check the displayed balance against what you expected before taking another action, and screenshot the game history entry if the two disagree, because that record is what a support conversation will be about.

One mobile-specific detail affects sign-in more than anything else on this list. Password managers and system autofill behave differently inside a standalone web app than inside a browser tab on some platforms, and an autofill that works in the tab may not appear through the icon. Check it before you rely on it, because the combination of a short session timeout and an unavailable password manager is the configuration in which people start choosing shorter passwords, which is a worse outcome than a visible address bar ever was.

What the build leaves on the handset

A mobile casino lobby, by either route, stores things locally, and the categories are the ordinary web ones rather than anything exotic. There is a session cookie or token that keeps you signed in. There is local storage holding interface preferences — sound on or off, the last lobby filter, a dismissed banner, sometimes the last game opened. There is a cache of static assets so the lobby loads faster the second time. Where a service worker is used, there is a separate cache it controls, which is also what allows an installed lobby to open its shell with no connection at all and then fail at the point where real data is needed.

Three consequences follow. The first is that a logged-in casino may open instantly from a cold tap, which is convenient and is also the behaviour that makes an impulse into a deposit in about four seconds. The second is that clearing the browser’s site data for that origin signs you out and resets the preferences, and is the correct action when handing the phone to somebody else. The third is that an installed lobby with a service worker can show a stale shell after the site has changed, which is worth knowing before you conclude that a cashier screen is broken; closing and reopening, or clearing the site data, is the first thing to try.

Where that data sits depends on the route, and on a shared or family handset the difference is the whole point. Site data for a browser tab lives in the browser profile, visible in the browser’s site settings and clearable there per origin. Site data for an installed web app may sit in the same place or in its own partition, which is the same uncertainty described above. The way to settle it is to clear the browser’s data for the origin and then launch the icon: if you are still signed in, the icon has its own store and needs clearing through its own settings entry or by deleting and reinstalling it.

Private or incognito browsing is a usable third position for anyone who wants no persistence at all. It leaves nothing behind when the window closes, which also means no saved session, no saved preferences and no cached assets, so every visit is a full sign-in on mobile data. It cannot be combined with the home-screen route, since the point of the icon is persistence. The trade is straightforward: convenience against leaving a logged-in gambling account on a device that other people pick up.

Two smaller handset behaviours are worth deciding about once. The app switcher keeps a preview image of the last screen of every open app, so a balance, a deposit confirmation or a game result may be visible to anyone who double-taps the switcher without unlocking anything further; both platforms offer ways to limit or clear those previews, and closing the lobby rather than backgrounding it is the simplest. And if you use deposit limits, session reminders or self-exclusion, condition five in the test above exists precisely because those controls are useless if they are three menus deeper on mobile than the deposit button is.

Exclusive

Safe Casino

+500% bonus offer

Play with bonus at Safe Casino

Mobile data, dropped connections and what a lobby costs to run

Condition six says to test on mobile data, and the reason is that a casino lobby is one of the heavier things a phone browser loads: a grid of title artwork, a live-updating jackpot or promotion strip, an analytics layer, and then a game client that streams its own assets. How many megabytes that adds up to varies enormously between operators, between lobby pages and games, and between one build and the next, so no figure is printed here. Your handset already measures it: both platforms report data use per app, which for the browser route means the browser’s figure and for the installed route may be reported separately.

Do the arithmetic with your own measurement rather than with somebody else’s. Reset the counter, play a deliberate thirty-minute session on mobile data, and read the figure. If it reports 40 MB for the half hour, that is 80 MB an hour; against a 10 GB monthly allowance that is roughly 125 hours before anything else on the phone is counted, and against a 2 GB allowance it is about 25 hours. If it reports 150 MB for the half hour, the same 2 GB allowance supports under seven hours. Both outcomes are plausible depending on the build, which is exactly why the figure has to come from your own session rather than from a page like this one.

Live dealer tables are the case where this stops being theoretical, because a video stream is a different order of consumption from a lobby grid, and a capped or throttled plan will show it first there. The behaviour of live tables generally, and the shortlist of operators that run them, sits at /best/live-dealer-casinos/ on this site. On a phone the additional considerations are plain: a video stream drains the battery faster, throttles on a shaped connection, and is the product most likely to be unwatchable on a train.

Connection loss needs a rehearsal rather than a theory. Open the lobby, turn on flight mode for ten seconds, turn it off, and watch what the build does. The outcomes worth distinguishing are a clean reconnection into the same state, a reconnection that drops you at the top of the lobby, a frozen screen that needs a restart, and a shell that renders from cache while showing no live balance. The last of those is the one to recognise, because a cached shell showing a stale number looks exactly like a working lobby showing a current one.

Keep one habit for the case where money and a dropped connection coincide. Before reacting to an unexpected balance, screenshot the screen you are on, then screenshot the account’s own transaction or game history once it reloads. The history held by the operator is the record any support conversation will work from, and a screenshot with a timestamp is the only thing you will have that it did not generate. What happens next — the stages a disputed or pending amount passes through, and what verification can hold up — is pokiescashout.com’s territory, not this page’s.

The notification prompt and what a lock-screen promotion does

An installed web app can ask for permission to send notifications, and a casino lobby that holds that permission can put a message on a locked screen. This is the one permission the home-screen route does grant, it is requested after installation rather than during it, and it is the only item in this whole process where a single tap meaningfully changes what the operator can do to you afterwards. Declining it costs nothing: the account still works, the promotions still exist in the account’s own inbox, and nothing in the lobby stops functioning.

What a granted permission buys the operator is a direct line to a moment you did not choose. Gambling promotions are built around timing, and a notification arriving in the evening, on a weekend, or shortly after a session ended is the strongest tool in that kit. For anyone using deposit limits, time-outs, session reminders or self-exclusion, the prompt is working directly against the thing those tools exist to protect, and the right answer to it is no, without deliberation.

If it has already been granted, it is revocable in two places and either works. On Android, the installed web app appears in the system notification settings and can be switched off there; on both platforms the browser’s site settings list notification permissions per origin and allow a blanket block for the site. Revoking the permission does not sign you out and does not affect the account. It is one of the few items on this page that can be fixed after the fact in under a minute.

Push notifications are a separate channel from the operator’s marketing email and SMS, and switching one off does not switch off the others. Those live in the account’s own communication preferences on the operator’s site, and the specific clauses that govern what an operator may send you after sign-up are part of the terms you accepted, which is this site’s subject rather than a mobile question. The point for a phone is simply that three channels exist and that turning off the loudest one leaves the other two running.

One further note on prompts, because they cluster at the same moment. A lobby may also ask for location, for camera access when a verification step is involved, or to keep the screen awake. Each should be decided on its own and none should be granted because it appeared in the same sequence as the install. A camera request in particular belongs to an identity-verification step rather than to the shortcut, and verification is handled on pokiescashout.com.

Browser tab against home-screen icon, field by field

Nine fields separate the two routes, and listing them is more useful than a verdict. Address bar: visible in the tab, absent from the icon. Origin verification: available at any moment in the tab, available only at install time and then through settings for the icon. Screen area: the icon wins, by the height of the browser’s own controls, which on a phone is the difference between seeing one row of lobby tiles and two. Launch speed: the icon wins. Session persistence: platform-dependent for the icon and ordinarily shared with the browser profile for the tab.

Storage location: browser profile for the tab, possibly a separate partition for the icon, which is the uncertainty to resolve by testing. Updates: both load whatever the server is serving, except that an icon with a service worker may serve a cached shell first. Permissions: identical, except that the icon can ask for notifications and a tab in practice rarely does. Removal: closing a tab leaves the site data in the browser profile, deleting an icon leaves the site data wherever that icon kept it, and in both cases clearing the data is a separate action.

The ninth field is the failure mode when a domain stops resolving on Australian connections. A tab returns an error page you can read, in a browser where you can immediately try something else. An icon opens a blank or failing shell with nothing explaining why, and it stays on the home screen looking functional, next to a saved session and whatever balance sits behind it. That asymmetry is the strongest practical argument for the tab, and what actually causes it is covered at /legal/acma-blocked-casinos/.

A decision rule follows from the fields rather than from a preference. Choose the icon if you play often enough that launch friction matters, the handset is yours alone and locked, you have declined notifications, and you installed from a domain you typed yourself. Choose the tab if the handset is shared or occasionally handed around, if you want the address bar in view every session, if you are trying to reduce how easily a session starts, or if you are using any limit or exclusion tool and would rather the casino were two deliberate steps away rather than one tap.

Neither route is more authorised than the other and neither is endorsed here. Both reach the same offshore operator under the same terms, and the choice is about handset behaviour and friction rather than about safety in any regulatory sense. Anyone presenting the installed version as the safer or more official one has the relationship backwards: the icon is the version with no address bar, and the address bar was the only verification either route offered.

Why this page publishes no ranked list of mobile casinos

Pages answering this query usually open with a numbered list of operators and a score beside each for mobile experience. This one does not, for a reason that is specific rather than coy. A mobile web build carries no version number, passes no review, and can be replaced between one session and the next without any marker that it changed. A published score for a named operator’s mobile build is therefore a claim about a build that may no longer exist by the time it is read, and the more precise the score sounds, the shorter its useful life.

What a ranked mobile list is usually ranking is worth naming, because it is rarely the mobile build. It is ranking bonus headline size, commercial placement, partner-reported review volume, or the order the author’s affiliate feed happened to return — all of which are real quantities and none of which measures whether a session survives a lock screen or whether a cashier opens inside the same shell. A list that scores nine operators out of ten for mobile without describing the handset, the connection or the date has not measured anything repeatable.

This site does hold dated operator data, and it is published where the criterion matches it: the shortlists under /best/ each state their own filter, their own sorting rule and the date each row was confirmed, and the two sponsored partners configured here appear on them with whatever figures were supplied and dated. Nothing about a bonus headline or a review count belongs on a page about session behaviour, so none of it is repeated here. If the mobile question you actually have is about install flow and home-screen behaviour for the configured brands, /best/casino-apps/ is the page that holds it.

For readers who arrived wanting to know where this subject turns up in practice, both Safe Casino and WinCrown operate browser-based lobbies that an Australian visitor would reach the same way as any other offshore site, and that is a navigational note about how the routes on this page apply rather than any claim about either lobby’s contents, quality or catalogue. Everything in the six-condition test still has to be run on your own handset, against the live build, on the day you intend to use it.

The honest short answer to which mobile casino is best in Australia is that no store-listed app exists, the home-screen shortcut is the product, the operators are offshore in every case, and the condition-by-condition result differs between handsets, browsers and weeks. Half an hour on your own phone produces a better answer than any league table, and the next section is that half hour written down.

The half-hour check on your own handset, in order

Run it in sequence, because each step depends on the one before it, and run it on mobile data rather than wi-fi so that what you measure is the worse of your two ordinary conditions. Step one: type the operator’s domain into the browser yourself and read it back character by character before doing anything else. Step two: use the browser’s own add-to-home-screen or install item; if the page instead offers a file to download, stop and record that, because the thing offered is not the thing this test covers.

Step three: close the browser completely, then launch from the new icon. Pass requires a full-screen lobby, no address bar, and a logged-in state. An address bar still present means you have a bookmark rather than an installed app, and nothing the operator does will change that. Full screen but logged out means an icon that asks for a password on a phone keyboard every time, which is the configuration most people abandon. Step four: decline the notification prompt when it appears, which it usually does shortly after the first launch.

Step five: open the cashier without depositing. It should render inside the same shell, on the same domain, list the methods available to an Australian account, and show the minimum and maximum per transaction. If it bounces you into the browser or onto a different domain, write that down: it is the single most important observation in the whole sequence, because it is the step at which money moves. Step six: find the account’s limit and time-out controls and count the taps from the lobby; compare that against the taps to the deposit button. Step seven: open a game in demo where the operator offers it, rotate the handset, and open the game’s own info panel.

Step eight is the interruption test: with a game open, enable flight mode for ten seconds, disable it, and record which of the four reconnection outcomes you get. Step nine is the session test: lock the phone and return at five minutes, fifteen minutes, an hour, and the next morning, noting at which bracket the login disappears. Step ten is the data reading: reset the per-app data counter before the session and read it after, then run the arithmetic against your own monthly allowance as set out above.

The time budget is the reason this is a half-hour check rather than a ten-minute one. Steps one to seven take about fifteen minutes of attention. Step eight takes two. Steps nine and ten run in the background and cost only the discipline of looking at the phone four times. Write the results as ten lines in a note, with the date, the handset and the browser at the top, because the one thing a published table can never give you is a result for your own device — and because the next time the lobby behaves oddly, a dated set of ten lines tells you whether it changed or you did.

The offshore position, a blocked domain, and the check date

Every operator reachable from Australia through either route on this page is offshore. The position taken by the Australian Communications and Media Authority is that online casino services cannot lawfully be provided to people in Australia, so no operator discussed here holds or could hold Australian authorisation, and none is described on this site as licensed in Australia. No licensing authority or licence number is printed for any brand here, because none is held on file, and a regulator’s logo in a website footer is artwork published by the operator rather than a record published by the regulator.

The check a reader can actually run takes one search and belongs to the company rather than to the app. Find the operating company name — footer, account terms, or the payments section of the terms, where it has to appear — then open the named regulator’s own public register and search it for that exact company and for the exact domain the icon points at. An entry naming a different entity or a different domain is not a match. What the various licence types mean once a genuine entry is found is set out at /legal/licences-explained/, and what an offshore licence does and does not give an Australian player is at /legal/offshore-vs-licensed/.

A phone adds one failure mode the desktop does not have, and it is the strongest argument in this whole page for keeping an eye on the browser route. If a domain stops resolving on Australian connections, an installed icon does not announce it. It sits on the home screen looking exactly as it did, opens a blank or stalled shell, offers no error you can act on, and does so with a saved session and whatever balance is behind it on the other side. Where the blocking list lives and what a block means for money already deposited is covered at /legal/acma-blocked-casinos/.

What to do before that happens is short and cheap. Know the operating company name and the support address independently of the lobby, so that a non-loading icon is not also the end of your ability to contact anyone. Keep withdrawals from accumulating in an account you reach through one shortcut. Note the escalation path beyond the operator’s own support queue, and whether whichever body it names publishes its decisions, because that road is short and is worth knowing the length of before you need it.

This page was last checked on 6 October 2026. Three things would change it: a change to how home-screen installation works in either mobile browser, which has happened more than once and affects every operator simultaneously rather than one at a time; a change to either store’s published gambling policy, which would alter the first half of this page without altering the Australian outcome; and a change in the Australian legal position, which would change considerably more than this page. A larger bonus headline would not change it, because the six conditions ask nothing about promotions, and a higher partner-reported review count would not, because a count supplied by the party selling the offer measures none of them.

What is deliberately not asserted here, so that nobody has to guess: no figure for session timeout, lobby data use, catalogue size, loading time or install success rate, because every one of those varies by operator, by build, by handset and by week, and the authoritative reading is the one your own handset produces. No designed-return figure for any game, which is read in the loaded game’s own info panel. No ranking of named operators’ mobile builds, and no licensing claim of any kind. And nothing anywhere on this page suggesting that a route, a setting or a sequence changes what a game is designed to return, because none does.

Read next