1win on iPhone for NZ — Web App Install (No App Store)

Why There’s No 1win App Store Version

Apple’s App Store policy bans real-money casino apps in most jurisdictions including New Zealand. The policy is consistent across casino operators: 1win, 22Bet, Megapari, Betsson, and most peer brands have no native iPhone app distributed through the App Store, and they don’t have one because Apple won’t allow it.

What 1win provides instead for iPhone users is a Progressive Web App (PWA) — a web-based experience that you add to your iPhone’s home screen and that behaves close to a native app once installed. The PWA is the official iPhone path supported by the operator. There is no native app coming, and any third-party site claiming to offer one is misleading at best and serving malware at worst.

This page covers what the PWA delivers, how to install it, what’s different from the Android native app, and the practical considerations for iPhone users at 1win.

What a Progressive Web App Actually Is

If you’ve installed a website to your iPhone home screen before, you’ve used a PWA. The mechanic is straightforward: Safari saves a launchable shortcut to the operator’s mobile web site, with some additional features that make the experience feel more app-like.

Standalone window. Tapping the home screen icon opens 1win in its own window without Safari’s URL bar or tab interface. The visual experience is similar to a native app.

Cached assets. The PWA caches site assets locally so subsequent launches don’t re-download everything. After the first launch, opening the PWA is quick — typically 2–4 seconds to interactive on a current iPhone.

Persistent login. Login persists across launches the same way it would on the website, with cookie or token-based authentication.

Push notifications (limited). Apple supports web push notifications on iOS 16.4 and later, with caveats. Whether 1win has implemented web push is operator-dependent and may not be enabled in all PWA versions.

What the PWA doesn’t do that a native app would:

No background processing. The PWA doesn’t run background tasks. Notifications and account updates only happen when you have it open.

No deep iOS integration. No Siri shortcuts, no native sharing extensions, no widgets.

No biometric authentication for login. PWAs can request Face ID or Touch ID on iOS 16.4+ via the WebAuthn standard but the implementation has to come from the operator side; not all PWAs offer it.

The gap between PWA and native app is smaller than it used to be. For most session-length use — slot play, live dealer, deposits and withdrawals — the PWA is functionally equivalent to a native app. The differences become apparent only at the edges.

Step 1: Open 1win.com in Safari

Must be Safari, not Chrome or Firefox or another browser. Apple restricts PWA installation to Safari on iOS — third-party browsers can render the website but cannot add it to the home screen as a PWA. (Apple has gradually loosened this in 2024–2025 in some EU jurisdictions; NZ is not in scope.)

Navigate to 1win’s official site. The operator’s mobile lobby will offer to add the site to your home screen; you can also do this manually in the next step. Either path arrives at the same result.

Step 2: Add to Home Screen

With the operator site loaded in Safari:

1. Tap the share button (square with up arrow at the bottom of the screen on iPhone, top-right on iPad).
2. Scroll the share menu to find “Add to Home Screen.” The option is below the iCloud and AirDrop options, in the secondary action list.
3. Tap “Add to Home Screen.”
4. The next screen shows the icon, name (you can edit), and URL of the bookmark. Confirm by tapping “Add” in the top-right.
5. The PWA icon appears on your home screen, identical in appearance to a native app icon.

The “Add to Home Screen” option is sometimes hidden if Safari’s share sheet has too many options enabled. If you don’t see it, scroll the share menu further down or tap “Edit Actions” at the bottom to enable it.

Step 3: First Launch and Login

Tap the home screen icon. The PWA opens in a standalone window. Log in with your existing 1win credentials, or register a new account if you don’t yet have one.

First launch takes 5–10 seconds as the PWA loads its asset bundle and authenticates. Subsequent launches are 2–4 seconds.

What Works in the iPhone PWA

Account management. Deposits, withdrawals, KYC document upload, password change, deposit limit settings — all functionally identical to the desktop website experience.

Slot play. Slot games run cleanly. Touch controls are well-mapped for portrait orientation; landscape works but the interface scales modestly. Auto-spin, RTP filters, game search all work.

