Ably can deliver native push notifications to devices using, amongst others, Apple’s Push Notification service and Google’s Firebase Cloud Messaging service. Native push notifications, unlike Ably’s channel based pub/sub messaging, do not require the device to maintain a connection to Ably, as the underlying platform or OS is responsible for maintaining its own battery-efficient transport to receive push notifications. Therefore, native push notifications are commonly used to display visual notifications to users or launch a background process for an app in a battery-efficient manner.
Delivering push notifications
As shown above, Ably provides two models for delivering push notifications to devices:
Ably provides a REST API that allows native push notifications to be delivered directly to:
- Devices identified by their unique device ID
- Devices identified by their assigned
- Devices identified by the recipient details of the native push transport such as their unique
registrationTokenin the case of FCM,
deviceTokenin the case of APNS, or
encryptionKeyin the case of a Web device (experimental). This means is particularly useful when migrating to Ably with existing push notification target devices.
The model for delivering push notifications to devices over channels is intentionally very similar to how messages are normally delivered using Ably’s pub/sub channel. For example, a normal message published on an Ably channel is broadcast immediately to all realtime subscribers of that channel. When broadcasting push notifications on channels, however, the process is the same with the exception that the subscribers (devices receiving push notifications) are registered in advance using our API and the message itself must contain an extra push notification payload that specifies the optional visual format and optional data payload of the native push notification.
Activating a device and receiving notifications
Every device that will receive push notifications must activate itself with the local operating system or framework, and hook into the push notification services that the underlying platform provides. This functionality is platform-specific and can also vary considerably across not just platforms, but also across the push services that operate on those platforms such as GCM and FCM, both of which are available on the Android platform.
The Ably client libraries aim to abstract away this complexity and platform-specific behaviour by providing a consistent API for device activation, maintenance of the device registration, and for subscription to Ably channels for receiving push notifications.
Managing devices and subscriptions
Whilst the realtime client libraries provide APIs for a device to activate itself (via
client.push) and subscribe for push notifications (via
channel.push), those APIs are intentionally limited to actions pertaining to the device it is run on.
Ably currently offers support for push notifications on the following platforms:
- Apple Push Notifications
- supported on all mobile devices running iOS and desktop devices running OS X
- Firebase Cloud Messaging
- supported on all Android and iOS devices, although we use FCM exclusively for Android message delivery
- Experimental W3C Push API
- experimental support for modern W3C compliant browsers (this does not include Apple’s Safari browser). Get in touch if you want to use this.
We no longer support Google Cloud Messaging; this is deprecated by Google, in favour of FCM, and the service will soon be terminated altogether.
Downloading a client library with push support
The following Ably client library SDKs provide support for activation and receiving of native push notifications:
- Android SDK
- iOS Objective-C and Swift SDK
- General Availability Support for Android and iOS
- Experimental support for Chrome, Firefox and Opera. Apple’s Safari Notifications planned.
- Custom notification formats and badges for iOS and Android. Browsers receive the notification in a Web Worker which is in turn responsible for presenting a visual notification to the user (this is an experimental feature).
- Both visual notifications and data payloads can be sent to mobile devices.
- Any number of mobile and browser devices can be registered on pub/sub channels. Each time a message is published with a push notification payload, Ably will ensure that all registered devices receive the push notification in near realtime.
- Scale to millions of devices simultaneously by leveraging Ably’s global platform.
- User-centric device registration allowing devices to be grouped by user (
- Filters can be applied to notifications such as client ID, connection ID or device type, or alternatively you can push message directly to devices or users via our API.
- Realtime metrics for your delivered and undelivered push notifications.
- Error logging on a dedicated metachannel (
If you wish to see step by step instructions to set up, send and receive push notifications on your mobile devices, you can checkout our tutorials for iOS and Android, with both direct device registration and registration via server examples.
Smart Notifications (Not yet released)
Ably’s Smart Notifications will offer a less intrusive and more effective way to notify your users with native iOS, Android and browser notifications. Instead of delivering “dumb” push notifications to your users when you wish to get their attention, Ably allows you to deliver messages based on a user’s connection state, their active device and their current context within your application. This means you can send less but more effective notifications to your users. Find out more.
Get in touch to find out more.
How do Smart Notifications work?
When a message is published on a pub/sub channel, a smart notification payload and rules can optionally be included with the message. When the Ably service receives a message with a smart notification payload, it will do one of two things:
- If the notification is configured as a “dumb” push notification, it will deliver the push notification to the relevant devices associated with the pub/sub channel. This is a common pattern with other vendors and it assumes that if the registered device app is not active, a visual push notification will be displayed, and if the app is open and active, the visual push notification will be suppressed. In the case of a data push notification, it will be always be delivered and no visual indicator is shown to the user.
- If the notification is configured as a “smart” push notification, then Ably will process the rules for each smart notification in a user-centric way, such that the user is notified in the most effective way on the most relevant device based on their current context. For example, if a user has your mobile app installed but also uses your web app during office hours, and a notification is sent whilst the user is currently using the web app, then a visual notification can be shown only on the open web app, and the unnecessary duplicate push notification to their device can be suppressed. If however, after some configured time, the user has not responded to the message in the web app, a follow up native mobile push notification could be triggered automatically by Ably.