SOCIAL SHARING USING NOKIA ASHA SDK 1.1 (BETA)

Pranav Gothadiya Product Owner Nokia Asha SDK pranav.gothadiya@nokia.com

CONTENTS • Introduction to Social Sharing • What is Share API? • Using Share API • Application development using Share API

- Share contents from MIDlet - Share contents from other apps - Fastlane integration

• Oauth 2.0 • Emoji Support • Additional Information

INTRODUCTION TO SOCIAL SHARING • Sharing content with social media • Built-in feature of Share API through content handler • Oauth 2.0 based authentication support • Use unicode base emoticons in content sharing

WHAT IS SHARE API ?

• Its a convenient overlay to JSR-211 for simple social sharing of content

• Platform implements this social sharing support • Content handled either by content type/content handler ID • Application development:

- Implementing source for sharing - Implementing destination for sharing

APPLICATION SIDE IMPLEMENTATION Code snippet: String[] args = new String[]{"text=" + this.sharedText.getString()};

String mime = "text/plain";

Registry registry = Registry.getRegistry(this.getClass().getName());

Invocation invocation = new Invocation(null, mime, "com.nokia.share"); invocation.setAction("share");

invocation.setArgs(args);

invocation.setResponseRequired(false);

registry.invoke(invocation);

SUPPORTED ARGUMENTS • url: url

- The url to the file that is being shared (many supported) n - This is used when the shared items are files

String[] args = new String[]{“url=file:///Phone/_my_picture/img1.png"};

SUPPORTED ARGUMENTS • url: url

- The url to the file that is being shared (many supported) n. This is used when the shared items are files

• text: text

- Textual content that is being shared - This is used when the shared items are texts

String[] args =

new String[]{"text=file:///Phone/_my_picture/img1.png"};

SUPPORTED ARGUMENTS • url: url

- The url to the file that is being shared (many supported) n. This is used when the shared items are files

• text: text

- Textual content that is being shared. This is used when the shared items are texts

For Fastlane integration • id

- A unique identifier of the share transaction. - It can be stored for future reference. - Used with “open-shared” action.

SUPPORTED SHARE TYPES

Following mime types can be registered: • image/* or specific image types • audio/* or specific audio types • video/* or specific video types • text/plain type

“No limit on size or types by the Share API, but there might be limitations on the individual share destinations”

SHARE CONTENTS FROM MIDLET

• Generate arguments to pass content • Specify mime type of the content • Get content handler Registry • Create invocation • Invoke

SHARE CONTENTS FROM OTHER APPLICATIONS

• Make JAD entry for content handler • Create ContentHandlerServer • Get Invocation from content handler server • Get the arguments (content) • Use content to share

CONTENT INVOCATION

Content can be invoked from following native apps: • Sharing link and bookmark from Browser • Sharing files from:

- Gallery - Music player - Video player - Camera

• Sharing contacts and calendars

FAST LANE INTEGRATION • Destination must register to action "open-shared“ • Destination can deep link the user into the right view • Fastlane item is added if the destination returns with Invocation.OK handler.finish(invocation, Invocation.OK);

• Fastlane item is added if the destination returns Invocation.CANCELLED and quit contentHandlerServer.finish(invocation, Invocation.CANCELLED);

• Share UI considers that sharing has ended, but does not create a Fastlane item because the sharing was not completed

contentHandlerServer.finish(invocation, Invocation. INITIATED);

OAUTH 2.0 SUPPORT • Allows to access server resources on behalf of the resource owner • Secure open authorization protocol • Authentication handled by Nokia browser • Invocation happens through Content Handler • Browser - Performs Oauth 2.0 based authentication - Get back the access token - MIDlet app to use that access token further

22 November 2013 / Slide no 15

OAUTH 2.0 IMPLEMENTATION

EMOJI SUPPORT • Japanese term which represents a picture • It expresses an visual/idea in messaging • Standard Unicode set: - Large number of emoji chars - Range: U+1F300 to 1F64F • Surrogate pair: - Maps an emoji character to a pictograph - Nokia Asha Platform has built-in implementation • Back to UTF16 char: - While reading the char from Java text component

EMOJI SUPPORT - IMPLEMENTATION • Constants

• Create surrogate par from Unicode character

• Get Unicode character back from surrogate pair

MORE INFORMATION Overview - http://developer.nokia.com/Develop/asha/java/start/ Downloads - http://developer.nokia.com/Develop/asha/java/tools.xhtml - http://projects.developer.nokia.com/LWUIT_for_Series_40 Guides - Nokia Asha Design Guide: http://developer.nokia.com/Resources/Library/Asha_UI/ - Porting Guide: http://developer.nokia.com/Resources/Library/Porting_to_Nokia_Asha/ - Documentation: http://developer.nokia.com/Develop/asha/java/resources/docs/ - Training Videos: http://developer.nokia.com/Develop/asha/learning.xhtml - Code Examples: http://developer.nokia.com/Develop/asha/java/resources/code/

THANK YOU. QUESTIONS? For more information: https://developer.nokia.com/Develop/asha/learning.xhtml