A player who opens an operator's app for the first time is not really asking whether it will run. They are asking whether the thing they installed is what it claims to be, whether it can do anything the website cannot, and whether installing it has changed what they owe or what they can withdraw. Those three questions decide whether the app is worth the space on the phone, and none of them is answered by the download button.
The three things an operator can put behind the same icon
When a reader sees the MGM app in a store listing, the word "app" is doing a lot of work. It can mean three different pieces of software, and the difference between them changes what the reader should check before and after installing.
A native app is a program written for the phone's own operating system. It is installed, it has its own icon, and it can ask the phone for permissions that a website cannot: camera access, location, device storage, notifications, biometric login. A native app can also keep a player logged in between sessions and can store some data on the device itself rather than in the browser. None of that changes the rules of any game, but it does change what the operator can see and what the player has agreed to let it see.
A wrapped web view looks like an app and is distributed like an app, but the screen the player sees is the operator's website rendered inside a thin native shell. The shell may ask for the same permissions as a native app, but the actual play, the cashier, the promotions page and the account settings are the same web pages the player would reach in a browser. The shell adds convenience; it does not add a second set of rules.
A mobile site is not an app at all. It is the operator's website laid out for a small screen, reached through a browser, with no installation and no store listing. It asks for no permissions beyond what the browser itself allows. A player who wants the least possible software on their phone uses the mobile site; a player who wants push notifications or biometric login uses one of the other two.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Whether the app is native or a wrapped web view | The operator can repackage the mobile site as an app at any time, and the store listing may not say which one it is | The app's own settings or "About" screen, and the permissions it asks for at first launch |
| Which permissions the app requests | An update can add camera, location, storage or notification access that the first version did not ask for | The store listing's permission section, and the phone's own app settings after installation |
| Which version is current | Operators release updates to fix faults, change payment screens or add features, and an old version may stop working | The store listing's version history, and the app's own update prompt |
| Whether the app is the official one | Copies and lookalikes appear in third-party stores and on download sites, and the operator cannot control what those copies do | The operator's own website, which should link to the official store listing rather than to a direct download |
| What the app changes about bonuses or withdrawals | An operator may run app-only promotions, or may require the app for certain login or verification steps, and those conditions can change | The promotions page and the withdrawal policy, read inside the app or on the mobile site |
What installing an app can and cannot change about play
The most common misreading is that an app gives better odds, faster payouts or different rules. It does not. The games run on the operator's servers, and the outcome of a spin or a hand is decided there, not on the phone. The app is a window onto the same account, the same wallet and the same game engine as every other channel. A player who deposits through the app and a player who deposits through the browser are playing the same games with the same house edge, whatever that edge is for the game they choose.
What the app can change is the surface around the play. It can remember the login, so the player does not re-enter a password every session. It can send a notification when a new promotion is published or when a withdrawal moves to a new state. It can use the phone's camera to scan an identity document for verification, where the mobile site would ask for a photo upload instead. It can offer a smoother table view or a faster way to switch between games. Those are conveniences, and they are real, but they are conveniences of access, not of odds.
The reader should also understand what the app cannot fix. It cannot make a slow withdrawal faster, because the withdrawal is processed by the operator's payments team and the payment method, not by the phone. It cannot remove a wagering requirement, because that requirement is written in the promotion terms and applies to the account, not to the device. It cannot bypass verification, because the operator must identify the account holder no matter which screen they use. When a player reads a promise that the app does any of those things, they are reading a promise that is not the operator's.
The permissions an app can ask for, and which ones a player should question
Every permission an app requests is a door the player opens. Some doors are necessary for the app to do its job; some are conveniences the operator wants; some are things no casino app needs and a careful player should refuse or delete.
The permissions that make sense for an operator app are the ones tied to a specific feature the player can see. Camera access makes sense if the app offers document scanning for verification. Notifications make sense if the player wants to hear about a withdrawal or a promotion. Storage access can make sense if the app lets the player download game files to play offline, though most casino games are streamed and need no offline storage. Location access is the one to question hardest: an operator may use it to confirm the player is in a place where play is permitted, but a player who is asked for location before any game has loaded should ask why.
The permissions that should stop a player are the ones with no visible feature attached. An app that asks for contacts, call logs, SMS access or microphone access is asking for data that no casino game needs to run. The answer to that request is to deny it, and if the app refuses to work without it, to delete the app and use the mobile site instead. The mobile site asks for none of those things, and it reaches the same account.
Where the real risk sits: anything installed from outside an official store
The single most important check a reader can make is where the app came from. An app installed from the phone's official store has passed that store's review process, whatever its limits, and the reader can see the developer name, the permission list and the version history before installing. An app downloaded from a website, a forum link, a QR code or a third-party store has none of those protections. It may be the operator's app; it may be a copy with the operator's name on it; it may be something else entirely that only looks like the operator's app until the player types a password into it.
The reader's rule is simple and does not depend on any fact about this operator: the only download that should be trusted is the one reached from the operator's own website, and even then only when it leads to the official store listing, not to a direct file. A direct file can be changed after it is posted, and no one can verify what it contains after the fact. If the operator's website does not link to a store listing, the reader should treat that absence as the answer: there is no official app to install, and anything else with the name on it is not the operator's.
What to read before and after installing
Before installing, the reader reads the store listing. The developer name should match the operator's name exactly, not a close variant. The permission list should contain only the permissions tied to visible features. The version history should show recent updates; an app that has not been updated in years is an app the operator has stopped maintaining, and it may stop working or stop receiving security fixes.
After installing, the reader reads two more things. The first is the phone's own app settings, which show the permissions the app has, which can be more than the store listing showed. The second is the operator's promotions page and withdrawal policy, read inside the app, to see whether the app carries any conditions the mobile site does not. If the app shows a bonus the mobile site does not, the terms of that bonus are the only thing that matters, and they are read on the operator's page, not in the app's marketing screen.
When the page does not state something, the reader should treat that silence as information. If the store listing does not show a permission list, the reader cannot know what the app will ask for, and the safe choice is not to install. If the operator's website does not link to the app, the reader cannot know that any store listing is official, and the safe choice is the mobile site. If the app does not show its own version number or its own terms, the reader cannot know which rules apply, and the safe choice is to close it and open the browser.
FAQ
Does the MGM app give better odds than the website?
No. The app, the wrapped web view and the mobile site all reach the same account and the same game servers. The odds are set by the game, not by the device, and a player who reads a claim that the app pays more is reading a claim the operator's own game rules do not make.
How do I know the app I installed is the official one?
Check the developer name in the store listing against the operator's name, and check that the operator's own website links to that same store listing. If the website does not link to it, or if the app came from a direct download or a third-party store, there is nothing to verify and the reader should treat it as unofficial.
What permissions should a casino app have?
Only the permissions tied to visible features: camera for document scanning, notifications for alerts, storage for offline files if the app offers them. Contacts, call logs, SMS and microphone access have no role in running a casino game, and a request for any of them is a reason to deny or delete.
Can I just use the mobile site instead?
Yes. The mobile site reaches the same account, the same games and the same cashier, and it asks for no permissions beyond what the browser allows. A player who does not want an app on their phone loses nothing except push notifications and biometric login.
This page is an independent summary of what an operator app is and is not; it is not published by MGM, and it states no figure or status for them, so the operator's own app listing and terms pages are the only binding source for anything about their app.
Play responsibly
Gambling should be treated as paid entertainment, never as a way to earn income or recover losses. 1-800-MY-RESET (1-800-697-3738)
18+ or 21+ depending on where you are; follow the minimum age that applies to you.
This article is general information about how these mechanics work. It is not legal advice and not a recommendation to gamble or to use any particular operator. Availability and legality differ by jurisdiction — check the rules that apply where you are.
