Push notifications explained: iOS vs Android browser alerts

Push notifications are the small banners, badges and lock-screen messages a phone shows when an app or a website wants your attention. For a casino brand they are the main channel for telling a player that a bonus has landed, a deposit needs confirming or a tournament has started. Anyone installing the Casushi app, or opening the Casushi mobile site in a browser, will meet a permission prompt within minutes of signing up. What happens after that tap differs sharply between an iPhone and an Android handset, and the difference matters more than most beginners expect.

The short version: on iOS, alerts from the Casushi iPhone app travel through Apple’s Push Notification service and are governed by a single per-app switch in Settings. On Android, the picture splits in two. Players who install the Casushi Android app get standard app notifications controlled from the device’s app settings. Players who use the Casushi mobile site in Chrome get browser notifications instead, and those depend on Chrome staying alive in the background. The Casushi casino app is not available as a standalone APK file, so Android users who avoid app stores typically end up on the browser route whether they intended to or not.

This primer sets out how each delivery route works, how to switch alerts on and off, and where the practical trade-offs sit: battery drain from a background browser, data use on mobile connections, and the privacy question of a casino logo appearing on a shared lock screen. It also flags a point worth knowing early. The Casushi app cashier manages payments, and the mobile lobby includes the welcome offer, but notification settings sit outside both. They are a device-level control, not an account-level one, so two players on the same account with different phones can end up with completely different alert behaviour.

What push notifications are and how casino apps use them

A push notification is a short message a service sends to your device without you opening anything first. It arrives as a banner, an alert on the lock screen or a badge on an app icon. The key detail is that the message is pushed from outside rather than pulled by you: the sender decides when it fires, and the device decides how to display it depending on your settings.

Two things travel with every push: a title and a body of text, sometimes with an image or a deep link that opens a specific screen. That link is why a casino app such as Casushi can send an alert about a bonus drop and have it land directly on the promotions page rather than the home screen. The message itself is small, usually a few hundred bytes. What makes push notifications worth understanding is not the technology but the intent behind them.

Casino apps send notifications for three broad reasons, and they map onto the customer journey fairly neatly.

• Bonus drops and offers. The mobile lobby includes the welcome offer, and a push is the standard way to announce a new promotion, a free spins window or a reload deal before it expires. These are the most frequent alerts from any operator.
• Deposit reminders and cashier prompts. The Casushi app cashier manages payments, and notifications can flag a pending deposit, a completed withdrawal or a payment method that needs re-verifying. This category is functional rather than promotional.
• Game updates and account events. New titles going live, a jackpot crossing a threshold, a KYC document request, a login from an unrecognised device. These are lower volume but higher value per message.

For a beginner, the practical question is not what a notification is but how many you want. A casino app has an incentive to send often, because each push is a chance to bring a lapsed player back to the mobile lobby. The player has an incentive to stay informed about money matters (deposits, withdrawals, verification) while ignoring the marketing layer. Most platforms let you split those two streams, and section four covers exactly how.

Push notifications are also one of the clearest examples of how the same feature behaves differently across platforms. Apple users download the Casushi app from the App Store, and those alerts are routed through Apple’s Push Notification service. Android users access the Casushi site through a mobile browser, and browser notifications follow a different set of rules entirely, including the fact that Chrome must be running in the background for them to arrive. Casushi does not publish a standalone Android APK file, so Android alerts are browser alerts by default rather than app alerts.

There is a privacy dimension worth flagging early. A notification sits on your lock screen, visible to anyone who picks up the phone. Message text can reveal that you hold a casino account, and a poorly written alert can reveal more than that. Both the Casushi app and the Casushi mobile site offer controls to hide notification previews, and responsible gambling tools often include the option to switch off promotional pushes altogether while keeping transactional ones active.

One last point of context. This website operates as an information page only: it explains how these systems work, it does not send notifications itself and it does not host games or handle deposits. Everything below describes the mechanics you will encounter inside the Casushi app or the Casushi mobile site, not features offered here.

The delivery route for Casushi notifications on iPhone versus Android

