Adding Notifications to Your Mobile App With the Universal Notification Service
2 likes2,808 views
Notifications bring your users real-time alerts of business events. Join us to learn why notifications are driving engagement far beyond mobile, and how the new Salesforce Universal Notification Service can help you along the way. You'll engage in a step-by-step walkthrough of adding push notifications to your mobile app utilizing the service.
Ad
More Related Content
What's hot (20)
Viewers also liked (16)
![[UMAP 2016] User-Oriented Context Suggestion](https://cdn.slidesharecdn.com/ss_thumbnails/slideumap2016-160715024646-thumbnail.jpg?width=560&fit=bounds)
Ad
Similar to Adding Notifications to Your Mobile App With the Universal Notification Service (20)
Ad
More from Salesforce Developers (20)
Recently uploaded (20)
Adding Notifications to Your Mobile App With the Universal Notification Service
- 1. Adding Notifications to your Mobile App with the Universal Notification Service Steve Krenzel, Salesforce, Lead Developer Notifications Kevin Hawkins, Salesforce, Lead Developer Mobile SDK
- 2. Safe harbor Safe harbor statement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site. Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.
- 3. Steve Krenzel Lead Developer, Notifications
- 4. Kevin Hawkins Lead Developer, Mobile SDK
- 5. % of time spent on mobile devices is in apps 80%
- 6. Average person checks their smartphone 150x per day (~6.5 minutes)
- 7. Average apps installed on a US Smartphone 41 apps
- 8. The Problem: Content Overload ▪ More and more content is feed based ▪ Feeds are temporal in nature ▪ Easy to miss key updates or information ▪ Everyone hates email but it guarantees delivery
- 9. The Solution: Universal Notification Service • Cross Platform Delivery Management Native Push Mobile Web Cross App • Consistent Experience • Extensible • Custom notification types • Customizable • Preferences • Relevance is key Rule Engine Queueing Preferences Actions Templates Custom Notifications API • • • • Centralized Notifications
- 10. Roadmap: Universal Notification Service • Winter ‘14 (TODAY) • • Salesforce1 notifications iOS and Android native push notification support for custom mobile apps using our SDK • Spring ‘14 • • • Notification Preferences Additional Salesforce notifications Additional delivery channels • Summer ‘14 • • Salesforce Web UI Notification center in custom apps • Winter ’15 • • Custom notification types Actionable notifications
- 11. Touch Revolution Mobile apps using native push have 4x the engagement rate vs non-push apps * comScore Mobile Metrix (March 2012)
- 12. Adding Push Notifications to your Mobile App 1. Register to send push notifications with Apple or Google 2. Enable your connected app for push notifications 3. Configure native push notifications on your mobile app 4. Add logic to generate a native push notification for your custom mobile app
- 13. Register for Push Notifications with Apple or Google
- 14. Enable Connected App for Push Notifications
- 15. Configure Mobile SDK Android for Push Notifications // Set Google project number <string name="androidPushNotificationClientId">35123627573</string> Configure Mobile SDK iOS for Push Notifications // NOTHING TO DO – SALESFORCE DOES IT FOR YOU…SWEET!
- 16. Generate Push Notifications // Instantiating a notification *MobilePNS.MobilePushNotification msg = new *MobilePNS.MobilePushNotification(); // Assembling the necessary payload parameters for Apple. //(<alert text>,<alert sound>,<badge count>,<free-form data>) Map<String, Object> payload = *MobilePNS.MobilePushPayload.apple( 'Case ' + cs.CaseNumber + ' status changed to: ' + cs.Status, '', badge, null); // Add the assembled payload to the notification msg.setPayload(payload); // Getting recipient users String userId1 = cs.OwnerId; String userId2 = cs.LastModifiedById; // Adding recipient users to list Set<String> users = new Set<String>(); users.add(userId1); users.add(userId2); // Sending the notification to the specified app and users. msg.send('customerSupport_App', users); } } *(Developer Preview), APEX API name change in Spring ‘14