The decision is made before the download begins
A reader looking at the 987ng app page is usually deciding between three different things without always knowing they are three different things: a native app installed on the device, a wrapped web view that behaves like an app but is really the mobile site in a shell, and the mobile site itself opened in a browser. The choice matters because each one asks for different permissions, stores different data on the device, and updates in a different way. The 987ng app page is where a reader should be able to tell which of the three they are being offered, and where the download comes from.
An operator app is not a better version of the casino. It is the same account, the same balance, the same game results and the same terms, reached through a different piece of software. Nothing about the house edge, the payout behaviour or the bonus conditions changes because the reader is holding a phone instead of sitting at a desktop. What changes is what the software can see on the device, and how much the reader trusts the source of the installation file.
Native app, web view, or mobile site: the difference is the permissions
A native app is written for the device's operating system and installed through an official store or a file the reader downloads and approves manually. It can ask for access to storage, contacts, location, camera, microphone, device identifiers and notifications. Each of those permissions is a separate decision, and the operating system shows them one by one at install time or on first use. A wrapped web view is a native shell that loads the operator's mobile site inside it. It asks for fewer permissions, but it can still ask for some, and the reader may not be able to tell from the outside whether they are installing a real app or a browser window with an icon. The mobile site asks for almost nothing, because the browser already isolates it from the rest of the device.
For the 987ng app, the page should state plainly which of these it is. If it does not, the reader can still tell: a native app has a version number that changes with updates, a file size, and a list of required permissions visible in the store or in the device settings. A web view has almost none of that. A mobile site has none at all.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Whether the app is native or a web view | Operators sometimes repackage the mobile site as an app without changing its behaviour | The app's store listing or the operator's own app page, under technical details or version history |
| Which permissions the app requests | Updates can add or remove permissions, and the list differs between operating systems | The store listing's permission section, or the device's app settings after installation |
| Which operating system versions are supported | Older devices fall out of support as the app is updated | The store listing's compatibility section or the operator's app page |
| Whether the app can be updated automatically | Apps installed outside an official store often cannot update themselves | The download source and the device's update settings |
| What the app stores on the device | Cache size, saved login tokens and offline data all grow with use | The app's settings, or the device's storage breakdown for the app |
| Whether the app logs the reader out automatically | Session timeouts are a security setting the operator can change remotely | The app's security or account settings, if stated at all |
What an app can and cannot change about play
An app changes the delivery of the games, not the games themselves. The same random number generator, the same return-to-player design, the same table rules and the same bonus terms apply whether the reader plays through the 987ng app, the mobile site or a desktop browser. The app can change how quickly pages load, how smoothly a game runs on the device, whether notifications appear, and whether the reader can use biometric login. It cannot change the mathematics of a bet, and it cannot make a withdrawal arrive faster than the operator's own processing pipeline allows.
One thing an app can change is the reader's exposure to the operator's promotional timing. Push notifications are a permission the app requests, and once granted they give the operator a direct line to the device. A reader who installs the 987ng app and accepts notifications has chosen to receive messages at the operator's discretion. The bonus terms themselves do not change, but the reader's awareness of them does, and that is a real difference in behaviour.
Installation from outside an official store is a different security decision
When an operator distributes an app through an official store, the store has already applied its own review process, and the app is signed by a developer certificate that the operating system checks. When the same app is distributed as a direct download from the operator's site, the reader is being asked to bypass that review and trust the operator's own file. On most devices this requires changing a security setting to allow installation from unknown sources, and that setting then applies to every other file the reader installs afterwards, not just the 987ng app.
The questions to ask before installing from outside a store are the same for any operator: does the download page use an encrypted connection, does the file name match the app being described, does the device warn that the file is unsigned or from an unknown developer, and does the operator explain why the app is not in the store. An absence of any of those answers is itself an answer. A page that offers a direct download without explaining the security trade-off is asking for trust it has not earned.
Login rewards and the app: the claim is on the promotions page, not the app page
A reader who installs the 987ng app because they have seen a login reward advertised should understand that the reward is a promotional term, not a property of the app. The app is the delivery channel. The reward is defined by the operator's promotions page: its amount, its wagering requirement, its eligible games, its expiry, and the steps needed to claim it. None of those figures can be read off the app page, and none of them should be assumed from the fact that an app exists.
If the app page mentions a login reward, the reader's next step is to open the promotions page and read the terms that govern it. If the app page does not mention a reward, the reader has no basis for expecting one. In either case, the app itself is not the source of the obligation. The operator's published terms are.
What the app page should tell the reader, and what it cannot
The 987ng app page can tell the reader what kind of software is being offered, where it can be downloaded, which devices it supports, and what permissions it will request. It cannot tell the reader whether the app is safe, whether the operator is licensed, or whether the games are fair. Those are separate questions answered by separate pages: the licensing page, the fairness or RNG certificate page, and the terms and conditions. A reader who treats the app page as evidence of any of those things is reading the wrong document.
The same applies to account security. An app can offer biometric login, two-factor authentication prompts, and automatic logout. Whether those features exist is stated on the app page or in the app's settings. Whether they are sufficient is a judgement the reader makes, not a fact the app page can supply. The 987ng app page is a description of software, not a guarantee about the operator.
FAQ
Is the 987ng app the same as the mobile site?
It is the same account and the same games, reached through different software. The mobile site runs in a browser and asks for almost no device permissions. An app, whether native or a wrapped web view, is installed on the device and can ask for more. The difference is in the permissions and the update path, not in the game results.
Does installing the app change the bonus terms?
No. Bonus terms are set on the promotions page and apply to the account regardless of how the reader logs in. An app can make the reader more aware of promotions through notifications, but it cannot change the wagering requirement, the eligible games or the expiry date of a bonus.
What should I check before downloading the app from the operator's site?
Check that the download page uses an encrypted connection, that the file name matches the app being described, and that the device does not warn of an unsigned or unknown developer. Also check whether the operator explains why the app is not in an official store. If any of those checks fails, the reader is taking on more risk than a store download would involve.
Where do I find the login reward terms?
On the operator's promotions page, not on the app page. The app page may mention that a reward exists, but the amount, the wagering multiple, the eligible games and the expiry are all stated in the promotions terms. The app is only the channel through which the reader logs in to claim it.
This page is an independent summary of what an operator app page covers. It is not published by 987ng, and it states no figure or status for them. The operator's own app page and promotions page are the only binding sources for what the app is and what it offers.
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.