Push notifications take a different route to an iPhone than they do to an Android handset, and the difference matters for anyone relying on alerts from a casino brand. Apple runs a single delivery service, the Apple Push Notification service, and every app on iOS must send its messages through it. Google’s equivalent, Firebase Cloud Messaging, handles native Android apps, but browser notifications follow a separate path entirely, generated by the browser itself rather than by an installed application.

On iPhone, the chain starts when the Casushi app registers with Apple’s servers and receives a device token. That token is passed to Casushi’s own backend, which sends each alert to Apple with the token attached. Apple then pushes the message to the handset. The practical consequence is that alerts from the Casushi iOS app do not depend on the app being open. They arrive whether the phone is locked or the app has been swiped away, provided the user granted permission when prompted. They can be silenced per app without touching the rest of the system, by going to Settings > Notifications, selecting Casushi and switching off Allow Notifications or trimming alert styles and sounds.

Android works differently depending on how the player accesses Casushi. Apple users download the Casushi app from the App Store, and Android users access the Casushi site through a mobile browser. Casushi does not publish a standalone Android APK file, so there is no sideloaded native app on that platform and no Firebase-delivered alerts. Instead, the Casushi mobile site can request browser notification permission, and those alerts are issued by Chrome through the web push standard. The catch is the delivery window: Chrome must be running in the background for the message to surface. Close Chrome completely, and the notifications stop until it is reopened. On many Android builds the operating system will also throttle or kill background browser processes to save power, which adds a second layer of unreliability that the iOS route does not have.

The two paths diverge at several concrete points:

• iOS: delivery runs through Apple’s servers to the installed app; alerts arrive with the app closed.
• Android: delivery runs through Chrome to the browser; alerts arrive only while Chrome is alive in the background.
• iOS: permission is granted once at app level and controlled in Settings > Notifications.
• Android: permission is granted per site in Chrome, and clearing site data or resetting Chrome removes it.
• iOS: no battery cost beyond the app’s own background refresh.
• Android: keeping Chrome resident for alerts draws battery and mobile data over a session.

There is also a shortcut worth knowing about on Android. Adding the Casushi mobile site to the home screen creates a shortcut that opens in its own Chrome window, and on recent Android versions web notifications from that shortcut behave much like app alerts, complete with a badge on the icon. It is still Chrome underneath, so the background requirement stands, but the experience sits closer to a native app. The responsive site detects screen dimensions automatically, so the lobby and cashier render correctly whether the shortcut opens on a 5.5-inch phone or a tablet.

One point of consistency: whichever route the alert takes, tapping it opens the destination, usually the mobile lobby where the welcome offer and current promotions sit. Neither Apple nor Chrome reads the content of a notification beyond what is needed to display it, and the message payload is encrypted in transit on both platforms. What differs is reliability and control, not privacy of the alert itself. A player who wants alerts to arrive promptly should favour the iOS app; a player on Android should expect browser alerts to work best when Chrome is left running and battery optimisation is relaxed for it.

Setting up alerts in the Casushi app and on the Casushi mobile site

Enabling alerts follows a different route depending on whether you are using the Casushi app on an iPhone, the Casushi Android app, or the Casushi mobile site in a browser. The permission prompts look similar but they are issued by different systems, and that shapes what you can switch off later.

Casushi iPhone app. Apple users download the Casushi app from the App Store, and the notification request appears the first time the app launches or shortly after a first login. The prompt is generated by iOS, not by the casino, and it offers just two choices: Allow or Don’t Allow. Tapping Allow registers the device with Apple’s push service and the app can then send bonus drops and deposit reminders. Tapping Don’t Allow is not permanent: the app cannot ask again, so you must go to Settings > Notifications > Casushi and enable Allow Notifications manually. If you want alerts but not the sound, enable notifications and switch off Sounds in the same screen. The Casushi app supports Face ID logins, but Face ID is an authentication feature and has no bearing on whether alerts arrive.

Casushi Android app. Android handles permission in two layers. On Android 13 and later, the system shows an Allow Notifications prompt on first run, and the app also offers a channel list so you can separate bonus alerts from deposit reminders. On older versions, notifications are switched on by default and you turn them off per app in Settings > Apps > Casushi > Notifications. The Casushi app is not distributed as a standalone APK file, so there is no sideloaded build with a different permission model; the prompt you see is the standard Android one.

