Introduction to Mobile Push Notification
Push Notification,
describes a style of internet-based communication where the App requests for a
given transaction is initiated by the publisher or central server. It is contrasted with pull, where the request for the transmission of
information is initiated by the receiver or client (Ex: Mobile App, Desktop App).
Mobile Push Notification:
Push notifications on mobile and other platforms
allow your cloud-based applications to send brief alerts and updates to a
client application. Push notifications are a great way to keep the dialogue
going between a consumer and marketer. However, mobile experts agree that
similar to all other marketing channels, the key is consistency and including
the medium into a multichannel strategy. “Push notifications as a stand-alone
mobile messaging channel has a place in the marketer’s toolbox,”
Apple Push Notification
The Apple
Push Notification Service is a service
created by Apple Inc. that was launched together with iOS 3.0 on June 2009. It uses push technology through a constantly open IP connection to
forward notifications from the servers of third party applications to the
Apple devices; such notifications may include badges, sounds or custom text
alerts. In iOS 5, Notification Centre enhanced the user experience of push
and local notifications. APNS was also added as an API to Mac OS X v10.7 "Lion" for developers to take advantage of and was greatly improved in OS X 10.8 "Mountain Lion" with the introduction of Notification Centre.
With Mac OS X Lion, an app can take advantage of
the same API used in iOS to push badge numbers to applications running on Mac
OS X. With the release of OS X Mountain Lion, users can
receive push notifications through Notification Centre. If the
application is not open when the notification is received, the app will be
badged and added to the dock (until the badge is cleared) to notify users.Each
notification is restricted to a maximum size of 256 bytes.
Source - http://www.raywenderlich.com/3443/apple-push-notification-services-tutorial-part-12/push-overview
ü
Client app is
enabled to receive Push Notification.
ü
App request
for token from the APN server.
ü
APN server
sends a token to the Client app.
ü
Server takes
the token from the client side app and sends a notification to the APNS server.
ü
APN server
sends a notification to the respective devices based on the token value.
Android Push Notification
Google Cloud Messaging (GCM) replaces
the beta version of Android Cloud to Device Messaging (C2DM).
Android Cloud to Device Messaging (C2DM), which
is now deprecated, is a push notification service that helps
developers sends data from servers to their applications on Android devices
which launched together with Android 2.2 by Google. The
service provides a simple, lightweight mechanism that servers can use to tell
mobile applications to contact the server directly, to fetch updated
application or user data. The C2DM service handles all aspects of queuing of
messages and delivery to the target application running on the target device.
Applications on an Android device don’t need to
be running to receive messages. The system will wake up the application via
Intent broadcast when the message arrives, as long as the application is set up
with the proper broadcast receiver and permissions. C2DM does not provide any
built-in user interface or other handling for message data. Instead, it simply
passes raw message data received straight to the application, which has full control
of how to handle it. For example, the application might post a notification,
display a custom user interface, or silently sync data. It requires devices
running Android 2.2 or higher that also have the Market application installed.
It uses an existing connection for Google services. This requires users to set
up their Google account on their mobile devices. Each notification message size
is limit to 1024 bytes, and Google limits the number of messages a sender sends
in aggregate, and the number of messages a sender sends to a specific device.
Source -
http://www.freeware-files.com/index.php/component/jdownloads/view.download/297.html#.UNL5wOSTwpU
Windows Phone Push notifications
The Microsoft Push Notification Service in
Windows Phone offers third-party developers a resilient, dedicated, and
persistent channel to send data to a Windows Phone app from a cloud
service in a power-efficient way.
The following diagram shows how a push
notification is sent.
ü
Your app requests a push notification URI from the
Push client service.
ü
The Push client service negotiates with the Microsoft
Push Notification Service (MPNS), and MPNS returns a notification URI to the
Push client service.
ü
The Push client service returns the notification URI
to your app.
ü
Your app can then send the notification URI to your
cloud service.
ü
When your cloud service has info to send to your app,
it uses the notification URI to send a push notification to MPNS.
ü
MPNS routes the push notification to your app.
Depending on the format of the push notification
and the payload attached to it, the info is delivered as raw data to the app,
the app's Tile is visually updated, or a toast notification is displayed. MPNS
sends a response code to your cloud service after a push notification is sent
indicating that the notification has been received and will be delivered to the
device at the next possible opportunity. However, MPNS doesn’t provide an
end-to-end confirmation that your push notification was delivered from your
cloud service to the phone.
Blackberry Push Notification
The BlackBerry Push Service enables developers to
easily develop Java applications or BlackBerry Widgets that leverage
RIM’s push technology either through the BlackBerry Enterprise Server (for
enterprises) or BlackBerry Internet Service infrastructure (for consumers), so
that content providers can reliably push images, text, or audio content to
millions of BlackBerry devices at once. Unlike alternative push solutions that
can only notify users that new content is available for download because of
push message size limitations, with the BlackBerry Push Service, full content
(up to an industry-leading 8KB in size) is pushed to the device and made
immediately available for use.
ü
Content provider sends a push request.
ü
Blackberry infrastructure returns a response.
ü
Blackberry infrastructure pushes the data to the
Blackberry smart phones.
ü
Blackberry smart phones return a response to the
blackberry infrastructure.
ü
Blackberry Infrastructure forwards acknowledgement to
content provider.
ü
Read notification is returned to the Blackberry
Infrastructure.
Conclusion:
Important thing is push notifications can
increase engagement of Customer and Vendor; message relevance is very important
to long-term app usage and maintaining a solid mobile relationship with
customers. If this functionality not utilized correctly, customers may opt-out
of receiving notifications or even delete the app. And when we use the push
notification effectively it’s a wonderful way to have a good relationship with
the customers.
If you don't design your own life plan, chances are you'll fall into someone else's plan. And guess what they have planned for you? Not much.- Jim Rohn
Push
Service Provider
|
Users
|
Monthly
$
|
Annual
$
|
|
Push
Woosh
|
Unlimitted
Users
|
26
|
254
|
|
AirWatch
|
Per
Device
|
3.25
|
50
one time
|
|
UrbanAir
Ship
|
0
to 10000 Users
|
199
|
2388
|
Features
|
Push
Woosh
|
AirWatch
|
UrbanAir
Ship
|
|
Mobile Security
|
Yes
|
Yes
|
Yes
|
|
Mobile Device Management
|
N/A
|
Yes
|
N/A
|
|
Mobile Application Management
|
N/A
|
Yes
|
N/A
|
|
Mobile Content Management
|
N/A
|
Yes
|
N/A
|
|
Mobile Email Management
|
N/A
|
Yes
|
N/A
|
|
Bring Your Own Device (BYOD)
|
N/A
|
Yes
|
N/A
|
|
Push Notification
|
Yes
|
Yes
|
Yes
|
|
Rich Push Notification
|
Yes
|
Yes
|
If you don't design your own life plan, chances are you'll fall into someone else's plan. And guess what they have planned for you? Not much.- Jim Rohn
No comments:
Post a Comment