Nokia Ovi Publisher Guide for September 2010

Publisher Guide
September, 2010
1 (75)
Nokia Ovi Publisher Guide, as of September, 2010
CHANGE LOG Following are the recent changes introduced in this guide. Please review the changes as some of them may affect the QA testing requirements and may require modifications to your existing applications.
ISSUE Nokia signing Java Nokia signing - . Symbian applications for S60 1 and 2 Ovi Store and hence do not need to be signed. Supported new file extensions.
st nd
Pg. 31 Ed devices are not supported by 32
38
2 (75)
1.
Ovi overview .................................................................................................................................................................. 4 1.1 Benefits of publishing to Ovi ................................................................................................................................ 4 2. Publisher Registration .................................................................................................................................................. 6 2.1 To register as a publisher with Ovi Store ............................................................................................................ 6 2.2 Logging in ............................................................................................................................................................ 12 2.3 Changing your password ................................................................................................................................... 13 2.4 Password Recovery ............................................................................................................................................ 13 2.5 Providing your bank data details. ...................................................................................................................... 15 2.6 Applying for a Publisher Media account ........................................................................................................... 16 2.7 General rules ....................................................................................................................................................... 16 2.8 Content files......................................................................................................................................................... 17 2.9 Images and Icons ................................................................................................................................................ 22 3. Signing Symbian and Java apps................................................................................................................................ 32 3.1 Current process for signing apps ...................................................................................................................... 32 3.2 File types supported ........................................................................................................................................... 32 3.3 Steps to get your apps signed by Nokia ........................................................................................................... 32 3.4 Certified signing Symbian apps ......................................................................................................................... 33 4. Adding a new content item ......................................................................................................................................... 33 4.1 Choosing a content type ..................................................................................................................................... 33 4.2 Answer the legal questions relating to content compliance. .......................................................................... 34 4.3 Create the content item....................................................................................................................................... 35 4.4 Adding additional optional metadata................................................................................................................. 37 4.5 Choosing a global price point ............................................................................................................................ 39 4.6 Selecting a preferred billing method ................................................................................................................. 40 4.7 Adding a file ......................................................................................................................................................... 40 4.8 Choosing distribution for your content item .................................................................................................... 42 4.8.1 Choosing device compatibility for distribution........................................................................................ 42 4.8.2 Choosing country compatibility for distribution...................................................................................... 44 4.8.3 Choosing language compatibility for distribution ................................................................................... 44 4.9 Submitting content to a quality assurance check ............................................................................................ 45 5. Tips: distributing global content locally.................................................................................................................... 46 5.1 Increasing discoverability of content in Ovi Store ........................................................................................... 46 5.2 Increasing downloads of localized content ...................................................................................................... 47 6. Security ........................................................................................................................................................................ 47 7. Quality assurance (QA) process ................................................................................................................................ 48 7.1 Purpose of Testing .............................................................................................................................................. 48 7.2 Testing criteria..................................................................................................................................................... 48 7.3 Submission process ........................................................................................................................................... 51 7.4 Checking a content items QA status ................................................................................................................ 52 7.5 Checking an individual files QA status ............................................................................................................ 52 8. Editing content ............................................................................................................................................................ 53 8.1 Editing the content item..................................................................................................................................... 54 8.2 Editing a file ......................................................................................................................................................... 55 9. Unpublishing content already published in Ovi Store. ............................................................................................ 56 10. Promoting content on Ovi Store Spotlight Promotion .......................................................................................... 58 11. User accounts and roles ............................................................................................................................................. 60 11.1 Roles..................................................................................................................................................................... 61 11.2 Add users ............................................................................................................................................................. 61 11.3 Company information ......................................................................................................................................... 61 12. Financial Related Issues ............................................................................................................................................. 61 13. Metadata details .......................................................................................................................................................... 61 14. Glossary ....................................................................................................................................................................... 75
3 (75)
1.
OVI OVERVIEW
Ovi Store is Nokia's global application and content market reaching millions of Nokia users worldwide on Nokia devices as well as through the Nokia device browser. Submitting content and applications to Ovi is done through a self-service tool that provides publishers with an easy way to distribute and monetize their content. Ovi is Nokias global brand for Internet services which currently includes Maps, Messaging (email and instant messenger), Media (Ovi Store, Ovi Share and N-Gage), and Music. With the Ovi services catalogue continually growing, Ovi will remain an increasingly powerful way for you to access and create content and services from a mobile device, desktop computer or via the Web.
A consumer can experience the Ovi Store by easy access through browsing a variety of content. After choosing a content item, the consumer simply clicks the download action button next to the item to initiate the download. 1.1 Benefits of publishing to Ovi Easy access to a single channel reaching millions of consumers around the world Monetize your applications and content with Nokia-provided billing Rewarding revenue share (see Terms & Conditions for details) Fast time to market via self-serve publishing Sales and usage reports, updated daily Liberal content validations and quality assurance procedures make it easy for Publishers to get their content to market.
Publishing applications and content to the Ovi Store is done through a self-service tool, Ovi Publish, used by publishers to register and upload content to the Ovi Store. Publishing your content makes it available for download and consumption on Nokia devices worldwide.
4 (75)
To make your content available in the Ovi Store you can use our content intake portal at http://publish.ovi.com. Once youre registered as an Ovi publisher you can publish content to the Ovi Store.
5 (75)
2. 2.1
PUBLISHER REGISTRATION To register as a publisher with Ovi Store Go to publish.ovi.com Click Register Now
Step 1/6
Enter your country The account type you wish to create - corporate or personal. Corporate accounts are designated for legal business entities. These accounts may apply for a Media Publisher that permits distribution of audio, video and personalization content
Personal Accounts are designated primarily for individuals that wish to distribute content. These accounts cannot apply to be a Media Publisher
6 (75)
Step 2/6
Enter information in: Publisher details Public profile Primary contact for business enquiries Other Click Next when you have entered all the relevant information.
NOTE: Fields marked with an asterisk (*) are mandatory.The guide illustrates the corporate registration page. Personal account registration may differ in the mandatory fields collected.
7 (75)
Step 3/6
Enter the information details for the Administrator of your companys Ovi Publish account. Click Next.
8 (75)
Step 4/6
Read the Terms and Conditions. Click the Agree to Terms and Conditions check box. Click the Accept Terms and Conditions button.
Step 5/6
9 (75)
Read the payment terms. Click on the I approve these Payment Terms check box. Click on proceed to payment Select your banks country Select a credit card
10 (75)
Click on the submit button Complete your Credit Card information and click Submit
NOTE: The 1 charge is a non-refundable processing fee. Fields marked with an asterisk (*) are mandatory.
Step 6/6
This page tells you to go to your primary contact email. Open your email Click on the link provided.
The login page opens with a message confirming that registration is complete and you are now ready to log in.
11 (75)
2.2
Logging in
Log in to Ovi Publish with your verified username and password.
The Ovi Publisher Home page opens, giving you general information on the following: Your latest content updates A brief overview of how to publish content A list of important terms used when publishing content Links to information related to your account
12 (75)
2.3
Changing your password
When you receive your password for the first time you may want to change it to something that is easier to remember. To change your password:
Log in to Ovi Publish. Click Edit profile at the top-right of the screen.
Click Change password.
Enter a new password.
Click Update.
2.4
Password Recovery
If upon logging in, you forget your password:
Click the Forgot username/password link.
13 (75)
Enter your email address.
Click Send. You will receive an email with your new password.
14 (75)
2.5
Providing your bank data details.
Publishers that submit chargeable content to Ovi Store must provide their bank data details in order to receive payment attributed to purchases of their content. Publishers that submit free content to Ovi Store do not need to provide this information. To provide your bank data details go to Payee Information page under the Account tab. Please contact your bank if you need help gathering this information. NOTE: Note: In case you use an intermediary bank for depositing funds into your account from abroad, please provide the intermediary details to Publishtoovi.support@nokia.com. Please include the following information: Bank country, Bank city, Bank name and SWIFT code for both banks (intermediary and beneficiary.
15 (75)
2.6
Applying for a Publisher Media account
Media Account publishers are allowed to publish the personalization content on Ovi Store which includes: Audio, ringtones, video and wallpapers. There are two account types: Media Genre Account is intended for 1st party publishers who own their content and all its inherent rights for distribution, or who have acquired exclusive license to distribute content. This category describes a publisher with specific genre, segment or niche content. Media Genre Accounts have a limit of 20 content items (paid and/or free) which may be discoverable in Ovi Store at any given time.
Media Geo Account is intended for 3rd Party publishers who have geographic rights to distribute content, which may or may not be exclusive, and is more generic by nature, such as popular ringtones. Content in this type of account is limited by geographic region. The Ovi Store content team will select a limited number of Media Geo accounts in each geographic region to ensure content quality and discoverability is maintained.
The goal of creating these accounts is to enable Ovi Store to provide optimum placement of your content in Ovi Store, while ensuring maximum relevance for consumers. Contact publishtoovi.business@nokia.com to request an application to be considered for a Publisher Media account.
Before you begin There are certain files and creative materials that you must have ready and available when adding a new content item for publishing. Submitted content files are checked in the QA process and must follow specific requirements. This chapter provides information on those requirements: General guidelines on how to publish content to Ovi Examples of how content is presented in downloadable pages across the various Ovi Store touch points Information about the files used to create content including content file types, images and icons
2.7
General rules
The creation of images for content download pages should follow these general rules of thumb: Avoid using too much information over the images. Make sure any text on the image is readable. If not, do not use text. Do not use borders in the thumbnails. Violent, sexually explicit, or offensive images are not permissible. All content must comply with Nokia content guidelines which are available for viewing at https://publish.ovi.com/help/content_guidelines Use thumbnail images that depict your game or application experience. DO NOT use generic brand logos, rather create application icons that will give an idea of what your application experience is about, and will compel the user to download and/or buy.
16 (75)
Consider the size limitations of the mobile screen when designing your promotional assets. The minimal image upload size is 256x256 pixels. Keep graphic layouts simple and be sure to test your images on a handset before publishing. Devices for testing the applications or images are available over the Internet on Forum Nokia at the following URL: http://www.forum.nokia.com/rda.
Consider using colorful and descriptive icons to give your content a fresh and lively appearance.
2.8
Content files
In order to publish content to Ovi Store, the following items must be prepared in advance of the submission process. These items include: Packaged application. If youre submitting a Java application it will need to be packaged as a JAR and JAD pair and signed appropriately. Refer to section 3.0 for more details about Nokia signing Java apps at no cost for Ovi Publishers. If youre submitting a Symbian application it will need to be packaged as a .SIS file and be Symbian Signed (Express or certified). If the Symbian application is developed using Nokia Qt SDK, then the .SIS file called Nokia Smart Installer must also be included. See http://wiki.forum.nokia.com/index.php/Nokia_Smart_Installer_for_Symbian. Refer to section 3.0 for more details about Nokia signing Symbian apps at no cost for Ovi Publishers. If youre submitting a Maemo application it will need to be packaged as a .deb file If youre submitting a Flash Lite application it will need to be packaged as a .SIS file and be Symbian Signed (Express or Certified) if it is for S60 devices. Refer to section 3.0 for more details about Nokia signing Symbian apps at no cost for Ovi Publishers. For Series 40 devices it must be published as a .NFL file. Images (used to visually represent your application experience to a consumer): make sure you have all the necessary image sizes listed in section 2.9. Icons used to identify your application on a consumers handset. Name and description of the content item. A list of keywords to be used as metadata for your application enabling indexing and discovery via the Ovi Store search functionality. Identify in advance the devices you wish to target with your content items. http://www.forum.nokia.com/devices/matrix_oviStore_1.html Identify in advance the appropriate countries to which you will distribute your content. Please keep in mind that content may be considered appropriate in some countries but not in others. For example, gambling and risqu content is prohibited in some Middle Eastern countries.
17 (75)
The following examples illustrate how content is presented and promoted to users within the Ovi Store in both the on-device client as well as the Nokia mobile browser-based XHTML experience.
Spotlight promotional banner and application icons Series 40/S60 client

GOOD BAD
EXAMPLE OF HOW TO CROP AN IMAGE
Spotlight (mobile) promotional banner 74x74: A compelling depiction of the content/application brand or experience. Size: 74*74 pixels Icon - 46x46: Icon/ product logo of your content/application. Size: 46*46 pixels
18 (75)
Content download Series 40/S60 client

GOOD BAD
Primary screen shot: Images depicting the user experience of your game or application. Size: 96*96 pixels Primary screen shot 29x29: Smaller images illustrating content/application features. You may submit up to 3 individual images for this area. These images are extremely small and therefore are best kept simple. DO NOT try to fit too much detail in these images. Size: 29*29 pixels Icon - 46x46 This icon / product logo is shown when the end-user navigates through the store on the Nokia mobile XHTML experience. Size: 46*46 pixels
19 (75)
Content download mobile browser (ex: N900)
GOOD
BAD
Primary screen shot 96x96: Images describe the content/application brand or experience. Size 96*96 pixels Primary screen shot 29x29: Images describe the content/application features and increase the visibility of the content/application experience and actual visuals. Images DO NOT use visuals that describe elements in an overly detailed manner. Size: 29*29 pixels Icon - 46x46: Description of the content/application and its features. Size: 46*46 pixels
20 (75)
Content download desktop browser
Primary Screen shot 192x192: Images should describe the content/application brand or experience. Size: 192*192 pixels Primary screen shot 96x96: Should describe the content/application features and increase the visibility of the content/application experience within the desktop browser. Images Keep it simple; Avoid using visuals with too much detail that may have problems rendering clearly to mobile device users. Size: 96*96 pixels
21 (75)
2.9
Images and Icons
There are only a small number of image and icon files that the publisher must supply. The rest are optional. In other words, they can be generated by the system from the file supplied by the publisher or they are optional to the content. The publisher can submit an image (for example, 256X256 pixels) and in some instances the system will resize it to the correct pixel size depending on where the image will appear. Then the publisher can edit the image if necessary. The file size of images must be as small as possible. In addition to normal optimizations, there are other factors that can increase the size of an image and these must be considered when creating images and icons: Transparency Amount of colors Gradients and complexity
Publishers can submit the following file types: JPEG -> converted by the system to smaller JPEG per device resolution PNG-8 -> converted by the system to smaller PNG-8 per device resolution PNG-24 -> converted by the system to smaller PNG-8 per device resolution
Here is an example of how the metadata images and icons are used in a high resolution touch phone like the Nokia N97. The images and icons shown in the figure are explained in Table 1.
22 (75)
NOTE: The Icon 256 X 256 and Primary screen shot 256x256 are the most important files the publisher must prepare before starting to create new content. These files can contain the same image but the file name must be different. These are the minimum files necessary to successfully create a content item.
Table 1 describes: The names of all the images and icon that can be used when creating new content The purpose of the image or icon Size in pixels of the image or icon If the image or icon needs to be supplied by the publisher If the system will generate it or not Any comments about the file
23 (75)
Table 1 To see where the images are used, refer to the previous example figure. Name Purpose Size (pixels) Icon -256x256 This icon / product logo is shown when the end-user navigates through the store via the Ovi Store desktop experience. This image is used to represent your brand product. The icon will be automatically scaled down to other resolutions. Icon- 96x96 This icon / product logo is shown when the end-user navigates through the store on Nokia touch screen devices. 96x96 10 Bytes2MB. Square Format: JPG, PNG Icon- 85x85 This icon / product logo is shown when the end-user navigates through the store on QVGA resolution Nokia devices. 85x85 10 Bytes2MB. Square Format: JPG, PNG Icon- 46x46 This icon / product logo is shown when the end-user navigates through the store on the Nokia mobile XHTML experience. Primary screen shot 256x256 This screen shot image as shown below, appears as the first image in the content item page on the Ovi Store desktop experience. The screen shot should depict the user experience of your game or application. 46x46 10 Bytes2MB. Square Format: JPG, PNG Min 256x256, Max 2000x2000. 10 Bytes2MB. Square. Format: JPG, PNG Yes No Optional Yes (scaled down from Icon -256x256) Editable by the publisher after system has generated it Optional Yes (scaled down from Icon -256x256) Editable by the publisher after system has generated it Optional Yes (scaled down from Icon -256x256) Editable by the publisher after system has generated it Min 256x256, Max 2000x2000. 10 Bytes2MB. Square. Format: JPG, PNG Supplied by Publisher Yes No System generated Comments
24 (75)
Name
Purpose
Size (pixels)
Supplied by Publisher Optional
System generated
Comments
Primary Screen shot 192x192
This screen shot image as shown below, appears as the first image in the content item page on Nokia touch screen devices. The screen shot should depict the user experience of your game or application.
192x192. 10 Bytes2MB. Square Format: JPG, PNG
Yes (scaled down from Primary screen shot 256x256)
Editable by the publisher after system has generated it
144x144 10 Bytes2MB. Square Format: JPG, PNG
Optional
Primary screen shot 96x96
This screen shot image as shown below, appears as the first image in the content item page, on QVGA resolution Nokia devices. The screen shot should depict the user experience of your game or application.
Optional
25 (75)
Name
Purpose
Size (pixels)
System generated
Comments
This screen shot image as shown below, appears as the first image in the content item page on the Nokia mobile XHTML experience. The screen shot should depict the user experience of your game or application.
Optional
26 (75)
Name
Purpose
Size (pixels)
Supplied by Publisher Yes/ Optional
System generated
Comments
Secondary screen shot 256x256
This screen shot image as shown below, appears as the second image in the content item page on the Ovi Store desktop experience. Screen shot should depict the user experience of your game or application. The screen shot will be scaled down to other resolutions.
Min 256x256, Max 2000x2000. 10 Bytes2MB Square. Format: JPG, PNG
No
Used if publisher wants to rotate the Primary screen shot
This screen shot image as shown below, appears as the second image in the content item page on Nokia touch screen devices. The screen shot should depict the user experience of your game or application.
192x192 10 Bytes2MB. Square Format:: JPG, PNG
Optional
Yes (scaled down from Secondary screen shot 256x256)
27 (75)
Name
Purpose
Size (pixels)
System generated
Comments
This screen shot image as shown below, appears as the second image in the content item page on Nokia touch screen devices. The screen shot should depict the user experience of your game or application.
This screen shot image as shown below, appears as the second image in the content item page on QVGA resolution Nokia devices. The screen shot should depict the user experience of your game or application.
Optional
This screen shot image as shown below, appears as the second image in the content item page on Nokia mobile XHTML experience. The screen shot should depict the user experience of your game or application.
Optional
28 (75)
Name
Purpose
Size (pixels)
System generated
Comments
This screen shot image as shown below, appears as the second image in the content item page on Nokia mobile XHTML experience. The screen shot should depict the user experience of your game or application.
Yes (scaled down from Secondary screen shot 256x256).
Tertiary screen shot 256x256
This screen shot image as shown below, appears as the third image in the content item page on the Ovi Store desktop experience. Screen shot should depict the user experience of your game or application.
Min 256x256, Max 2000x2000. 10 Bytes2MB Square. Format: JPG, PNG
Yes/ Optional
No
Used if publisher wants to rotate the Primary screen shot
This screen shot image as shown below, appears as the third image in the content item page on Nokia touch screen devices. The screen shot should depict the user experience of your game or application.
Optional
Yes (scaled down from Tertiary screen shot 256x256)
29 (75)
Name
Purpose
Size (pixels)
System generated
Comments
This screen shot image as shown below, appears as the third image in the content item page on Nokia touch screen devices. The screen shot should depict the user experience of your game or application.
Yes (scaled down from Tertiary screen shot 256x256).
Editable by the publisher after system has generated it.
This screen shot image as shown below, appears as the third image in the content item page on QVGA resolution Nokia devices. The screen shot should depict the user experience of your game or application.
Optional
66x66 image shown in the content item details page and is used in thumbnail in high resolution mobile.
Optional
Yes (scaled down from Tertiary screen shot 256x256).
30 (75)
Name
Purpose
Size (pixels)
System generated
Comments
This screen shot image as shown below, appears as the third image in the content item page on Nokia mobile XHTML experience. The screen shot should depict the user experience of your game or application.
Spotlight (desktop) promotional banner 967x277
Spotlight is a content promotion ad slot, presented in the Ovi Store desktop experience, which can be used to link directly to a content item. This ad is visible for logged in users of the Ovi Store desktop experience.
967x277
Yes/ Optional
No
Publisher can supply but it is optional and content works without it
Spotlight (mobile) promotional banner
Spotlight is a content promotion ad slot, presented in the Ovi Store mobile experience, which can be used to link directly to a content item.
111x111
Yes/ Optional
No
Spotlight (mobile) promotional banner
Spotlight is a content promotion ad slot, presented in the Ovi Store mobile experience, which can be used to link directly to a content item.
74x74
Yes/ Optional
No
31 (75)
3. 3.1
SIGNING SYMBIAN AND JAVA APPS Current process for signing apps
All Symbian based apps, and Java apps are required to be signed before they can be published. Nokia helps to make this easier for you by offering to Express Sign your Symbian based content, and JavaVerified sign your Java content. And the best part is both offerings are free services to all Ovi Publishers.
Apps already signed by another signing service can still be submitted. Applications already signed or that have an expired, or expiring certificate can also be signed using this service. For Symbian apps a new UID will need to be used if not already assigned by Nokia under this program.
NOTE: Symbian applications for S60 1st and 2nd Ed devices are not supported by Ovi Store and hence do not need to be signed. So please do not use the Nokia-supplied UIDs for S60 1st and 2nd Ed applications.
3.2
File types supported
Nokia offers free signing to Ovi Publishers for apps that are developed with the following languages: Symbian (SIS files): written with Symbian C++, Qt or Adobe Flash Lite Java (JAD/JAR files): written with Java 3.3 Steps to get your apps signed by Nokia
Before submitting your content, follow these steps when requesting Nokia to sign your application. All steps can also be found here: http://www.forum.nokia.com/Distribute/Packaging_and_signing.xhtml.: Symbain: Ovi Publisher emails Publisher Support (publishtoovi.support@nokia.com) and requests more details Ovi Publish support asks publisher to review and accept new terms and conditions Ovi Publisher accepts new terms and conditions and provides IMEI numbers for up to 5 devices Ovi Publish support sends publisher UIDs, a cert installer, and developer cert/key pair for testing their app Ovi Publisher packages their unsigned SIS file using the UID provided and tests on their device making sure it is tested against Symbians signing criteria (http://developer.symbian.org/wiki/index.php/Symbian_Signed_Test_Criteria_V4_Wiki_version) Ovi Publisher submits their app (unsigned SIS file with the UID provided) to the intake tool QA and moderation will test the app and if it passes it will be express signed by Nokia and put into Ovi Store
Java: Ovi Publisher emails Publisher Support (publishtoovi.support@nokia.com) and requests more details. Ovi Publish support sends additional details in email and asks publisher to review and accept new terms and conditions. The email from support contains information for Java supporting documentation and how to submit your content. Ovi Publisher submits their app to the intake tool.
32 (75)
QA and moderation will test the app and if it passes it will be Java Verified signed by Nokia and put into Ovi Store.
3.4
Certified signing Symbian apps
Its important to note that Nokias signing of Symbian apps only applies to apps that would normally be Express signed. For apps (SIS files) that require Certified signing will require a third party signing solution, those SIS files will not be signed by Nokia.. You can learn more about Certified signing by visiting the Symbian Foundation developer site: http://developer.symbian.org/wiki/index.php/Certified_Signed_%28Symbian_Signed%29
4.
ADDING A NEW CONTENT ITEM
Once you have successfully created your Publisher account and are logged in, you can start creating new content. A content item is composed of: Metadata Descriptive text or graphics included in content item or file. A content item contains one set of metadata, which can be used by several files. File(s) The actual content file, plus information for a selected distribution. There can be more than one file per content item, for example, to support different devices. The steps to adding content are listed here and described in further detail in this chapter: Getting started checklist Choosing a content type Selecting a channel Describing content Choosing a price point Adding metadata Adding a file Choosing distribution Submitting a file to a quality assurance (QA) check
To add new content to your content items: Refer to the getting started checklist in section 4.2 Content files to make sure you have everything. Click the Content tab. Click New content item.
4.1
Choosing a content type
To choose the type of content you want to create - Click the content type.
33 (75)
NOTE: The content types that are available to choose from may vary depending on the publisher type. Personalization content, wallpaper, video, and ringtones will be available for media account publishers only. In this chapter, the Symbian application is used as an example.
4.2
Answer the legal questions relating to content compliance.
Answer the legal questions to ascertain the technical parameters of the encryption used (if any), and the purpose of that encryption. If an official classification is required, you will be prompted to submit a copy of the ECCN provided by BIS. The form to be submitted is known as a CCATS. This is the official document used by BIS to communicate the final classification of encryption items.
Click Continue.
NOTE:
Many common software products include encryption, a dual use technology developed
for civilian applications but which may be adapted for military or terrorist purposes. For this reason, encryption capabilities subject software items to target and rigorous dual-use export controls. Legislation is designed to prevent the delivery of products incorporating dual-use
34 (75)
encryption items to end users considered to be a risk to national and international security. Nokia is fully committed to complying with all relevant international export control legislation and agreements. Only decontrolled or mass-market encryption items will be published on Ovi (ECCNs EAR99 or 5D992 respectively) and Nokia reserves the right to refuse publication if the encryption item is not suitable or if inadequate information is provided by the publisher. It is the publisher's responsibility to determine the technical parameters of any encryption capability of those items submitted for publication on Ovi and to first obtain the necessary classifications and permissions for export. This information should be provided to Nokia. If not already available, the publisher may be required to first obtain an Export Control Classification Number (ECCN) from the United States Bureau of Industry and Security (BIS) prior to publication on Ovi, even if the content is developed or distributed outside the United States. Please refer to Section 17.7, Export Control, in the Terms and Conditions of the Ovi Publisher Agreement for more details. BIS regulates exports of products and technology, including software offered for download extraterritorially, i.e. outside the U.S. An "export" is defined as the shipment, transfer, or electronic transmission, either from the U.S. to a foreign country or within the U.S. to an embassy or affiliate of a foreign country. Posting software products to the Internet for download constitutes an export even if the software is not ultimately downloaded. For more information about export controls for encryption items, please refer to http://www.bis.doc.gov/encryption.
4.3
Create the content item.
Metadata is descriptive text or graphics that is used to classify or define a content item or file. The content item creation page requires to fill the mandatory metadata pertaining to the content you wish to sell on Ovi Storedisplay name, description, Global price point, Preferred billing method, Support email address and website, content icon and content screen shot.
35 (75)
Click Create. You will be directed to the content tab page.
36 (75)
4.4
Adding additional optional metadata
On the content item tab you can edit the metadata you just entered on the previous content creation page and you may add additional optional metadata such as secondary and tertiary icons. The next step after completing all content item metadata is to upload the actual application. For a complete list of metadata, see section 9.
To Add or edit information click on the Edit. An information box appears for each field describing what you must enter.
To get context help about a field, move your mouse over the green question mark.
37 (75)
Table 2 lists the supported content types visible in desktop and mobile clients. Each content item can only belong to one content area at a time, for example, Applications - Business, Games - Arcade.
Table 2 Content type Possible content areas File extensions currently supported Symbian application (Symbian applications must be Symbian Signed to pass QA). Java application (Java applications must be signed to pass QA). Web RunTime (WRT) widget Applications Games Flash Lite application (Flash Lite applications must be Symbian Signed for S60 devices to pass QA) Applications Games .sis .sisx .nfl Note: Currently SIS files created with the Adobe Mobile Packager tool will not be supported and will be rejected during the QA process. Audio Audio .mid .mp3 .mp4 .aac .amr .wav .mp2 .wma Ringtone Ringtone mid .mp3 .aac .amr .wav .mp2 .wma Video Video .3gp .mp4 .3g2 .wmv .asf .avi Theme (.SIS Theme applications must be Symbian Signed to pass QA.) Wallpaper graphics .jpg .png .gif .deb 1 MB Theme .sis .nth .deb 2 MB 35 MB 35 MB 2 MB Applications Games .jar +.jad (both files are mandatory for a single Java content item) .wgz 2 MB 2 MB Applications Games .sis .sisx Maximum File size 350 MB
Maemo Qt based Application (.SIS applications must be Symbian Signed to pass QA)
Applications Games Applications Games
.deb .sis .sisx
350 MB 350 MB
38 (75)
Each content area has its own set of categories. These vary depending on the chosen content type. All available content areas and their respective categories are listed in Table 3.
Table 3 Applications Books Business & Finance City Guides & Maps Communication Education & Reference* Entertainment Games Action Adventure Card & Casino Classics & Arcade Education Puzzle Ringtones Classical & Jazz Comedy Country & Folk Dance Hip Hop/R&B Holidays Graphics Screensavers Themes Wallpapers Video Entertainment Comedy Kids & Family Lifestyle & Leisure Music Sports Science & Technology Travel TV & Film Audio Arts & Entertainment Comedy Kids & Family Lifestyle & Leisure Sports Science & Technology Travel TV, Film & Radio
Health & Fitness Lifestyle & Leisure Music News & Weather Photo & Video Productivity Social Networks Sports Tools
Sports & Racing Strategy Trivia & Word
Latin Oldies Religious Rock & Pop Sounds Sports TV & Film World
NOTE: The categories shown reflect the Store's new information architecture. Consumers will continue to see the old categories until a future release. For example though you may choose the "Books" category, your book content will continue to appear under "Entertainment" until the version of store supporting this category is released.
4.5
Choosing a global price point
The publisher chooses a global price point (price amount) to implement for the content. The pricing structure is based on predefined price tiers where: The retail price of a content item is the same regardless of the payment method. For each price point Nokia has defined a global retail price. Additionally each price point may have country and operator specific exceptions. There are 15 price points available. This means that Nokia and the Other Ovi Store publishers have the same price points available to them. The publisher: Selects a global price point for each content item You may change a content items price point only once in a months time. Specifies the countries where the item is available for sale Is able to select the payment options. (Default all applicable)
39 (75)
There are 15 price points to choose from.
You can define the price point in the content item page.
4.6
Selecting a preferred billing method
The publisher selects a billing method by which the publisher prefers the end-user to purchase the content by. The billing payment options are Credit card & operator billing or Credit card only.
NOTE: Your billing preference will be applied in most cases, but if your stated preference is NOT possible, the system will default to an allowed billing method that will be presented to the end user. For example, some operators may not allow credit card billing in which case operator billing will be used by default.
4.7
Adding a file
The file is the actual application or media content file you wish to publish on Ovi Store. In addition you will need to provide related information regarding the file and select the target distribution (where you want the content to surface devices, countries and languages. Refer to section 3.0 for more details about Nokia signing Symbian and Java apps at no cost for Ovi Publishers.
To add a file: Click Upload file in the notification massage or click on the content files tab.
40 (75)
Enter the details of your file. Follow the instructions describing what each field is for. Note: In this screenshot the content item selected was a Symbian application. The actual input fields and information you see may vary depending on the content type youre uploading.
Click Upload and Continue.
NOTE: You can add numerous files to a single content item by clicking Add new file. All files in a single content item share the same general and channels metadata. File specific file metadata, for example, version, application UID are not shared.
41 (75)
4.8
Choosing distribution for your content item
You must choose the distribution compatibility for each file in your content item. The Distribution tab contains tabs for: Devices Countries Languages
4.8.1
Choosing device compatibility for distribution
You can choose the specific Nokia devices which are best suited for your content by selecting all devices or by specifying devices individually.
To choose the distribution compatibility of your file: Click the Devices tab. Choose the Nokia device or platform to which you would like to distribute. Devices are viewed in a tree structure, which can be expanded by clicking the plus sign (+).
42 (75)
Roll your mouse pointer along the proposed compatibility bar of the device you want to distribute to. The bar information changes and you can choose the correct compatibility.
NOTE: - You must specify at least one device as Fully Tested per platform. Otherwise is will fail the QA review process. - The device list includes devices that are not yet supported by the Ovi Store. By selecting these devices as compatible, you choose to distribute your content to these devices in the future when they become available. An email will sent once new devices are supported by Ovi Store - The latest list of Nokia devices supported by Ovi Store is available here: http://www.forum.nokia.com/devices/matrix_oviStore_1.html
You can assess your file and choose its compatibility. Fully tested: You have executed full test cases with this file to this configuration. Briefly tested: The file's main functionality has been briefly tested with this configuration. Assumed to work: You assume that platform compatibility will guarantee that this file works with the configuration. Might work: The file has not been tested, but you assume that it might work with the configuration. Not compatible: The file should not work with the configuration. Do not even try. Not known: Shown only when a new operator, terminal or language is added to the system and the compatibility is not defined yet.
43 (75)
4.8.2
Choosing country compatibility for distribution
To choose the distribution compatibility for a country or countries: Click the Can be distributed in any country and any operator check box to choose all countries. OR Click the Countries tab. Click the relevant region/country.
Regions and countries are viewed in a tree structure, which can be expanded by clicking the plus sign (+). Check the on the check box for the region or specific country you wish to distribute to.
4.8.3
Choosing language compatibility for distribution
To choose your content distribution compatibility for a country or countries: Click the Works for all languages check box to choose all languages. OR Click the Languages tab. Roll your mouse pointer along the proposed compatibility bar of the language base to which you would like to distribute. The bar information changes and you can choose the correct compatibility.
44 (75)
4.9
Select the Save button. Submitting content to a quality assurance check
Before a content item can be published, it must be submitted to a quality assurance (QA) for review. Once you have added the distribution information you can check submit the file to QA. Click the File tab. Make any final changes to the general metadata if necessary. Click Submit to QA.
You will receive a confirming notification that the file has been submitted to QA..
45 (75)
Adding additional files.
A content item may have several content files associated with it. Each content file should serve a specific distribution. To expand the distribution of an existing content file go to the existing content file and add distribution (i.e., devices, countries or languages). You may also copy and paste an existing distribution of an exiting file by clicking on the Load Distribution link. This will pull up the existing distribution. You will need to modify the distribution so that the files do not overlap. To update the actual file (binary) of a content file go to the existing content file and replace the existing file. To create a version that serves a different distribution all together create a new content file.
5. 5.1
TIPS: DISTRIBUTING GLOBAL CONTENT LOCALLY Increasing discoverability of content in Ovi Store
If your content has global appeal and you wish to target territories that are language sensitive you can make it easier for end users to find your content by following these tips: Transliterate your content display name by changing the letters of the name into the corresponding characters of the local language Localize the content description Translate your application interface into that language. Add content type information (e.g.: ringtone, theme, game etc) to your content description. Add the word free to your content description (but only if your content is indeed free!).
The translations of your metadata (display name and description) will appear to end users who have chosen that matching language in their Nokia device settings (or in their device browser in the case of the xHTML version of Ovi Store).
46 (75)
5.2
Increasing downloads of localized content
For applications that are audience (country and/or language) sensitive, translate the application itself so that end users of the specific languages will choose to use it. After translating the application, upload the different associated content files to the content item and target each translated version to the appropriate distribution.
6.
SECURITY
Restricted time URL All paid content is automatically assigned with a 6 hour time restricted URL. This means that once a consumer purchases a content item from Ovi Store, the URL to access the download of that content item will only work for the next 6 hours. Free content is not assigned with a restricted time URL and can be downloaded as often as a consumer wants.
47 (75)
7.
QUALITY ASSURANCE (QA) PROCESS
All content items submitted for publishing go through a quality assurance process. The main purpose of the the QA review is to ensure consumers receive quality content and application experiences through Ovi Store. We also strive to achieve fast publishing turnaround for developers. The best way to ensure your content is approved quickly is to test it thoroughly on all target devices before submitting it to Ovi Store. Nokias QA process consists of the performance of a number of tests as well as a review of legal and content appropriateness on all items submitted by developers.
NOTE: Testing does not cover every aspect of the content experience or application functionalities, nor does it cover all possible phone, operator and language combinations. Rather, we focus on the verification of basic or core functionality. It is the responsibility of the content publisher to fully test, validate and sign their application content prior to submission to the Ovi Store. Do not expect Ovi consumers and users to test your content for you. If you do, they may not buy from you again!
As you prepare a file to be published, its QA status will pass through several states. Each state tells you where the file is in the process and what, if anything, you need to do next to make sure the file is successfully published. The QA states are: NOT SUBMITTED TO QA - A file has not yet been submitted to QA. The desired publisher action is to submit a file to QA. PENDING - The file has been submitted to QA but is still in the queue for testing or in the QA process IN PROGRESS - The QA review process is currently taking place. FAILED - The file has undergone testing and was found lacking in functionality or compatibility. In the file view, failed link, you will be able to see reason the file failed QA. PASSED - The file has undergone testing and was found to have good functionality and compatibility. The file will be published to Ovi Store. After the quality assurance process is complete you will receive an email stating the status of the item in the system. If the QA fails, the reason and related test case will be provided by email. 7.1 Purpose of Testing
Nokia tests content prior to publishing to ensure consumers experience the same level of high quality across all content types in the Ovi Store. While it is expected that all publishers will thoroughly test their content and applications on all target devices before submittal, if Nokias QA test process identifies any problematic content, the publisher of that content will be notified with a summary of the test failure results. It is then the publishers responsibility to either correct the problem or change their target device or distribution selection.
7.2
Testing criteria
When you submit content for testing during the QA process there are factors that must be taken into account before submission. The publisher must check that content meets these criteria before submission.
48 (75)
Generic entry criteria for testing

Publishers must complete the content submission form and lock the file Device distribution must have at least one specific device selected with a proposed compatibility status of FULLY TESTED per platform. You may also select to distribute in any country. Localization or language should be stated if applicable to ensure the right content is targeted to the right market. You may select to distribute content without specifying target languages by selecting Works for all languages. Only Nokia billing is accepted. If the content contains any other external billing solution it will be rejected. For signed content items, such as Symbian signed or Java Verified signed, channel specific metadata information must be entered for the "End date for published content" field. The date entered should be no later than the expiration date of the certificate. Tip for identifying the end date: Java ME applications: 1. Open the JAD file with a text editor (e.g. notepad) 2. Copy the contents of the MIDlet-Certificate-1-1: field (text starting from the colon and ending to the carriage return) and paste it to an empty text file. 3. Save the text file 4. Change the file extension to .cer 5. Open the file. The validity is presented in the Valid from field SIS files (you can use the Signsis utility which is available with the Symbian development tools). 1. On command line the following is executed: "Signsis -op sis_file_name.sis" 2. The outcome has usually multiple certificates, the validity period here would be the first listed certificate with the fields. For example: Validity Not Before: May 27 00:00:00 2008 GMT Not After : May 27 23:59:59 2018 GMT Content that includes links to external sites will be rejected by QA.
Entry criteria for testing Symbian or Java applications

Symbian application submissions (of the .sis and .sisx file type) must be pre-tested and must fulfill the Symbian Signed Criteria, which is available at: www.symbiansigned.com. If the Symbian application is developed using Nokia Qt SDK, then the .SIS file called Nokia Smart Installer must also be included and signed. See http://wiki.forum.nokia.com/index.php/Nokia_Smart_Installer_for_Symbian. Refer to section 3.0 for more details about Nokia signing Symbian apps at no cost for Ovi Publishers. Java application submissions must be pre-tested and signed. Services like Java Verified can be used to verify applications work on Nokia devices. Visit http://www.javaverified.com/ for more information on the Java Verified service. It is not mandatory to use Java Verified. VeriSign and Thawte are accepted for signing Java applications. Note: VeriSign signed MIDlets cannot be installed to Series 40 5th Edition, Feature Pack 1 devices. Refer to section 3.0 for more details about Nokia signing Java apps at no cost for Ovi Publishers.
49 (75)
Java and Symbian applications must be signed appropriately and no application certificate error message will be allowed for content or applications on Ovi Store. For best practices on how to sign applications go to the Forum Nokia discussion boards at http://discussion.forum.nokia.com/forum/forumdisplay.php?f=124
There must be Help and About available somewhere inside the application where consumer-users can find more information about the application that they have just installed.
The application language use must be consistent and appropriate throughout the user experience.
All applications submitted to the Ovi Store must be able to provide proof that Symbian Signed and Java Verified requirements are met if requested. For more information, see http://forum.nokia.com/main/0,6566,22,00.html. Nokia may require third party testing for applications. If the QA team receives content that frequently fails, it is the publishers responsibility to submit information to Nokia that the content works. Third party testing may be required as proof.
Entry criteria for Maemo application testing

See detailed Maemo Ovi Store entry requirements: http://www.forum.nokia.com/Distribute/Packaging_and_signing.xhtml
Entry criteria for Flash Lite application testing

SIS or WGZ files for supported S60 devices SIS files must be properly signed Refer to section 3.0 for more details about Nokia signing Symbian apps at no cost for Ovi Publishers. NFL files for supported Series 40 devices NFL files do not have to be signed Flash files (SWF) are not accepted. All Flash applications must be packaged as either a WGZ, NFL or as SIS Symbian Signed files. Flash files (SWF) packaged as SIS, NFL or WGZ files can not be static SWF files intended to be used by consumers as animated wallpapers or screensavers. SIS, NFL or WGZ files found to contain these types of SWF files will be rejected by QA. Installing a SIS file to an S60 device must not install or prompt to install the Adobe Flash or Flash Lite player. SIS files that are created using the Adobe Mobile Packager Tool will not be accepted and will be rejected during the QA process. Forum Nokia offers a free web based Flash packaging service: http://www.forum.nokia.com/Resources_and_Information/Explore/Web_Technologies/Flash_Lite/ Flash files must be published as versions 1.1, 2.0, 2.1 3.0 or 3.1. For information on device specification, please refer to http://www.forum.nokia.com/devices/matrix_all_1.html and select your version of Flash for a list of applicable devices. Note: ensure that the version of Flash Lite youre publishing your application to is compatible with the version of Flash Lite that is available on the supported device. For example, if your application is published as Flash Lite 3.0, and then only select those devices that support the Flash Lite 3.0 player. If you select a device with an older player (Flash Lite 2.0 for example), the application will not run.
50 (75)
Entry criteria for Wallpaper/Graphic testing

File type is PNG, GIF or JPEG Image ratio: identical to the target device screen ratio. Bit depth must be between 8 and 24
Entry criteria for audio testing

Music content (ringtones etc): Bit rate must be a minimum of 128 kbps Maximum file size is 35MB Audio sample rate must be a minimum of 44 kHz Audio content with little or no music (primarily spoken word assets, podcasts, audio books etc.) Bit rate must be at minimum 16kbps Audio sample rate must be at minimum 24 kHz Maximum file size for audio files is 35MB Note: Full track music will NOT be accepted to Ovi Store.
Entry criteria for Games on touch devices

Games on touch devices must: Be touch enabled. Utilizes the full screen and be fully playable without the device's generic virtual d-pad. Ensure that the virtual d-pad is switched off by default.
7.3
Submission process
The following provides information about submitting content for QA.
Resubmission process If a previously submitted content item fails the QA process or if the publisher needs to make changes, the publisher may unlock the content item, edit it and relock to resubmit to QA. Content server failure policy If the content or application makes http calls to an external service--for example, a content web server--it is the publishers responsibility to ensure that the external server is ready and functioning to allow the publishing QA team to perform the necessary testing. Submissions will fail testing if the QA team is unable to complete testing of core functionality including access to external services. Withdrawing submitted content Content can only be withdrawn if the QA team is not already testing it. In other words, if the status of the content item is pending then a content item can be unlocked to withdraw it from the QA. If any other status is shown, contact Ovi Customer Care to find out if the content item has already began testing.
51 (75)
7.4
Checking a content items QA status
Once content has been submitted to QA, you can check the QA status of a content item or of individual files. To check the status of a content item, open the Content Item tab.
7.5
Checking an individual files QA status Scroll down the Content Item tab to check the status of an individual file.
If you want more detailed information about a files QA status, click Details of file to open the File tab.
You can get more details about your file by clicking on the Pending, in progress, Passed or Failed boxes. The status of the item is also represented by a colored status bar.
52 (75)
The QA status bar shows an overview of the file. Table 3 lists and describes the colors representing the different statuses of a content item or file that is submitted to QA. Table 3 Color Green Red Orange Blue Green border
Status description Passed Failed Pending In progress QA complete: Does not mean that file passed the QA, just that the QA was completed
Status bar
Red border 8.
QA failed to complete the process EDITING CONTENT
You can edit content at any time and during any content status. Content item and content file/s can be edited independently of one another. Editing content that is currently in the QA process You may edit an item or file that is undergoing the QA review process. This will however remove the item or file from the QA review process. After making the changes resubmit the item or file to QA. This will restart the QA review process from the beginning. If your item or file is already published, the published revision of the item or file will remain published until the edited revision is QA passed after which it will replace the previous published revision in the store.
In the Content tab click Content Items.
Click the content item you want to edit. The Content Item tab opens.
53 (75)
8.1
Editing the content item Click the on Edit item button.
Select the field you want to edit and click on the Edit link.
Submit the changes to QA so that the QA review can start.
54 (75)
8.2
Editing a file
To edit an existing file, go to the content files tab and click Edit file on the relevant file: Click View metadata.
Click Edit to edit the file information.
When your changes are complete, click Submit changes to QA for the QA review to start
55 (75)
9.
UNPUBLISHING CONTENT ALREADY PUBLISHED IN OVI STORE.
Publishers may unpublished content published in Ovi Store at their discretion. Publishers may unpublish a complete content this action will also unpublish all the associated content files, or a publisher can select to unpublish only a specific content file, Unpublishing will prevent the chosen content from being available in Ovi Store for consumers to download. The unpublished content will remain available in the publisher interface where the publisher can select to republish the content by submitting it again to QA. Nokia will unpublish the content item and or files within 1-2 business days of the unpublihsing request. When unpublished your content state will be changed to unpublished.
Unpublishing a content item: Go to the content item page, click on the Unpublished button at the bottom of the page. After confirming you want to unpublish your file you will receive a notification that your request was received and the file will be moved to Pending unpublishing state.
56 (75)
Unpublishing a content file Go to the content files tab, select the content file you wish to unpublish. Click on the Unpublish button at the bottom of the content file page. After confirming you want to unpublish your file you will receive a notification that your request was received and the file will be moved to Pending unpublishing state.
57 (75)
10.
PROMOTING CONTENT ON OVI STORE SPOTLIGHT PROMOTION
In addition to the standard graphical and text-based promotion in Ovi Store, Nokia also offers publishers the option to submit additional graphical and metadata assets (see below) that Nokia can use to help elevate the publishers Brand and potentially drive additional downloads.
Each Spotlight placement enables a publisher to gain additional promotional push within a slot found in categories across all Ovi Store platforms; Web, Mobile Web, and Mobile Client. Spotlights can significantly enhance content visibility and download rates in Ovi Store. Spotlight placement is located at the top of each category area and provides a larger thumbnail image and an additional line of text below the content item name.
Placement 1: Content Areas appear in Device Client and XHTML experiences (5 Content Areas) Spotlights in 4 content areas: Applications Games Personalize Audio & Video
58 (75)
Placement 2: Device Client Categories (same for XHTML)
Spotlights are available in these categories shown at the right. You can find categories on Ovi Store by selecting the soft key Option under an active Content Area and then select Categories to browse Within Games- categories include: Action, Adventure, Arcade, Card & Casino, Puzzle, Sports, Strategy, Trivia, Word. Within applications: Business, City Guides/Maps, Entertainment, Music, News & Info. Photo & Video, Reference, Social Networks, Sports, Utilities. Within Audio & Video: Music, Movies, Podcasts. Within Personalization: Ringtones, Wallpaper, Themes.
59 (75)
Spotlight shown in Application > Top Free Category
To take advantage of this promotional opportunity, publishers should ensure content is available for Nokia to select publishers should be sure to add the metadata shown in the diagram below to the <content title>. The Ovi Store team will monitor your contents performance for the duration of your Spotlight run.
NOTE: Content will be re-submitted through the QA and Moderation process after metadata is added prior to Spotlight promotion. The screenshot below highlights an area on Ovi Publish where publishers may upload images and copy for spotlights promotion on device and on desktop. Please ensure all files are completed including those marked optional.
11.
USER ACCOUNTS AND ROLES
All companies wishing to sell or distribute content on Ovi store must first register at publish.ovi.com to become a publisher. Once the company is verified and contract agreements are in place, new users can be added for that company. A role is assigned to each user when creating an account.
60 (75)
11.1
Roles
When a publisher registers for the first time the first user created is assigned a cp_manager role. User roles determine their access rights. The roles available include: cp_manager administrator access Can manage users Can edit publisher company information Can see agreements for that publisher company Can see all content items of any user in the company Can upload and edit all content items of any user in the company Can view the Ovi Reports of the company
cp_developer Can see all content items of any user in the company Can upload and edit all content items of any user in the company
cp_developer_limited Can see only that users content items Can upload and edit only that users content items
All roles are only assigned within a specific company.
11.2
Add users
Anyone who is a cp_manager can add new users for their company. A cp_manager can create a user with a cp_manager role.
11.3
Company information
Company information must be kept up to date. Anyone who is a cp_manager can edit company details.
12.
FINANCIAL RELATED ISSUES
For all financial related information, refer to the Ovi Store publisher Terms and Conditions at publish.ovi.com or at
https://publish.ovi.com/ndas/show_accepted_nda For Ovi Store reporting information, see the Reporting Guide within the Ovi Publish support section. The Reporting Guide explains: Calculations for revenue projection and Relationship between Downloads, Purchases and Projected Revenue.
13.
METADATA DETAILS Description Mandatory. The name of the content item shown to end users. Limitations/Notes 2-30 characters, truncated in some views. Variability Lang
Metadata name Display name
61 (75)
Metadata name Description
Description Mandatory. Description of the content item shown to end users. Max. 500 characters.
Limitations/Notes 2- 500 characters One per language
Variability Lang
Category
Mandatory. Users will see the name of category you have chosen for your content underneath your content items name in the Ovi Store user interface.
The categories shown here reflect the Store's planned recategorization. Old categories will be displayed in Ovi Store until a future release. For example: the new "Books" category selection will continue to appear under "Entertainment" category until the version of store supporting this recategorization is released.
None (this means that an item is in same category independent of language. Category names are localized elsewhere.)
Keywords
Mandatory. Keywords are matched to users' searches and help return accurate search results.
100 characters
None
Mood Tags
Optional. Mood tags best describe the overall mood of your application or content. Will be used to surface relevant content to end-users in and across categories
Selection of up to 3 tags.
None
Global Price point
Mandatory. The price point selected represents the approximate end user price. Actual end user price is determined by Nokia in accordance with operator and currency mapping (See the Billing Matrix for approximate end user prices across markets).
Only one option can be selected.
None
62 (75)
Metadata name Preferred billing method
Description Mandatory. The selected preference for billing method will be applied in most cases, but if your stated preference is NOT possible, the system will default to an allowed billing method that will be presented to the end user. For example, some operators may not allow credit card billing in which case operator Billing will be applied.
Limitations/Notes Only Two values; Credit Card & Operator Billing or Credit Card only. Default is Credit Card & Operator Billing.
Variability None
DRM OMA 1.0 (Forward Lock)
Mandatory Select No or Yes If Yes, your content file will be automatically wrapped in an OMA DRM1.0 Forward Lock wrapper. If No, no Forward Lock will be applied. Default is No. more info: http://en.wikipedia.org/wiki/OMA_DRM
No or Yes
WRT, Widgets are not supported. Java applications and *.NFL files for S40 devices are not supported. Maemo N900 is not supported.
Start date for published content
Optional. Availability date after which the content item may be visible in Ovi Store. Country specific exceptions are possible.
None
End date for published content.
Mandatory for signed content. Date after which the content item may NOT be visible in Ovi store. Date entered should be no later than the expiration date of the certificate. Country specific exceptions are possible.
None
Support email address
Mandatory. The publisher support email that will be used by consumers to provide direct feedback to you on your app.
Valid email address
None
Support website
Mandatory. The publisher support URL that will be used by consumers to find out more about your app.
Valid http link
None
Additional help/support
Optional. Optional help content file for Nokia Care. This file is NOT shown to end users.
Any file
None
Episode#
Optional. The episode # from the original show (if applicable).
1-4 numbers.
Audio and Video specific
63 (75)
Metadata name Show title
Description Optional. The title of the original show.
Limitations/Notes 2-30 alphanumerical characters.
Variability Audio and Video specific
Producer/ Creator
Optional. Producer or Creator of the original show.
2-30
Creation date
Optional. Creation date of the original content (not the upload date).
DD/MM/YY
Track Title
Mandatory Ringtone title
2-30 alphanumerical characters.
Ringtone Specific
Artist Name
Mandatory. Name of performing artist.
2-30 alphanumerical characters.
Ringtone Specific
Icon - 256x256
Mandatory. This icon / product logo is shown when the end-user navigates through the store via the Ovi Store desktop experience. This image is used to represent your brand product. The icon will be automatically scaled down to other resolutions.
Size: Min 256 x 256, Max 2000 x 2000. Image must be square Format: JPG, PNG
None
64 (75)
Metadata name Icon - 96 X 96
Description Optional (Automatically generated and scaled down from the 256x256 Icon).
Limitations/Notes You may upload a 96x96 specific icon. Size: 96x96. Image must be
Variability None
This icon / product logo is shown when the end-user navigates through the store on Nokia touch screen devices.
square Format: JPG, PNG
Icon - 85x85
Optional (Automatically generated and scaled down from the 256x256 Icon)
You may upload an 85x85 specific icon. Size: 85x 85. Image must be
None
This icon / product logo is shown when the end-user navigates through the store on QVGA resolution Nokia devices.
square Format: JPG, PNG
Icon - 46x46
Optional (Automatically generated and scaled down from the 256x256 Icon) This icon / product logo is shown when the end-user navigates through the store on the Nokia mobile XHTML experience. This icon was automatically generated and scaled down from the 256x256 Icon.
You may upload a 46x46 specific icon. Size: 46x46. Image must be square Format: JPG, PNG
None
65 (75)
Metadata name Primary screen shot 256x256
Description Mandatory. This screen shot image as shown below, appears as the first image in the content item page on the Ovi Store desktop experience. The screen shot should depict the user experience of your game or application. The screen shot will be scaled down to other resolutions.
Limitations/Notes Size: Min 256x256, Max 2000x2000. Image must be square. Format: JPG, PNG
Variability None
Optional (Automatically generated and scaled down from the 256x256 Icon). This screen shot image as shown below, appears as the first image in the content item page on Nokia touch screen devices. The screen shot should depict the user experience of your game or application.
None
66 (75)
Metadata name Primary Screen shot 144x144
Description Optional (Automatically generated and scaled down from the 256x256 Primary Screen shot).
Limitations/Notes You may to upload a 144x144 specific icon. Size: 144x144. Image must be square Format: JPG, PNG
Variability None
Optional (Automatically generated and scaled down from the 256x256 Primary Screen shot).
You may also choose to upload a 96x96 specific icon. Size: 96x96. Image must be square
None
This screen shot image as shown below, appears as the first image in the content item page, on QVGA resolution Nokia devices. The screen shot should depict the user experience of your game or application
Format: JPG, PNG
67 (75)
Metadata name Primary screen shot 66x66
Description Optional (Automatically generated and scaled down from the 256x256 Primary Screen shot).
Limitations/Notes You may upload a 66x66 specific icon. Size: 66x66. Image must be square Format: JPG, PNG
Variability None
Optional (Automatically generated and scaled down from the 256x256 Primary Screen shot).
29x29 pixels
None
68 (75)
Metadata name Secondary screen shot 256x256
Description This screen shot image as shown below, appears as the second image in the content item page on the Ovi Store desktop experience. Screen shot should depict the user experience of your game or application. The screen shot will be scaled down to other resolutions.
Variability None
Secondary Screen shot 192x192
Optional (Automatically generated and scaled down from the 256x256 Secondary Screen shot). This screen shot image as shown below, appears as the second image in the content item page on Nokia touch screen devices. The screen shot should depict the user experience of your game or application.
You may upload a 192x192 specific icon. Size: <size>. Image must be square. Format: JPG, PNG
None
69 (75)
Metadata name Secondary Screen shot 144x144
Description Optional (Automatically generated and scaled down from the 256x256 Secondary Screen shot). This screen shot image as shown below, appears as the second image in the content item page on Nokia touch screen devices. The screen shot should depict the user experience of your game or application.
Limitations/Notes You may upload a 144x144 specific image. Size: 66x66. Image must be square Format: JPG, PNG
Variability None
Optional (Automatically generated and scaled down from the 256x256 Secondary Screen shot). This screen shot image as shown below, appears as the second image in the content item page on QVGA resolution Nokia devices. The screen shot should depict the user experience of your game or application.
None
70 (75)
Metadata name Secondary Screen shot 66x66
Description Optional (Automatically generated and scaled down from the 256x256 Secondary Screen shot). This screen shot image as shown below, appears as the second image in the content item page on Nokia mobile XHTML experience. The screen shot should depict the user experience of your game or application.
Limitations/Notes You may upload a 66x66 specific icon. Size: 66x66. Image must be square Format: JPG, PNG
Variability None
Optional (Automatically generated and scaled down from the 256x256 Secondary Screen shot). This screen shot image as shown below, appears as the second image in the content item page on Nokia mobile XHTML experience. The screen shot should depict the user experience of your game or application.
29x29 pixels
None
71 (75)
Metadata name Tertiary screen shot 256x256
Description Optional. This screen shot image as shown below, appears as the third image in the content item page on the Ovi Store desktop experience. Screen shot should depict the user experience of your game or application. The screen shot will be scaled down to other resolutions.
Variability None
Tertiary Screen shot 192x192
Optional (Automatically generated and scaled down from the 256x256 Tertiary Screen shot). This screen shot image as shown below, appears as the third image in the content item page on Nokia touch screen devices. The screen shot should depict the user experience of your game or application.
You may upload a 192x192 specific image. Size: 192x192 Image must be square Format: JPG, PNG
None
72 (75)
Metadata name Tertiary Screen shot 144x144
Description Optional (Automatically generated and scaled down from the 256x256 Tertiary Screen shot). This screen shot image as shown below, appears as the third image in the content item page on Nokia touch screen devices. The screen shot should depict the user experience of your game or application.
Limitations/Notes You may also choose to upload a 144x144 specific icon. Size: 144x144. Image must be square Format: JPG, PNG
Variability None
Optional (Automatically generated and scaled down from the 256x256 Tertiary Screen shot). This screen shot image as shown below, appears as the third image in the content item page on QVGA resolution Nokia devices. The screen shot should depict the user experience of your game or application.
96x96 pixels
None
Optional (Automatically generated and scaled down from the 256x256 Tertiary Screen shot). 66x66 image shown in the content item details page and is used in thumbnail in Nokias high resolution mobile devices.
You may upload a 66x66 Specific icon. Size: 66x66. Image must be square Format: JPG, PNG
None
73 (75)
Metadata name Tertiary Screen shot 29x29
Description Optional (Automatically generated and scaled down from the 256x256 Tertiary Screen shot). This screen shot image as shown below, appears as the third image in the content item page on Nokia mobile XHTML experience. The screen shot should depict the user experience of your game or application.
Limitations/Notes 29x29 pixels
Variability None
Spotlight (mobile) Promotional text
Optional. Promotional teaser text shown in mobile spotlights.
2-23 characters.
Language
Marketing & Spotlight (mobile) Promotional text
Optional. Promotional teaser text shown in mobile spotlights. May also be used by Nokia in marketing campaigns.
2-50 characters.
Language
Spotlight (desktop) promotional banner 967x277
Optional. Spotlight is a content promotion ad slot, presented in the Ovi Store desktop experience, which can be used to link directly to a content item. This ad is visible for logged in users of Ovi Store desktop. .
Size: 967x277 Format: PNG, JPG
None
Spotlight (mobile) promotional banner 111x111
Optional. This Spotlight promotional ad slot is presented to users of the Ovi Store mobile experience, and can be used to link directly to a content item.
None
Spotlight (mobile) promotional banner 74x74
Optional. This Spotlight promotional ad slot is presented to users of the Ovi Store mobile experience and can be used to link directly to a content item.
None
74 (75)
14. Content item
GLOSSARY Represents the main entity that is published and includes the metadata and files for different devices. For example, Nokias Maps application.
Content type
Describes what kind of digital media the content item is. For example, Java application, audio file or theme.
CP Device
Content Provider (Publisher) The physical entity where the content item can be viewed. For example, Nokia S60 phones.
Distribution
The devices, countries and languages to which the file is distributed. For example, Nokia N95 version for Europe only.
File
The actual content file plus related information for a selected distribution. For example, xxx.SIS, xxx.JAR.
Forum Nokia
Nokias developer community and website where publishers can get technical information about devices, support, resources, and discuss ideas with other content creators. http://forum.nokia.com
Metadata Ovi Store Ovi Store Publisher Platform Qt
Descriptive text or graphics included in content item or file. For example, name, description, icon. The Nokia channel where a content item is published. The tool used to publish a content item to Ovi Store. Qt (pronounced cute) is a C++ application and UI framework for cross platform development. The same source code is used for Symbian and Maemo devices but is compiled to different content types (including desktop apps)
75 (75)

Nokia Ovi Publisher Guide for September 2010

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Nokia Ovi Publisher Guide for September 2010

Uploaded by

Copyright:

Available Formats

Publisher Guide

Nokia Ovi Publisher Guide, as of September, 2010

Pg. 31 Ed devices are not supported by 32

Nokia Ovi Publisher Guide, as of September, 2010

Nokia Ovi Publisher Guide, as of September, 2010

Nokia Ovi Publisher Guide, as of September, 2010

Nokia Ovi Publisher Guide, as of September, 2010

Nokia Ovi Publisher Guide, as of September, 2010

Nokia Ovi Publisher Guide, as of September, 2010

Nokia Ovi Publisher Guide, as of September, 2010

Nokia Ovi Publisher Guide, as of September, 2010

Nokia Ovi Publisher Guide, as of September, 2010

Nokia Ovi Publisher Guide, as of September, 2010

Log in to Ovi Publish with your verified username and password.

Nokia Ovi Publisher Guide, as of September, 2010

Changing your password

Click Change password.

Enter a new password.

If upon logging in, you forget your password:

Click the Forgot username/password link.

Nokia Ovi Publisher Guide, as of September, 2010

Enter your email address.

Nokia Ovi Publisher Guide, as of September, 2010

Providing your bank data details.

Nokia Ovi Publisher Guide, as of September, 2010

Applying for a Publisher Media account

Nokia Ovi Publisher Guide, as of September, 2010

Nokia Ovi Publisher Guide, as of September, 2010

Spotlight promotional banner and application icons Series 40/S60 client

EXAMPLE OF HOW TO CROP AN IMAGE

Nokia Ovi Publisher Guide, as of September, 2010

Content download Series 40/S60 client

EXAMPLE OF HOW TO CROP AN IMAGE

Nokia Ovi Publisher Guide, as of September, 2010

Content download mobile browser (ex: N900)

EXAMPLE OF HOW TO CROP AN IMAGE

Nokia Ovi Publisher Guide, as of September, 2010

Content download desktop browser

Nokia Ovi Publisher Guide, as of September, 2010

Images and Icons

Nokia Ovi Publisher Guide, as of September, 2010

Nokia Ovi Publisher Guide, as of September, 2010

Nokia Ovi Publisher Guide, as of September, 2010

Supplied by Publisher Optional

Primary Screen shot 192x192

192x192. 10 Bytes2MB. Square Format: JPG, PNG

Yes (scaled down from Primary screen shot 256x256)

Editable by the publisher after system has generated it

Primary Screen shot 144x144

144x144 10 Bytes2MB. Square Format: JPG, PNG

Yes (scaled down from Primary screen shot 256x256)

Editable by the publisher after system has generated it

Primary screen shot 96x96

96x96 10 Bytes2MB. Square Format: JPG, PNG

Yes (scaled down from Primary screen shot 256x256)

Editable by the publisher after system has generated it

Nokia Ovi Publisher Guide, as of September, 2010

Supplied by Publisher Optional

Primary screen shot 66x66

66x66 10 Bytes2MB. Square Format: JPG, PNG

Yes (scaled down from Primary screen shot 256x256)

Editable by the publisher after system has generated it