keepcalculator

06 Numbers and Powers

Local Alerts vs Remote Push: Notification Types

Card No. 06·80336 · Updated · Standard formula, shown below

Local alerts and remote push notifications are the two ways an app can notify you, and the core difference is where the message originates: local alerts are scheduled and triggered entirely on your device by the app itself, while remote push notifications are sent from a server over the internet. This article explains both types, how they work under the hood, when to use each, and common pitfalls developers and users encounter.

Background: How Notifications Evolved

Early smartphones had no unified notification system. Each app had to run in the foreground to show anything. Apple introduced the Notification Center in 2009 (iOS 3), and Android followed with its own system. Remote push notifications arrived as a way to deliver time-sensitive information without keeping an app open. Local notifications were added later, allowing apps to schedule alerts on the device itself, even when offline. Today, both types are first-class citizens on iOS (via UserNotifications framework) and Android (via NotificationManager and WorkManager).

How Local Alerts Work

Local alerts are created and scheduled by the app on the user’s device. The app asks the operating system to show a notification at a specific time or when the user enters a location. No internet connection is required after the scheduling is done. Common examples:

  • Reminder apps (e.g., “Take medication at 8 AM”)
  • Alarm clocks
  • Calendar event alerts
  • Fitness apps that remind you to stand up every hour

On iOS, the app registers a notification request with the system, which handles the delivery even if the app is terminated. On Android, similar APIs exist, but the app must be at least scheduled via WorkManager or AlarmManager, and some OEMs (like Xiaomi or Huawei) have aggressive battery management that can delay local alerts unless the app is whitelisted.

How Remote Push Notifications Work

Remote push notifications (often just “push”) are sent from a server to the device via the platform’s push service: Apple Push Notification Service (APNs) for iOS, Firebase Cloud Messaging (FCM) for Android, and Web Push for browsers. The flow:

  1. Your device registers with the platform and receives a unique device token.
  2. Your app sends that token to your server.
  3. When you want to notify the user, your server sends a message to the push service with the token and payload.
  4. The push service delivers the message to the device, which displays it even if the app is closed.

Push requires an internet connection and a server. Examples: messaging apps (new message), news alerts, social media likes, shipping updates.

Key Differences at a Glance

Aspect Local Alerts Remote Push
Origin Device itself Server over internet
Internet needed No (after scheduling) Yes
Real-time from server No Yes
User permission Required (same as push) Required
Can be triggered by server event No Yes
Battery impact Low (scheduled) Moderate (network)
Examples Alarms, reminders Chat messages, breaking news

How to Choose: Which Should You Use?

The decision depends on what triggers the notification. Ask yourself: does the notification need to reflect something that happens on a server, or can it be scheduled in advance?

  • Use local alerts when the notification is based on a time or location the user sets, and no server involvement is needed. Examples: “Water your plants every Tuesday,” “Meeting in 10 minutes.”
  • Use remote push when the notification is triggered by an external event, such as a new email, a friend’s message, or a price drop. You need a server to detect the event and send the push.
  • Hybrid approach: Some apps use local alerts for scheduled reminders and push for real-time events. For example, a weather app might send a push for severe weather warnings but use local alerts for daily forecasts at a user-chosen time.

Common Problems and Misconceptions

One common misconception is that push notifications are more reliable than local alerts. In reality, push delivery is not guaranteed—the platform may throttle or delay messages, and the device may be offline. Local alerts, once scheduled, are delivered by the OS on time (subject to battery optimizations). Another issue: users often revoke notification permissions when apps over-notify. Both types require permission, and once denied, you cannot prompt again (on iOS) or must guide the user to settings (on Android).

Developers also confuse “silent push” (which wakes the app in the background) with regular push. Silent pushes have stricter limits and are not meant for user-facing alerts. Also, local alerts cannot be updated once scheduled on iOS—you must cancel and reschedule. Android allows updating via notification ID.

Safety, Privacy, and Best Practices

Both notification types can leak sensitive information on the lock screen. Always consider what appears in the preview. For example, a banking app should not show full account balances in a push. Use the OS’s “sensitive notification” flags or redact content. Also, respect the user’s time: there is no official limit, but sending more than a few notifications per hour is a common cause of app uninstalls. For local alerts, be aware of time zones—if the user travels, a scheduled alert may fire at the wrong local time unless you handle timezone changes.

For remote push, security is critical: never send sensitive data in the payload; use it only as a signal to fetch content from your server. Both iOS and Android support end-to-end encryption for the push channel, but the payload is visible to the platform unless you encrypt it yourself.

Frequently Asked Questions

Can I receive a local alert if my phone is off?

No. If the device is powered off, no notification will be delivered when it turns back on. Local alerts are scheduled on the device, but they are not stored for later delivery if the device was off at the scheduled time. Remote push messages may be queued by the platform for a short period (usually up to 24 hours) and delivered when the device comes online, but this is not guaranteed.

Do local alerts work without an internet connection?

Yes, that is their main advantage. Once the alert is scheduled, the OS handles delivery locally, so no internet is needed. Remote push, by definition, requires an internet connection to receive the message.

Which type is more battery-efficient?

Local alerts are generally more battery-efficient because they involve no network activity. Remote push uses a persistent connection to the push service, which consumes some battery, though modern systems use efficient push channels. However, the difference is usually negligible for a few notifications per day.

Can a remote push trigger a local alert on the device?

Yes, a common pattern is to send a “silent push” that wakes the app, which then schedules a local alert. This is used when you want the notification to appear at a specific time after receiving the server signal, or when you need to customize the notification content beyond what the push payload allows.

Why do my local alerts sometimes not appear?

Common reasons: the app’s notification permission was revoked, the device is in Do Not Disturb mode, or the app was force-quit (on iOS, force-quitting does not prevent local alerts, but on some Android OEMs it does). Also, if the device restarts, some Android OEMs clear scheduled alarms unless the app has auto-start permission.

Is it possible to send a push notification without a server?

No, remote push requires a server to send the request to the push service. However, for testing, you can use tools like Postman or the platform’s console to send a push directly. For production, you need a backend.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →