This blog post is coauthored by Bhargav Perepa, a WebSphere IT specialist/architect at IBM Federal Software Group in Washington, DC, and Stephen Ades, worldwide enterprise mobility management (EMM) principal solutions consultant for IBM.
Are you looking to engage your mobile consumers with personalized, simple notifications? Do you want to reach your savvy but forgetful mobile users with rich notifications delivered programmatically through a mobile application? Would your mobile developers be interested in delivering notifications to your consumers in their time zone or location? You can do all of this by developing mobile applications featuring the web application programming interface (API) integration of the IBM Mobile Push Notification platform. IBM MobileFirst and IBM ExperienceOne products offer fit-for-purpose solutions that can help you better engage your clients for mobile and social commerce.
The IBM Mobile Push Notification software development kit (SDK) enables mobile developers working on the Android, iOS or BlackBerry platforms to integrate push notifications into their mobile applications. It does so by using a web API technology integration approach, which is available in the IBM Mobile Push Notification console.
Using the IBM Mobile Push Notification console (a browser-based capability for provisioned and authorized administrative or marketing users), a marketer can push an ad hoc notification quickly, with zero programming effort, to a mobile application’s target audience. That notification can be directed to a single user, all users, a segment of users or a set of XID (Xtify ID) users. Marketer push notifications can be simple or rich text with colors, formats, content with images and so on, and they can be scheduled with complex rules.
Figure 1: IBM Mobile Push Notification: Console views
For example, using IBM Mobile Push Notification console, a marketer can set up a notification campaign that considers the following factors:
- An indicated date or range of dates (with notifications going out before or after)
- The location of an individual or a group
- The time at the user’s location or a specific time zone
- The frequency of messages sent to the user (indicated by number of messages per minute, hour, day, week or month, with a minimum time between messages and a maximum number of messages)
- The number of days since a mobile application was installed or opened
- Segmented user groups as defined by tags
A mobile developer using an SDK can have access to these and other capabilities offered by the IBM Mobile Push Notification console by using APIs programmatically.
The APIs offered by the IBM Mobile Push Notification platform are categorized as follows:
IBM Mobile Push Notification APIs
- Push API 2.0 enables developers to push ad hoc notification messages programmatically.
- Push Notification Scheduler API 2.0 enables developers to push notification messages based on campaign schedules created by the marketer using the non-programmer console; it also enables separation of concerns for roles. This capability requires using the IBM Mobile Push Notification console.
- Bulk Push API 2.0 allows developers to send a broadcast of a single message to hundreds of thousands of users in a short amount of time (all users or a selection of users based on a tag).
There are notable differences between Push API and Bulk Push API that are well documented, with guidance on when to use which API.
Registration and events APIs
- Inactive XIDs API allows developers to get a list of inactive XIDs for a specified date. XIDs become inactive when users remove the mobile application from their devices.
- Location API 2.0 allows developers to submit location updates from a platform or custom provider.
- Registration API 2.0 allows developers to register a device with the device details provided and receive a unique XID from the IBM Mobile Push Notification system for subsequent use.
- Rich Notification API 2.0 allows developers to present notifications pushed to users from within a mobile application using a customized view for user experience. Rich notifications are presented and stored in a rich notification inbox.
- Tag API 2.0 allows developers to associate a segment name (tag) with specific members of the notification recipient group.
Figure 2: IBM Mobile Push Notification: Device views
In summary, IBM Mobile Push Notification helps mobile developers to deeply engage their consumers with web API-integrated mobile applications. These applications can make use of the rich capabilities of the IBM Mobile Push Notification platform for enriched brand loyalty, resulting in potential consumer retention, improved business performance and profitability.
Do you have any ideas on how to engage consumers at a deeper and richer level, while at the same time investing in our developers and technical community?
For further information, please explore the following resources:
- Download Push Notification SDKs
- Develop IBM Push Notification integrated mobile applications
- Engage mobile application users/consumers by creating an API project with GCM