1win Android App / APK — Install Guide for NZ Players

Why You’re Sideloading and Not Going to Google Play

Google’s Play Store policy bans real-money gambling apps in most jurisdictions including New Zealand, which means 1win and every comparable offshore casino operator distributes its Android app via direct APK download rather than through the Play Store. This is normal for the category. It is also a setup that requires you to override Android’s default “only install apps from Play” security setting for the install to complete, which is the source of most confusion in the install process.

This page is the practical install guide. We assume you’re a New Zealand player downloading on a Samsung, Pixel, OnePlus, Xiaomi, or other Android phone running Android 9 or later (most current models). The instructions below are tested across the major manufacturers and Android versions; the specific menu paths vary by manufacturer but the underlying steps are the same.

Before You Start: Three Things to Verify

Your Android version. 1win’s APK supports Android 5.0 and later, but in practice we’d recommend Android 9+ for performance and security reasons. Settings → About Phone → Software Information → Android Version. If you’re on an older Android, the app will install but may run sluggishly.

Storage space. The APK file is around 80MB; the installed app footprint after first launch is around 250MB once cache and game assets are downloaded. Plan for ~400MB of free storage if you want headroom.

Network connection. The APK download itself is a one-time ~80MB transfer. Use WiFi or 4G+ for the download. After install, ongoing usage runs at typical mobile-app data rates (around 30–80MB/hour for slot play, higher for live dealer streams).

If any of these are constrained, address them before starting. The install steps below assume you’re not running into version, storage, or connection issues mid-flow.

Step 1: Download the APK From the Operator Site

Open Chrome (or your default browser) on your Android device. Navigate to 1win’s official site. The mobile lobby will show an Android download prompt; the desktop lobby has the same download via a footer or app-page link.

Critical: download the APK only from 1win’s official domain. Third-party APK aggregators (“APK download sites” not affiliated with 1win) sometimes serve modified versions of operator apps with embedded tracking, malware, or stale versions that no longer work with the operator’s authentication. The download path: official operator site only.

The browser will warn that you’re downloading an APK file. Tap “Download anyway” or “OK” depending on the manufacturer. The download takes 30–60 seconds on a reasonable connection.

Step 2: Allow Install From Unknown Sources (Permission)

When you tap the downloaded APK to install, Android will block the install with a message about “unknown sources” or “untrusted sources.” This is the security setting we’re overriding for this app specifically.

The permission flow varies slightly by Android version:

Android 8 and later (most current devices): the dialog will offer a button to “Settings” — tap it. You’ll land on a screen showing your browser (or file manager) with a toggle for “Allow from this source.” Enable the toggle. Back out, and the install resumes.

Android 7 and earlier (rare on current devices): Settings → Security → Unknown Sources, enable globally. Less granular than Android 8+. Disable again after install if you’d prefer to keep the global setting off.

This permission is granted per-app in modern Android, not globally, which is meaningful from a security perspective: enabling install permission for Chrome doesn’t open the door to all sideloads forever. The permission applies to the specific browser or file manager from which you ran the install.

Step 3: Install

With permission granted, Android proceeds with the install. The dialog shows the permissions the app is requesting:

Network access (required). The app communicates with the operator’s servers for account, deposit, withdrawal, and game functions.

Storage (required). Game assets are cached locally rather than re-downloaded each session.

Notifications (optional). Push notifications for account events, promotions, and customer support replies. Optional — you can decline this without affecting core functionality.

Camera (optional, for KYC). The KYC document upload uses the camera. You can also upload existing photos from gallery. Optional permission.

Location (optional and worth considering). Some app builds request approximate location for region-specific compliance. NZ players don’t need to grant location for core functionality; if the app prompts, decline unless you’re comfortable with location-based features.

Review each permission, accept the required ones, and decline whichever optional permissions you’d rather not grant. Install completes in 5–10 seconds.

Step 4: First Launch and Account Login

