This topic explains the steps you need to take to deliver and publish your web app to Nokia Store. Adding your web app to Nokia Store is the best way to make it visible to the largest number of users.
The Nokia store provides users with access to downloadable content and applications, which it delivers and installs on a phone. Unlike applications, Nokia Asha web apps are not stored in the phone's memory. Instead, they are stored on and run in the Xpress Browser Proxy server. A Nokia Asha or Series 40 phone displays the results of the processing undertaken on the Proxy server. Nokia Asha web apps do run some code locally on the phone, such as the code to dynamically alter the UI content. However, this code is resident on the phone only temporarily. Since there is no Nokia Asha web app component to install on a phone, a Nokia Asha web app cannot be made available in the Nokia Store in the usual manner. Instead, a small system-generated Java application is delivered to the Nokia Store.
This Java application, once installed on a phone, adds an icon and the application title to the phones usual app launcher screens and menus. When the user runs this application, it passes the URL of the web app to the Xpress Browser, which communicates with the Proxy server to run the web app. In this way, the small Java application makes the web app available in the Nokia Store and also makes the web app easily accessible in the phone's UI.
For detailed information about publishing a web app to the Nokia store, see the Become a Nokia Store Publisher web page. From this page you can download the following documents:
All new or updated web apps should be designed to run on the latest version of the Xpress Browser. Because the Browser is under constant development, different Nokia Asha platform and Series 40 phones will run different versions of the Browser. When a user runs a web app that requires the latest version of the Browser on a phone that has an earlier version installed, the user will be prompted to install the new version.
Before packaging your web app for submission to the Nokia Store, you must define an icon, a favicon, and a name for your web app.
You must provide at least two names for your web app:
Figure 1. Display Name and Short Name fields in the WDE Nokia Asha web app wizard
The display name should be as short as possible so that it fits well in the display when translated in many languages. The short name must be 16 characters or shorter in length and can use the following characters only: ASCII characters, dashes, underscores, digits, and spaces.
Two different icons represent your web app on a phone:
During the publication process, this icon file is retrieved and incorporated into the Java application that is made available in the Nokia Store. Icons for some popular web apps are shown in a sample apps menu below:
Figure 2. Example icons in the applications menu
The favicon for your web app is a 16 x 16 pixel image file named favicon.png. Specify the favicon by including the following in the index.html file of your web app:
<link rel="icon" type="image/png" keyref="id4f3dfef4-f3f5-481c-992f-a0240614e004">
A sample favicon for the TicTacToe web app is shown in a Favourites menu as follows:
Figure 3. Example favicons for web apps in the Favourites list
The Nokia Store publication process requires you to submit the *.wgt file of your web app.
During development, the WDE automatically packages an app before previewing it. Packaging an app prepares it for upload to the Xpress Browser Proxy server. From the Proxy server, the web app can be run in the simulator or on a phone. You can create a package for your web app without running a preview. To do this, in WDE, right-click on the project name in the Project Explorer pane and select Package Web app in the resulting shortcut menu, which is shown in the figure below.
Figure 4. Shortcut menu for packaging a web app without previewing it
After you submit the *.wgt file to the Nokia Store, your web app goes through an approval process. If it is approved, the Nokia Publish system generates the Java application and publishes it in the store. The following flowchart provides an overview of the web app publication process.
Figure 5. Overview of the web app publication process
Once published you can obtain a copy of the Java application using the option on the Publish and Share page in the Web Developer Channel.
When you update your web app, you must define a new version number within it. Submit the updated version with the new version number to Nokia Publish according to the same process used to submit the initial version. The publication process adds the new version to the Xpress Browser Proxy server. The earlier version is not overwritten; therefore, users continue to open the previous version until they update the Java application that launches the web app. You might consider providing a mechanism within your web app to alert users when a new version is available and to encourage them to visit the Nokia Store to install the updated version.
To discover and install a web app onto a phone, a consumer follows these steps:
|Opens the Nokia Store, either directly from the Nokia Store icon or through a browser.|
|Browses the content available.|
|Chooses a web app to learn more about.|
|Purchase (if necessary) and download the web app. Nokia Store delivers the web app's Java application to the consumer's phone and installs it.|
|Start the Java application from the applications list on the phone. If Xpress Browser is not installed, the user is directed to a location from which the Browser can be downloaded.|
Last updated 7 October 2013
We appreciate your feedback.