To ensure the high quality of content published through Nokia Store, all content submitted for publishing must go through a QA (quality assurance) process. After you have submitted your application, validation takes approximately 2 to 5 days. When the QA process is complete, you receive feedback stating whether the validation was successful. If your application meets the Nokia Store Entry requirements, it is published in Nokia Store.
If the QA tests for your application fail, you receive a test report which describes the reasons why the testing has failed. If your application fails:
The following table presents the most essential test criteria that your application must pass to be published in Nokia Store. The criteria are related to installation, functionality, robustness, co-existence, and performance. The following information is provided for each requirement:
Publishing requirements for Harmattan applications
| Nokia Store entry requirements for Harmattan applications |
Instructions in Harmattan Developer Library |
- Possible to install and uninstall the application without errors.
- Name and version of the Debian package given in the correct format.
- Is easy to install and remove completely.
- Verifies if the user wants to delete any related user content before application uninstallation.
|
|
- Does not fail if the connection breaks briefly.
- Works normally after sudden power loss.
- Application UI displayed on the foreground if a call is routed through the application.
|
- Follow power management best practices when developing your application.
- Use the APIs included in the MeeGo 1.2 Harmattan API reference in your development work.
|
- Does not interfere with device functionalities (such as use of Swipe and Lock screen) or other applications.
- Shows the correct error message when data saving fails or at startup and exit after the user accepts the termination.
- UI elements large enough to ensure a pleasant user experience on a Harmattan device
- Graphics, animations, and text clearly displayed in landscape and portrait mode.
|
|
- Complies with Nokia values and customer satisfaction criteria.
|
|
- Input fields provide a virtual keyboard in different UI modes.
|
- Ensure that the virtual keyboard behaves correctly in different UI modes (portrait/landscape). For instructions, see Controlling rotation.
|
- Does not interfere with essential device functionalities such as:
- networking features
- offline mode
- language settings
- voice calls
- video players
- camera resources
- emergency calls
- auto-start configuration
- location usage
- backup and restore
|
- Use the Resource Policy Framework provided by the Harmattan platform to ensure that your application obtains the appropriate and sufficient resources and behaves according to the appropriate device mode (such as call, camera, media player, navigator, or game).
|
- Does not visibly affect the performance and responsiveness of the system, either through specific actions or leaving the application open/running during a long period of time.
- Speed adequate for allowing a positive user experience.
- Used or allocated memory freed after the application is closed.
- CPU stays in low power mode when device is idle.
- Memory allocation and CPU usage of the application are within the allowed range.
|
|
|
|
- To ensure that your application does not systematically crash or freeze:
- Run your application on the Harmattan device to test that it works in an authentic device environment.
- Test your application also with faulty inputs.
- Verify the application behaviour with the provided debugging tools.
- Monitor the CPU and memory usage of the application with the provided sp-memusage tool.
|
- Includes the following information:
- application name
- application version number
- name of the company or developer that has created the application
|
- Check that the information is included somewhere in your application, for instance, in an About or credits menu or splash screen.
|
