Your SlideShare is downloading. ×
0
Notifications APIJukka AlakontiolaSea Beyond 20111   © 20011 Nokia   Sea Beyond 2011.pptx/ 2011-‐02-‐03/ JAL
Increasing Demand for Push NotificationsPush Notifications among top most requested native features    50% of top N8 recom...
Why implement a shared push notification service?             Polling                                           Push per A...
Introducing Notifications APIEnabling Nokia and 3rd party developers access to optimized push notification4   © 2011 Nokia...
NotificationsToday: enabled within the Qt SDK with simple, intuitive tools                                          3rd Pa...
Design ConsiderationsUnlimited opportunity for app design, development, deployment, use                                   ...
Up-‐to-‐the-‐moment push deliveryAccess optimized and automated connectivity     Efficient         Lightweight notificatio...
Notifications APIGetting Started Registration and Notification ID             4. The Client App sends                     ...
Getting StartedDesign. Develop. Deploy.    1. Access SDK      2.Access API                 3. Service ID     4.Testing    ...
Notifications API: A Simple SolutionAdvanced functionality made easy, for the developer and the user                      ...
Upcoming SlideShare
Loading in...5
×

SeaBeyond 2011 ProcessOne - Nokia: Jukka Alakontiola - Notifications API

1,039

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,039
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
15
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "SeaBeyond 2011 ProcessOne - Nokia: Jukka Alakontiola - Notifications API"

  1. 1. Notifications APIJukka AlakontiolaSea Beyond 20111 © 20011 Nokia Sea Beyond 2011.pptx/ 2011-‐02-‐03/ JAL
  2. 2. Increasing Demand for Push NotificationsPush Notifications among top most requested native features 50% of top N8 recommended downloads use a type of notification 74% of Developers Prioritize Push Source: Appcelorator & IDC Developer Report: Oct 20102 © 2011 Nokia Sea Beyond 2011.pptx / 2011-‐02-‐03 / JAL
  3. 3. Why implement a shared push notification service? Polling Push per App Shared Push Anything for me? Anything for me? Ovi No No Drains battery 50% reduction in power Significant hidden data use => data charges consumption Impacts Operator network bandwidth & signaling load 2X battery life Source: VTT study3 © 2011 Nokia Sea Beyond 2011.pptx / 2011-‐02-‐03 / JAL
  4. 4. Introducing Notifications APIEnabling Nokia and 3rd party developers access to optimized push notification4 © 2011 Nokia Sea Beyond 2011.pptx / 2011-‐02-‐03 / JAL
  5. 5. NotificationsToday: enabled within the Qt SDK with simple, intuitive tools 3rd Party & Nokia Qt / QML Apps Qt SDK Client API (Qt) Ovi Notifications API Ovi Notifications Service Service (REST) API 3rd Party App Server (s)5 © 2011 Nokia Sea Beyond 2011.pptx / 2011-‐02-‐03 / JAL
  6. 6. Design ConsiderationsUnlimited opportunity for app design, development, deployment, use Up-‐to-‐the-‐moment Easy to developLimitless design possibilities push delivery and deploy Design how and when Notifications pushed the Included in the Nokia Qt to deliver notifications SDKs Optional prebuilt UI Optimized to assure Implement API in hours, screens and popup lightweight bandwidth not days Multiple app states use Design once and run on supported: foreground, Custom payloads up any supported Nokia in the background, or not to 1.5 kB device across any running network Any format, including text, xml, images, and binary6 © 2011 Nokia Sea Beyond 2011.pptx / 2011-‐02-‐03 / JAL
  7. 7. Up-‐to-‐the-‐moment push deliveryAccess optimized and automated connectivity Efficient Lightweight notifications Zlib compression algorithm for Chat 1 New notification reduced data consumption Heuristic ping tuned to individual network requirements Real-‐time Chat Notifications pushed to device in Ovi as soon as they are received 1 new notification Application wake-‐up ensures notifications reach target app regardless of state. Secure SSL/TLS for client-‐ and server-‐side connections7 © 2011 Nokia Sea Beyond 2011.pptx / 2011-‐02-‐03 / JAL
  8. 8. Notifications APIGetting Started Registration and Notification ID 4. The Client App sends Server Notification ID to App API server News Network Client API Ovi 1. App calls Client 2. Client API registers with API to register for the notifications the Notifications Server service 3. The Notifications Server sends the Notification ID via the Client API8 © 2011 Nokia Sea Beyond 2011.pptx / 2011-‐02-‐03 / JAL
  9. 9. Getting StartedDesign. Develop. Deploy. 1. Access SDK 2.Access API 3. Service ID 4.Testing 5.Publish Access the Qt Access API Register for Test new Apply to SDK via the details incl. Service ID and service in release Forum Nokia DevKit on Service Secret Service production web. From Forum on the Sandbox or version of App Nokia Developer with Simulator. with Notifications Console Access Sandbox notifications project site and Simulator via Developer via Developer Console Console. Publish App to Ovi Store https://projects.forum.nokia.com/notificationsapi9 © 2011 Nokia Sea Beyond 2011.pptx / 2011-‐02-‐03 / JAL
  10. 10. Notifications API: A Simple SolutionAdvanced functionality made easy, for the developer and the user + = Up-‐to-‐the Optimized Service/ moment Connection Client API content and context Nokia: Developer: User: A hosted notification Accessed with Nokia service and optional UI Notifications client to them popup and screens and server APIs included with the Nokia SDK10 © 2011 Nokia Sea Beyond 2011.pptx / 2011-‐02-‐03 / JAL
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×