Live dealer. Stream quality scales to your network. 720p baseline, 1080p available on capable networks. Stream load time is 4–7 seconds for the first session, 2–4 seconds for re-joins. Touch betting positions are larger than on Android in some implementations.

Crash games. Aviator, Lucky Jet, Mines, and the rest run on the PWA without compromise. The cash-out button on Aviator is responsive on a good connection.

Customer support. In-PWA live chat works. Push notifications for new chat messages may not work depending on iOS version and operator implementation; check periodically during a chat session.

What’s Worse Than Android

Re-authentication after long idle periods. This is the documented PWA limitation that catches iPhone users. iOS aggressively reclaims background memory; if the PWA hasn’t been opened in 24–48 hours and your authentication token has expired, you’ll re-login when you next open it. Not a big deal, but slightly more friction than the Android app’s longer-lived authentication.

No native push notifications in some implementations. If the operator hasn’t implemented iOS 16.4 web push, the PWA can’t notify you about deposit completions, bonus availability, or chat replies while it’s not open. Android handles this via the operator-published notification channels in the native app.

No haptic feedback on betting actions. The Android app uses Android’s haptic engine on key interactions (cash-out, big win). The PWA on iOS doesn’t have this, partly because Safari’s haptic API is more restrictive.

No offline asset access. If you launch the PWA without a network connection, you’ll see a connection error. The native Android app caches more aggressively and can show recent state without a fresh connection.

None of these are dealbreakers. They’re noticeable enough that an Android user switching to iPhone (or vice versa) will recognise the difference.

Updating the PWA

The PWA updates automatically when the operator publishes a new version. There’s no manual update step; opening the PWA after an operator update simply loads the new version on next launch.

If you want to manually clear the cache and force a fresh load:

1. Open Settings → Safari → Advanced → Website Data.
2. Search for the operator’s domain.
3. Tap and delete to clear cached site data.
4. Re-launch the PWA. It downloads fresh assets on next launch.

This is rarely necessary but can resolve display issues if the PWA shows out-of-date pricing or stale content after an operator promotion change.

Removing the PWA

If you decide to remove the PWA from your home screen:

1. Long-press the icon.
2. Tap “Remove App” (or “Delete Bookmark” on older iOS versions).
3. Confirm.

This removes the home screen icon and clears the PWA’s local cache. Your account on the operator side is unaffected; you can re-add the PWA at any time.

Security Considerations Specific to iPhone PWA

No risk of sideload-related malware. Unlike Android APK install, iPhone PWA install doesn’t involve permission overrides or unknown-source warnings. The PWA is just a Safari bookmark with extra capabilities. There’s no app to install in the security sense.

Use a strong password. The PWA stores authentication tokens. If your iPhone is unlocked and someone else has access, they can transact on your account. Use a unique, strong password.

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 even with credentials compromised.

Enable Face ID for the operator app via Safari’s password autofill. iOS can auto-fill saved passwords with Face ID, including for the PWA. Set this up via Settings → Passwords for fastest secure login.

When the PWA Isn’t Enough

For 95% of iPhone users at 1win, the PWA is fine. Where it might not be enough:

Heavy live dealer use during commute. iOS background-cleanup of the PWA mid-session can interrupt a live dealer table if you switch apps and come back. Use the PWA in foreground continuously during live dealer sessions, or accept the occasional re-join.

Push-notification-dependent workflow. If you rely on getting notified when a withdrawal completes or a bonus credits, and the operator hasn’t implemented iOS 16.4 web push, you’ll miss notifications until you next open the PWA.

Very-old iPhones. iPhone 8 and earlier (iOS 16 max) work but with degraded performance. If you’re on these older iPhones, the mobile web site without the PWA install is a lighter option.

For everyone else, the PWA is the recommended setup.

Term Changes

The PWA install steps above reflect Safari’s add-to-home-screen flow as of iOS 18 (May 2026). Apple modifies the share sheet and Safari interface periodically; specific menu paths may shift in future iOS versions. The underlying install mechanic is stable — add to home screen, launch, log in. Re-confirm with Apple’s published instructions or 1win’s iPhone download page if specific steps don’t match what you see.