Casushi mobile site. Browser alerts are a separate mechanism entirely. Open the Casushi mobile site in Chrome on Android or Safari on iOS, log in, and look for the notification prompt that the browser itself displays, usually a small banner at the top or bottom of the screen. On Chrome for Android, tap Allow when the prompt reads something like «Casushi wants to send notifications». On Safari for iOS 16.4 and later, the site must first be added to the home screen shortcut before Safari will offer web push at all; until then, no prompt appears. The responsive site detects screen dimensions automatically, but that has no effect on notification permissions, which are tied to the browser profile rather than the layout.

The practical difference matters. App-based alerts are delivered through Apple’s servers or Google’s service and arrive whether or not the app is open. Browser-based alerts on Android are delivered through Chrome, so they only arrive while Chrome is running in the background, and they stop when Chrome is closed. On iOS, web push from a home screen shortcut behaves more like an app alert but still depends on the shortcut being present.

One point of caution for beginners: the mobile lobby includes the welcome offer, and some promotional banners invite you to «enable alerts» before you have logged in. Granting permission before you have reviewed the account settings means you may receive marketing pushes before you have set any preferences. Enable alerts after login, when you can see which categories the app or site intends to send.

Managing and turning off Casushi notifications on each device

Silencing alerts on iPhone and Android step by step

On iPhone, notification control sits in one place and applies to every app installed on the device. Open Settings, tap Notifications, scroll to the Casushi app and tap it. The toggle at the top labelled Allow Notifications is the master switch. Turning it off stops banners, sounds and badges in a single action, and the app cannot override that choice from inside its own menus. For finer control, leave the master switch on and adjust the three delivery styles underneath: Lock Screen, Notification Centre and Banners. A beginner who wants the alerts but not the noise should keep Banners enabled and switch off Sounds, which silences the ping without hiding the message. The Casushi app supports Face ID logins, so a notification appearing on the lock screen can be tapped and opened without typing a password, though anyone holding the phone can read the preview text unless Show Previews is set to When Unlocked.

Android splits the job between two layers. For the Casushi Android app, open Settings, then Apps, then Casushi, then Notifications. Each notification channel the app has registered appears as a separate line, so a user can silence bonus drops while keeping deposit confirmations audible. This channel-level control is finer than iOS offers and is worth knowing about, because switching off the master toggle kills everything at once and there is no way to restore just one category from inside the app.

Browser alerts on Android follow a different path entirely. They belong to Chrome, not to the site. To review or revoke them, open Chrome, tap the three-dot menu, choose Settings, then Site settings, then Notifications. The Casushi domain appears in the allowed list with a toggle beside it. Switching that off stops all browser alerts from the site immediately. The same list can be reached by tapping the padlock icon in the address bar while the site is open, which is faster for a one-off change.

The practical difference between the two routes matters more than the menu names. App notifications on Android are handled by the operating system and can arrive when the phone is idle, provided the app has not been force-stopped. Browser notifications are handled by Chrome, so they only arrive while Chrome is running in the background. Close Chrome from the recent-apps screen and the alerts stop, with no error message and no queued delivery. A user who enables browser alerts, closes the browser and then wonders why nothing arrives has not hit a bug. The delivery channel simply went away.

Customising rather than silencing is the better default for most people. On iOS, the per-app screen also controls where alerts appear, so keeping Notification Centre on and Banners off produces a quiet archive that can be checked at will. On Android, long-pressing an incoming notification opens its channel settings directly, which is the quickest way to mute a category that has become repetitive. A user who wants to stop everything at once on either platform can also revoke permission from inside the app or site settings, though the browser route requires the page to be open to reach the prompt again.

One habit pays off across both systems: review the list monthly. Notification permissions accumulate quietly, and an alert enabled for a one-off bonus can keep firing long after the promotion ends.

Common notification problems and privacy considerations

Missed or unwanted alerts: what to check first

When alerts stop arriving, the fault is usually one of three things: a permission that was switched off, a battery saver that has put Chrome to sleep, or a background process that is no longer running. On iOS, open Settings > Notifications and confirm that the Casushi app still appears in the list with Allow Notifications enabled. Updates to iOS occasionally reset per-app permissions, so a silent app after a software update is common rather than unusual.

