Perhaps because we are constantly swamped with push notifications, they can go overlooked as a messaging category. They are nevertheless an important medium of modern communication, and a more diverse one than you might think.
Push notifications initialize interactions between a recipient and a sender, in an era of communication where response times are measured in seconds. Such high-frequency information requires effective distillation to remain efficient and to avoid flooding recipients with noise.
Users don’t have to request push notifications and don’t have to sort through an archive to view them. Because push notifications propagate even if the associated app isn’t open, they are durable to intermittent usage of your app.
This makes push notifications a preferred way to inform a user about changes to a system, to announce new messages or in-app content, or to re-engage in an abandoned process. In comparison with channels such as email, SMS, or social media, push notifications allow you to pinpoint a user’s attention to a specific event, without overwhelming them.
This article will dive into the topic of push notifications and will explain how to use Courier’s push API to deliver simple, one-time push notifications to Android or iOS systems. Web notifications are also supported by a different Courier product (toast messages), which is not covered here.
Push messages are a surprisingly wide-ranging topic. As a software developer, there are contexts where you need to provide users with small pieces of unsolicited information – whether on desktop or mobile, in a browser or in an app, brief contact from out-of-focus programs are vital for program function.
A top-down notification box on an Ubuntu desktop __A top-down notification box on an Ubuntu desktop
Commercial computer systems today are capable of running dozens of programs simultaneously, but rarely do users have visual space on their device to view more than a couple at once. Push notifications in a desktop help visually hidden processes claim user attention for events that require their input.
Test your own browser notifications at Ben Kennish’s website.
Similarly to desktop, the proliferation of tab-capable modern browsers has necessitated browser push notifications. Information about audio media from a background tab, new content in an auto-refreshing page, or the completion of a file download are all intermittent events that often require user response, and are therefore announced by push.
A typical Android lock screen
Mobile push notifications are very different from desktop and browser pushes. For one thing, mobile devices are generally used more intermittently than computers or tablets. This means that push notifications are important, asynchronous updates that keep users informed.
Additionally, mobile devices have a much smaller visual field for information. That makes push notifications more common, but also means there is more competition for attention among all the push notifications.
Mobile push notifications are therefore extremely important to the usage of a mobile device. Unlike other types of push notification, mobile pushes have a separate pipeline for generating, queuing, and distributing individual pushes. The software and servers that deliver these pushes are operated by push providers.
Keep in mind that mobile push notifications are NOT the same as an in-app notification. In-app notifications, such as confirmation messages after a user changes important settings, occur inside the app, in a context where user attention can already be assumed, and are not queued or distributed using the same push notification network as a mobile push. To learn more about in-app notifications, see our article highlighting the use of toast messages using Courier.
Mobile push notifications are sent to users through a specific provider’s service. Like a mobile network, that provider facilitates collecting and distributing the notifications. (Unlike a mobile network, these providers’ dispatches are broadcast not by cell towers, but by internet servers.)
Each provider has a number of advantages and disadvantages. Some providers – like Firebase Cloud Messaging – might already be ready to integrate with your existing customer tools. Others, like Apple Push Notification Service, are well adapted to a particular mobile development platform. Providers like OneSignal might offer support for your entire suite of customer messaging channels.
Courier is not a push provider itself, so why bring Courier into the mix? Although most push services are reliable utilities with their own push API, they really only handle the message delivery. Metrics about the messages, including their conversion rates, and advanced controls for user preferences are still the domain of the back-end engineer.
Courier supports and extends the existing API of your push provider, while delivering incredible customization options. It enables you to match customer details to the message, handle messaging across channels, and create extensive logging and error handling for when phones can’t get connectivity. Courier also integrates well with adjacent tools in your stack – including customer data platforms like RudderStack and Segment, and cloud observability platforms like Datadog.
Whatever mobile push use case your marketing team might dream up, Courier can deliver. Courier supports the deployment of many push providers. Our long-term support and the peace of mind we offer will help you get on track while building up your own service.
Firebase Cloud Messenger is a common push notification service that supports easy Android and iOS development. Our docs outline a simple but comprehensive process for testing out pushes via Courier in Firebase Cloud Messenger.
With Courier, you have out-of-the-box support for your marketing strategy. What’s more, you have that same support for channels such as SMS, email, Slack, or MS Teams.
If you want to learn more about our support for your push services, you can read through the documentation for our push notification API, request a demo, or sign up to the app, where you can send 10,000 messages per month, for free.
Let us keep you in touch with your users!
Best Practices for SMS Tools and Text Message API Implementation
Courier delivers easy access to the messaging providers you use, all in a familiar language and with documentation that’s comprehensive and easy to follow. This page will give you an overview of the SMS providers supported by Courier’s text messaging API, so that you can assess if moving towards a messaging management tool is right for you.
November 14, 2023
Toast messages, their use cases, and examples
Toast messages are an established part of modern technology – both a form of messaging and a protocol for delivering information. If you want an effective marketing strategy, an easy-to-use product, or a way to redirect traffic to new features, you would benefit from understanding toast messages and how they compare to other messaging formats. Read on to learn more about the toast message and how it lines up with other communication formats, and for advice on when the toast message is most appropriate for your users.
October 30, 2023