1 © 20011 Nokia Sea Beyond 2011.pptx/ 2011-‐02-‐03/ JAL

Jukka Alakontiola

Sea Beyond 2011

Notifications API

Increasing Demand for Push NotificationsPush Notifications among top most requested native features

2 © 2011 Nokia Sea Beyond 2011.pptx / 2011-‐02-‐03 / JAL

50% of top N8 recommended downloads use a type of notification

Source: Appcelorator & IDC Developer Report: Oct 2010

74% of Developers Prioritize Push

Why implement a shared push notification service?

Drains batterySignificant hidden data use => data chargesImpacts Operator network bandwidth & signaling load

Polling Push per App Shared Push

Anyth

ing fo

r me?

No

50% reduction in power consumption2X battery life

Source: VTT study

Anyth

ing fo

r me?

No

Ovi

3 © 2011 Nokia Sea Beyond 2011.pptx / 2011-‐02-‐03 / JAL

Introducing Notifications API Enabling Nokia and 3rd party developers access to optimized push notification

4 © 2011 Nokia Sea Beyond 2011.pptx / 2011-‐02-‐03 / JAL

3rd Party & Nokia Qt / QML Apps

Qt SDK

Service (REST) API

Ovi Notifications Service

3rd Party App Server (s)

Client API (Qt)

Ovi

Not

ifica

tion

s AP

I

Notifications Today: enabled within the Qt SDK with simple, intuitive tools

5 © 2011 Nokia Sea Beyond 2011.pptx / 2011-‐02-‐03 / JAL

Easy to developand deploy

Up-‐to-‐the-‐moment push deliveryLimitless design possibilities

Design ConsiderationsUnlimited opportunity for app design, development, deployment, use

Design how and when to deliver notifications

Optional prebuilt UI screens and popup

Multiple app states supported: foreground, in the background, or not running

Any format, including text, xml, images, and binary

Notifications pushed the

Optimized to assure lightweight bandwidth use

Custom payloads up to 1.5 kB

Included in the Nokia Qt SDKs

Implement API in hours, not days

Design once and run on any supported Nokiadevice across any network

6 © 2011 Nokia Sea Beyond 2011.pptx / 2011-‐02-‐03 / JAL

Up-‐to-‐the-‐moment push deliveryAccess optimized and automated connectivity

Efficient

Lightweight notifications

Zlib compression algorithm for reduced data consumption

Heuristic ping tuned to individual network requirements

Real-‐time

Notifications pushed to device in as soon as they are received

Application wake-‐up ensures notifications reach target app regardless of state.

Secure

SSL/TLS for client-‐ and server-‐side connections

Ovi1 new notification

Chat1 New notification

Chat

7 © 2011 Nokia Sea Beyond 2011.pptx / 2011-‐02-‐03 / JAL

News Network

Ovi

Clie

nt

AP

I

Server API

Client API registers with the Notifications Server

2.

The Client App sends Notification ID to App server

4.

The Notifications Server sends the Notification ID via the Client API

3.

App calls Client API to register for the notifications service

1.

Notifications APIGetting Started Registration and Notification ID

8 © 2011 Nokia Sea Beyond 2011.pptx / 2011-‐02-‐03 / JAL

Getting StartedDesign. Develop. Deploy.

1. Access SDK 2.Access API 3. Service ID 4.Testing 5.Publish

Access the Qt SDK via the Forum Nokia web.

Access API details incl. DevKit on From Forum Nokia Notifications project site

Register for Service ID and Service Secret on the Developer Console

Test new service in Service Sandbox or with Simulator. Access Sandbox and Simulator via Developer Console.

Apply to release production version of App with notifications via Developer ConsolePublish App to Ovi Store

https://projects.forum.nokia.com/notificationsapi

9 © 2011 Nokia Sea Beyond 2011.pptx / 2011-‐02-‐03 / JAL

+ =Optimized Connection

Developer: Accessed with Nokia Notifications client and server APIs included with the Nokia SDK

Service/ Client API

Nokia:A hosted notification service and optional UI popup and screens

Up-‐to-‐the moment

content and context

User:

to them

Notifications API: A Simple SolutionAdvanced functionality made easy, for the developer and the user

10 © 2011 Nokia Sea Beyond 2011.pptx / 2011-‐02-‐03 / JAL