On Android, browser alerts are more fragile. The Casushi site through a mobile browser relies on Chrome being open in the background, so closing the browser ends delivery until you reopen it. Battery optimisation settings on Samsung, Xiaomi and similar handsets kill background apps aggressively, and a phone that has been idle for a few hours may simply stop relaying anything. Check that Chrome is excluded from battery restrictions, and confirm site notifications are allowed in Chrome’s Settings > Site settings > Notifications.

Unwanted alerts tend to be a permission problem in reverse. A single tap on «Allow» during a sign-up flow can leave you receiving every bonus drop and deposit prompt. Both platforms let you revoke that in seconds. On iPhone, toggle Allow Notifications off for the app. On Android, revoke the site permission in Chrome, or block the app’s channel in Settings > Apps > Notifications. If alerts arrive at the wrong time rather than too often, scheduling quiet hours is usually better than switching notifications off entirely.

Battery, data and keeping casino alerts discreet

Background Chrome is not free. Keeping the browser resident so browser notifications can be delivered costs battery, typically a few percent over a day on mid-range Android handsets, and uses mobile data each time an alert is fetched. On a metered connection, a steady stream of promotional pushes adds up. The native Casushi iOS app avoids the browser layer altogether because Apple’s push service handles delivery, which is lighter on the handset than a persistent browser process. Android users who want the same efficiency can add a home screen shortcut from Chrome, which opens the mobile lobby quickly without changing how alerts are delivered.

Privacy matters more with gambling notifications than with most app categories. A lock screen that displays «Deposit bonus waiting» is visible to anyone nearby. Practical steps:

• Set the app or site to show notifications without preview text, so only the sender name appears on the lock screen.
• Turn off notification sounds and banners for the casino app, keeping only badges or the notification centre.
• Use Face ID login on the Casushi app so a borrowed phone does not open the cashier, and keep the app out of any shared device.
• Disable push notifications entirely during periods when you are not playing, rather than relying on willpower to ignore them.
• Use the responsible gambling tools on the Casushi mobile site, including deposit limits and session reminders, alongside notification settings so the two work together.

One structural point worth knowing: the Casushi app and mobile site are operated by the brand, while this website operates as an information page only. It does not send notifications, hold an account or process payments, so any alert you receive comes from the operator, not from a guide like this one. If you are unsure whether a notification is genuine, open the app or site directly rather than tapping a link in the message. A secure download from the official App Store listing, or typing the address into the browser, removes the main route for phishing pushes that imitate casino branding.

Start with one deliberate action rather than a full notification audit. Open the Casushi app or the Casushi mobile site, find the notification settings, and decide which alert types you actually want: bonus drops, deposit reminders, game updates, or none at all. Most players are better served by leaving bonus alerts on and switching off promotional pushes, because a bonus notification has a clear trigger and a deadline, while generic marketing messages arrive on someone else’s schedule. On iOS, that means Settings > Notifications > Casushi and toggling the categories you want to keep. On Android, check the app’s own settings first, then Chrome’s site settings if you enabled browser alerts. If you use both the Casushi iPhone app and the Casushi mobile site in a browser, set them up separately; they are distinct channels with separate permissions, and silencing one does nothing to the other.

Then test it. Trigger a real notification by leaving the app or browser closed for an hour or two and see whether anything arrives. If nothing does, the permission was probably never granted, or Chrome was closed on Android, which stops browser alerts entirely. If too much arrives, revisit the per-app controls rather than deleting the app. It also helps to know what you are installing: Apple users download the Casushi app from the App Store, Android users access the Casushi site through a mobile browser, and Casushi does not publish a standalone Android APK file, so any APK claiming to be the official app is not one. Keep your alerts discreet by turning off lock screen previews in your phone’s notification settings, and use the responsible gambling tools on the Casushi mobile site if notifications start nudging you to play more than you planned. This website operates as an information page only and does not take deposits or run games, so any account, cashier deposit or bonus claim happens on the operator’s own platform. Set the alerts once, check them after a week, and adjust from there; a five-minute review now saves months of ignored or unwanted pushes later.