Download, install on a current Android or iOS device
The download route explains how to install the platform's app on a current device, what the install screen asks for and how to verify the install is genuine.
Install on Android
On Android, the platform's app is published on Google Play under the platform's verified publisher name. Open Google Play, search for the platform's name, and check the publisher name, the install count and the review history before tapping Install.
A genuine app on Google Play has been reviewed by Google; a side-loaded APK from a third-party site has not. If the platform offers an APK download outside Google Play, the APK context page explains what to verify before installing.
Install on iOS
On iOS, the platform's app is published on the App Store under the platform's verified publisher name. Open the App Store, search for the platform's name and check the publisher name, the version number and the review history before tapping Get.
An iOS device will not install an unsigned app; the App Store is the only install channel for iOS. A reader who is offered a "direct download" for iOS is being offered something that is not how iOS works.
Verifying the install
Three signals help verify an install is genuine. (1) The publisher name matches the platform's own website. (2) The install count is consistent with a published platform, usually hundreds of thousands or more. (3) The review history is real: reviews are written by identifiable users and reference specific features.
After the install
Once the install is complete, the next step is the same as the web route: open the account menu, set the deposit cap, set the session-time cap and confirm that the pause action is one tap.
Set your limits
The safety and responsible-play guides explain what to check before depositing and what to set once the deposit has been made.
Install verification
Reading the install screens, line by line
The install screens for a real-money skill-game app are short but every line matters. Most readers skim past the permission list and end up surprised later by what the app can reach in the background. The notes below map each line of the install flow to the question a careful reader is actually asking, in the order those questions tend to surface.
Where the file came from
The first thing to confirm is that the file you are about to open came from the platform's official channel. On Android, that is either the Google Play listing or the platform's own APK repository; on iOS, the App Store entry. Anything forwarded in a chat, posted in a Telegram group, or hosted on a generic file share is, by definition, not a verified source, even if the filename looks identical. The source screen is the simplest one to read: filename, version, file size, last build date. If any of those four values do not match what the platform lists on its download help page, do not open the file.
What the install is asking for
The second install screen is the Android permission list. A skill-game app has a defensible reason to ask for storage, network, and (on older Android versions) read-phone-state. It does not have a defensible reason to ask for contacts, microphone, camera, location, or accessibility services. If any of those appear in the list, that is a separate signal from the file-source signal, and the right response is to cancel the install rather than toggle the permission off and proceed. iOS surfaces these in a separate per-feature prompt after install and the same reasoning applies: deny anything the genre does not need.
What the home screen confirms
Once the app is open, the home screen is the third verification surface. A genuine install usually shows the brand name in the title bar, the operator's licence reference (often at the bottom of the sign-up screen), and a version number in the settings menu that matches the one the platform's help page lists. If the title bar shows a different brand from the platform you intended, or if the version number reads something like "v.2.0.1-mod" or carries an extra suffix, close the app and clear its data before any further interaction. A mismatch at this layer is harder to walk back than a mismatch at the source.
A reader's three-pass checklist
Pass one, before the tap: confirm the file source against the platform's published help page on a separate browser tab. Pass two, at the permission screen: refuse every permission outside the genre-typical list and re-check the file size in case the install script has rewritten itself mid-flow. Pass three, on first launch: confirm brand title, operator licence reference, and version string in the same session, in that order. If any of the three passes fail, do not proceed to sign-up, and do not save the file as a "fallback" install. That is how a second-rate copy ends up installed alongside the real app and re-opening itself on every reboot.
Day-one setup
First-launch settings that shape the rest of the relationship
Most readers open the app, sign up, and discover weeks later that they never set the controls the app quietly placed inside the settings menu. The four settings below are the ones worth finding on day one, in the order they are best found.
Deposit cap
The deposit cap is the single most useful control on day one and the one readers most often postpone. The platform typically lets you set a weekly ceiling that the cashier screen will refuse to exceed regardless of how many deposits you queue. The cap is not a budget; it is an upper bound, and it is the bound a reader sets when they are least likely to be carried away by the moment. Most readers set this higher than they need; lowering it later is possible in most apps, raising it usually involves a short delay.
Session reminder
The session reminder is the second control worth turning on, and it is a counter, not a clock. Most platforms let you pick an interval (commonly 30, 60, or 120 minutes) at which a soft overlay appears showing how long the current session has been open. The overlay does not log you out, it does not pause play, and it does not block deposits. What it does is break the immersion at a predictable interval, which is the single most effective single thing a reader can do to keep a skill-game habit from sliding into a continuous one.
Reality-check alert
The reality-check alert is closely related to the session reminder but runs on a different signal. Most platforms let you set it to fire after a specified total session length across a calendar week, not per-session. The alert then shows play time and net position relative to deposit, which is the most useful number a casual reader never sees in the normal play interface. Reading that number at the moment the alert fires is genuinely clarifying even for readers who feel they already know their own play pattern.
Cool-off toggle
The cool-off is the last of the four day-one settings and the one a reader sets without expecting to use it. Most platforms let you lock yourself out of play for 24 hours, 7 days, or 30 days at a single tap; the lock cannot be shortened by the reader during the cool-off window, only extended. Setting it on day one removes the option of "I'll cool off tomorrow if I need to" from the reader's decision tree, which is the way decision trees actually work under stress.
Notification surface
The notification surface is often set by the app's first-launch flow but is worth revisiting in the system settings menu afterwards. A skill-game app that earns its notifications tends to send between zero and three push messages per week: a deposit confirmation, a withdrawal status update, and an occasional responsible-play nudge. If the volume is higher than that, the reader is being trained to check the app more often than the genre warrants, and silencing the notification category by category is faster than muting the app as a whole.
Two-factor on the cashier
Two-factor on the cashier is the last setting worth confirming on day one, and most platforms now require it by default. The reader's job is to make sure the second factor is tied to a device they will still have in twelve months, not the cheapest second SIM card available. A second-factor phone that gets rotated out at the end of a contract is the most common cause of a reader being locked out of their own withdrawal flow years later.
Frequently asked questions
Common install-flow questions, answered in short
These are the questions readers actually send to the customer-care address during the install window. The phrasing below is paraphrased; the underlying answers are the same ones the editorial review has heard back from the platforms themselves.
The install asks for accessibility access. Is that normal?
For a real-money skill-game app, no. A genre-typical install asks for storage, network, and possibly the phone-state identifier on older Android versions. If accessibility access is on the list, the legitimate answer from the platform is almost always "we do not need that permission to run the core game." Cancel the install and contact customer care through the official site, not through the in-app chat surface of the install you have just opened.
The file is 9 MB but the page lists 84 MB. Did I copy it wrong?
Most likely, yes. Very small copies of skill-game installs are almost always the wrapper installer that downloads the rest on first launch, or a partial copy that did not finish transferring. The publisher's site usually lists both the "full" and "lite" installer sizes; cross-check against that list before opening. If only the lite size is published and your copy is smaller than the lite size, it is corrupted and worth deleting rather than opening.
I see two apps with the same name in my launcher. Is one a fake?
Possibly. Skill-game brands sometimes have a "lite" demo build that sits alongside the real-money build for the same operator; if both are legitimately yours, the demo usually shows a coloured "demo" tag on its launcher icon and never asks for a deposit. If only one icon shows a demo tag and the other one asks for a deposit, the second icon is the real build. If neither carries a tag and you did not knowingly install two copies, uninstall both and start from the platform's published install link.
The home screen shows a brand name I do not recognise. What now?
The right move is to close the app without signing in, clear its storage from the system settings, and reopen the install flow against the platform's published help page on a separate browser tab. If the home screen brand does not match the brand on the help page you navigated from, the file you installed was sourced from somewhere other than the platform's official channel. Do not sign up from that install, even if the sign-up screen looks normal.