This document provides an overview of push notification technology. It discusses the need for push notifications to engage users even when apps are not open. Key elements discussed include triggers, content type, user behavior, and intelligence. Use cases for push notifications include engagement, content delivery, financial/scheduling apps, and generating revenue. The document also outlines how push notification systems work at a high level, benefits like user control and efficiency, delivery methods, communication protocols, and some limitations.
5. 5
Challenges in Mobility
• Increase the usabilty of installed App ?
• Increase revenue through mobile ads?
• To communicate with users even when
the app is off.
• Develop next generation SMART apps :
• More Context Aware
• Near Field Communication
7. 7
Introduction
What is Push Notification ?
• Push Notification allows an app to notify the user of new messages or
events without the need to actually open the application
• Request for a given transaction is initated by the publisher or central
server
• Constantly open IP connection to forward notification from the servers of
third party applications to the mobile devices.
• Contrast to the PULL : where the request for the transmission of
information is iniated by the receiver or client.
• Gets the message to the customer in the most direct and targeted way
possible.
8. Trigger
Behavior-Based
Pre-defined
Rule-driven
Content Type
Universal vs Personalized
Open vs Protected
Lean vs Detailed
Time sensitive vs Anytime
User Behavior
Read Only
Read/Write
Act-outside-the-App
Intellegence
BI-Analytics
Conext Aware Data
Feedbacks
8
Key Elements of Push Notification
12. 12
How does it Work?
High-level Architectural Overview
Device
Application
Server
DB
Notification Server
Apple / Google/ Microsoft/
PushWoosh
13. 13
How does it Work?
High-level Architectural Overview
Device
Application
Server
DB
Notification Server
Apple / Google/ Microsoft/
PushWoosh
Token
Store
Token
Notification Message + Token
1
2
3
4
14. 14
Benefits Of Push Notifications
• User needs to subscribe to receive
notification
User Control
• User receives the notification even
when the app is not activeEase of Use
• No need for constant queries to
Server
• Saves battery Usage
Efficiency
15. 15
Delivery of Notifications
Only Unicast:
No Batch, multicast or broadcast
Quality of Service
Queue Size: One message waiting per app per device
No guarentee delivery
No delivery Notification to the server
Delivery experies (for iOS)
Quota
iOS: Unspecified
Android: 200K (can ask for more)
16. 16
Communication Protocol
Comparison between Apple and Android
Connection Streaming TCP/IP Socket HTTP Post
Security SSL SSL
Content Binary JSON
Trust Certificiation provided by
Apple
Gmail account
authentification
“Device not found“ errors Servers must query
Asynchronous feedback
service and remove
obsolete device tokens
Response to POST request
contains indications
whether device is obsolete
or not
17. 17
Limitations
Short Coming in PUSH Notification Technology
Short message Size
No guarentee that delivery is secured
Delivery
No guarentee
Users can sign out of the App
Users can disable push to save battery
18. Mobile Client
PUSH notification Server
Apple / Google/ Microsoft/
PushWoosh
LocationManager
Services
STORM based
Notification Manager
1
4
5
Most Current Location
Context Provider
Noto
Context Manager
Server-Side
2
Notificatoin
DBBackend
DB
3
Context Information
Notification Polling
Weather
3rd Party
Context Provider
Stock
NEWS
Widas PUSH Notification Framework