The app’s first launch downloads game asset packs (~150MB on top of the install footprint). Wait for the asset download to complete — in our testing this took 30–90 seconds on a 4G+ connection.

Log in with your existing 1win credentials, or register through the app if you don’t yet have an account. Registration in-app is functionally identical to web registration; the same KYC and verification rules apply.

Step 5: Verify the Build

A quick sanity check: open the app’s settings (typically the gear icon or three-line menu) and look for a “Version” or “About” entry. The version number should match the operator’s currently-published Android version on the website. If the version is out of date, you may have downloaded from a third-party aggregator or an older operator-distributed link — reinstall from the official site.

Updating the App Later

Android’s auto-update doesn’t cover sideloaded apps. The operator handles updates one of two ways:

In-app update prompt. When a new version is available, opening the app shows an update prompt with a download link. Tap, the new APK downloads, and Android installs the update over the existing app (without losing data).

Manual check. Visit the operator site and re-download the APK if you suspect your version is out of date. Install over the existing app to update.

We recommend leaving the in-app update prompt enabled — it’s the path of least friction and ensures the security and feature updates the operator pushes are picked up.

What Could Go Wrong

“App not installed” error during install. Usually a sign that an old version of the app is already installed and the new APK doesn’t match its signature. Uninstall the existing app, then reinstall the fresh APK. Note: uninstalling will not affect your account or balance; those live on the operator side.

“Parse error” during install. Indicates a corrupt or partial download. Re-download the APK from the official site.

App crashes immediately on first launch. Usually a permission issue. Long-press the app icon, App Info, Permissions, ensure the required permissions (network, storage) are granted. Re-launch.

Stream quality poor on live dealer. Almost always a network issue. Check your connection (4G+ or stable WiFi). The app’s stream quality auto-adjusts; if you’re seeing 480p or below on a fast connection, log out and back in to reset the stream resolution detection.

KYC document rejected. A common quirk we’ve documented: the operator’s KYC system sometimes rejects PDF uploads and accepts JPG or PNG of the same document. If your bank statement PDF is rejected, take a JPG screenshot of the same page and re-upload.

Security Considerations Specific to APK Install

Don’t sideload from third-party APK aggregators. Mentioned above and worth repeating. The risk isn’t theoretical: stale or modified APKs have circulated for offshore casino brands, sometimes with malware overlays. Install only from the operator’s official site.

Disable the unknown-sources permission for the browser after install. Once the operator app is installed, you don’t need the Chrome permission to install from unknown sources still enabled. Settings → Apps → Chrome → Install Unknown Apps, toggle off. This reduces ongoing risk if you visit a site later that triggers a malicious download.

Use a strong account password. The app stores authentication tokens locally; if your phone is unlocked and someone else has access, they can transact on your account. Strong password, not stored elsewhere.

Enable two-factor authentication on your operator account. 1win supports 2FA via authenticator app (Google Authenticator, Authy). Enable it. The 30-second code requirement protects against unauthorised access even with credentials compromised.

When the App Doesn’t Beat the Mobile Site

Worth flagging: the app is genuinely better than the mobile web experience for slot play, live dealer, and most session-length use. Where the mobile web site is preferable:

Quick balance check / withdrawal request without launching the app. The mobile web site loads in 2–3 seconds; the app’s 5–10 second cold-start is comparable but not always worth the launch.

One-time login from a borrowed device. Don’t sideload the operator app on a borrowed device. The mobile web site logs you in once, ends when you log out, doesn’t leave a persistent app on the device.

Older Android phones below Android 8. App compatibility is genuinely worse on older Android; the mobile web experience is the better option.

For your daily phone, the app is the recommended setup. For occasional or shared-device access, the mobile web site is the lighter option.

Term Changes

The install steps above reflect 1win’s APK distribution and Android compatibility as of May 2026. The operator changes the APK build periodically (security updates, feature additions, occasional UI redesigns). The install flow itself is stable; specific permission prompts and asset-download sizes may shift between versions. Re-confirm with the operator’s currently-published Android download page if you encounter steps not covered here.