Nokia Publisher Guide - Nokia Publish Support

More documents

Recommendations

Info

Prepare MeeGo 1.2 Harmattan apps The MeeGo 1.2 Harmattan platform uses Debian packages to install apps. However, Harmattan enables you to use some additional metadata fields in the control file of the app. For the: � Debian packaging policy � see http://www.debian.org/doc/debian-policy/ � Harmattan Appendix to the Debian policy � see http://www.developer.nokia.com/Community/Wiki/Harmattan:Developer_Library/Reference_documentati on/Harmattan_Appendix_to_the_Debian_Policy_Manual � Harmattan Developer Documentation � see http://harmattan-dev.nokia.com/docs/library/ This section applies to apps developed through the Qt SDK. 1. The following files in the Debian package are the most relevant: � Copyright — Contains the information about copyright and license information. � Rules — Contains the exact rules for different targets specifying how to create the packages. � Control file — Includes the packaging metadata for your app. � Changelog — Includes the package name, version, distribution, urgency, and changes made in the package revision. � Aegis manifest file — If your app needs to access protected Harmattan resources, the credentials are defined in the Aegis manifest file. The Aegis manifest file is created automatically by the Qt SDK as a part of the build if it is needed. This usually covers your basic security needs. If the Aegis manifest file is not needed, the Qt SDK does not create it. You may need to edit the Aegis manifest file manually, if: � Your app provides protected services to other apps � You have problems with the automatically generated file 2. Modify the following files: � Desktop file � Add the display name and icon displayed for your app in the launcher. � Copyright file � Add the information about copyright and license information for your app. � Control file — Add the mandatory and optional packaging metadata for your app. 3. If you are using Qt, use an official release of the Qt SDK, not a Beta release, to package the app. 4. Test the app to meet the Nokia Store Content Guidelines: http://support.publish.ovi.com/?p=64. Do not sign MeeGo 1.2 Harmattan apps. Nokia Publish automatically signs all these apps for Nokia Store. Prepare Maemo apps This section applies to apps written in a native Maemo language as well as those developed through the Qt SDK. 1. Ensure the following: � Package category � Has the category user/hidden. � App file � Is installed in the opt folder on the ext3 partition. 2. If you are using Qt: � Use an official release of the Qt SDK, not a Beta release, to package the app. � Target Maemo 5 devices, for example, Nokia N900 with PR1.3. 3. Test the app to meet the Nokia Store Content Guidelines: http://support.publish.ovi.com/?p=64. Do not sign Maemo apps. The .deb packages on Maemo devices currently do not support any signing. Page 26 (of 62) Publisher Guide
Prepare Flash Lite apps � Do not (prompt consumers to) install Adobe Flash or Flash Lite Player. � Do not use the Adobe Mobile Packager Tool to package .sis(x) files. For a Flash packaging service, go to: http://www.developer.nokia.com/Develop/Other_Technologies/Flash_lite/. � Do not submit a standalone .swf Flash file, or submit an .swf Flash file packaged as a .sis(x), .wgz, or .nfl file, intending it to be used as an animated wallpaper or screen saver. � Use a version of Flash Lite that is compatible with the version on the target device. Prepare games Ensure that games distributed to touch screen devices: � Are touch enabled. � Disable by default the on-screen keypad, which is used to scroll the display. For sample code, go to: http://www.developer.nokia.com/Community/Wiki/Using_on-screen_keypad_in_MIDlets_in_S60_5th_Edition_devices. � Utilise the full screen and can be fully playable without the on-screen keypad. Publisher Guide Page 27 (of 62)
Page 1 and 2: P U B L I S H E R G U I D E Septemb
Page 3 and 4: I N T R O D U C T I O N Publisher G
Page 5 and 6: How do I publish to Nokia Store? Be
Page 7 and 8: W H A T ’ S N E W Nokia Publish,
Page 9 and 10: R E G I S T E R AS A P U B L I S H
Page 11 and 12: Step 2/6 — Publisher information
Page 13 and 14: Step 5/6 — Payment There is a 1
Page 15 and 16: Log in 1. Go to https://publish.ovi
Page 17 and 18: Manage account users When you regis
Page 19 and 20: P R E P A R E C O N T E N T Publish
Page 21 and 22: How content appears in Nokia Store
Page 23 and 24: Prepare files You can submit files
Page 25: Prepare Java apps 1. If you want No
Page 29 and 30: A D D N E W C O N T E N T About con
Page 31 and 32: Edit metadata You can add optional
Page 33 and 34: Spotlight content Spotlights can si
Page 35 and 36: Define the distribution After you u
Page 37 and 38: Enhance global appeal If your conte
Page 39 and 40: Check the QA status After you have
Page 41 and 42: U P D A T E C O N T E N T Publisher
Page 43 and 44: Update a content file If you are up
Page 45 and 46: R E V I E W P E R F O R M A N C E R
Page 47 and 48: View a detailed report for a conten
Page 49 and 50: A P P E N D I C E S Publisher infor
Page 51 and 52: Bank information You provide this p
Page 53 and 54: Categories You categorise content i
Page 55 and 56: Name Description Mandatory / Option
Page 57 and 58: Content file You provide content fi
Page 59 and 60: MeeGo 1.2 Harmattan & Maemo apps Na
Page 61 and 62: Glossary app A software application

Nokia Publisher Guide - Nokia Publish Support

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?