Push Notification

A push notification is a message that is "pushed" from backend server or application to user interface, e.g. (But not limited to) mobile applications and desktop applications. It is more user experience specific which is different from Push technology, which pushes the requests between components such as server to server communication. A common scenario of push notification is the client application pops up a message in front of application's user information, along with the alert sounds. The notification could also be coupled with images and hypertext link in some cases. Via interacting with the push notification it usually brings up the client applications to the front.

Push notification use cases

Push notification is usually used for the applications to bring information to the user for their attention. The messages could fall into the following categories:

• Chat messages. E.g. Facebook messenger that brings the chat sent from the other users.
• Vendor's special offers. E.g.: A vendor may want to advertise their social offers to the customers.
• Event reminder. E.g.: Some application may allow the customer to create reminder or alert for a specific time.
• Subscribed topics changes. E.g.: Some customers may use Aotol page monitor to track certain web page change.

Push notification history

Push notification was first introduced by Apple in 2009. In 2010 Google released its own service, Google Cloud to Device Messaging. November 2015, Microsoft announced that the WNS would be expanded to utilize the Universal Windows Platform architecture, allowing for push data to be sent to Windows 10, Windows 10 Mobile, Xbox, as well as other supported platforms using universal API calls and POST requests.

Type of push notification

Push notification is mainly divided into 2 approaches:

• Local notification
• Remote notification

For local notification the application schedules the notification into local device's OS, alternatively, set as a timer in the application itself if it is able to continuously running at the backend, and when the time of the events comes or the programmed condition of event is met, display the message in front of the application's user interface. For remote notification it is usually handled by remote server. Under this scenario the client application needs to be registered on the server with a unique key e.g.: UUID, and the server fires the message against the unique key to deliver the message to the client application via client/server agreed protocol such as HTTP, and then the client displays the message received.

Approach of push notification

The push notification could display in various ways:

• Banner on the top the screen
• A Pop up "bubble" from the button task bar
• A dialog box that interrupts and blocks the view of the front running application

A typical notification usually contains:

• Title
• Message details

It could also contain the following:

• Image
• Video
• Website link
• Other document attachment (Such as .txt file)

While push notification comes, it may also play alert sounds to attract user's attention.

Further reading

• "Push Notifications Explained". Urban Airship. UrbanAirship.
• "7 Key Tips for your Push Notification Strategy". CleverTap Blog. CleverTap.
• "5 Ways Rich Push Notifications Can Maximize Conversions". ShepHertz Blog. ShepHertz.
• "Understanding Web Push Notifications". iZooto Guide. iZooto.