Windows Mobile Windows Marketplace for Mobile
Home Get Started Submit Idea Submit Application Submission Guidelines Prizes Terms and Conditions Winners
 
Application Submission Guidelines
The Windows Marketplace for Mobile presents a very compelling opportunity for developers to monetize applications. The Marketplace delivers an end-to-end solution for end-users to discover, purchase and download Windows Mobile 6.5 applications. This includes an end-user experience on the device, a PC website, as well as a self-service portal for developers to submit their applications or listing in the Marketplace.

Once applications pass the core test criteria, they are designed Compatible with Windows Phone applications. The test criteria also form the basis for application testing standards that applications need to pass in order to be considered for the Marketplace. All Marketplace applications, with the exception of Widgets, that pass the submission process also earn the Compatible with Windows Phone designation. The marketplace has several additional requirements that applications need to meet. Limited waivers for test cases are reviewed on an individual basis. More information is detailed at: http://developer.windowsmobile.com.
 
Program Policies
  • Once your applications successfully pass testing, you can sign the electronic Logo License Agreement listed on the Windows Mobile Application Certification Program portal, which enables you to use the Compatible with Windows Phones artwork on product and marketing materials.
  • The test criteria that is listed as Recommended is not a requirement to pass Windows Marketplace for Mobile testing.
  • The Compatible with Windows Phones logo indicates that a software product provides all the features outlined in the guidelines. It is not a quality assurance seal.
Application Types
  • Applications may be file-based or non-file based.
  • The testing guidelines and the Compatible with Windows Mobile program apply to applications that are written in managed code (Microsoft .NET Compact Framework, C#, Visual Basic) or native code (Win32) that also uses the respective code libraries.
  • The Marketplace has specific application types that are eligible for submission.
  • Widgets are only permitted to be distributed through the Marketplace and have a limited unique set of criteria.
Requirement Details
  • Installation and Un-installation Requirements:
    1. A *.CAB file is required for applications to be submitted for testing
    2. No warnings during installation.
    3. Applications that install via the Windows Mobile Device Manager must use the CAAppMgr desktop application manager program to register the application with the Windows Mobile Professional application manager.
    4. Specific guidelines for shortcuts on Programs folder created on Install.
    5. Store DLLs only in specified directories.
    6. Persistence of User Configurations in Registry.
    7. Preserve non-proprietary files.
    8. Packages must have SETUP.XML file.
    9. Install CSP section of SETUP.XML must contain valid values for each parameter.
    10. Application name must be less than 70 characters.
    11. Application must install and un-install correctly.
    12. Clean-up data from files and remove Registry Keys during un-installation.
    13. Applications must not add Files to the RAM File system during installation.
    14. CESetup DLL must install to local storage volume.
    15. No CESetup DLL for *.HME or *.TSK files.
    16. Only write to the HKEY_CURRENT_USER subkey.
  • API Requirements:
    1. Applications must use the Connection Manager to configure all connectivity options.
    2. Use system support if implementing Full Screen.
    3. Refrain from using GAPI.
  • Compatibility Requirement:
    1. Ability for an application to run on multiple devices.
  • Functionality Requirements:
    1. Specific Filename requirements.
    2. Support only one instance of an application running simultaneously.
    3. Application stability and OS functionality.
    4. Dialog Box readability.
    5. No underlined accelerators in Menus or Dialog Boxes without alternative selection methods.
    6. Shut Timers off when application is running in the background.
    7. Applications must not interfere with incoming call functionality.
  • Hardware-specific Requirements:
    1. Must not assume external storage.
  • MAPI Requirements:
    1. No duplication of functionality provided by Microsoft Pocket Outlook Object Model.
    2. Microsoft Windows Mobile MAPI functionality not duplicated.
  • Localization Requirements:
    1. Localized versions of an application do not need to be submitted for testing.
  • Notification Requirements:
    1. Notification system not duplicated.
  • Performance Requirements:
    1. Functionality and stability specific requirements.
    2. Application must pass the Hopper Test.
    3. Application must pass the Application Verifier Test.
  • Security Requirements:
    1. The application shall be free of viruses and malware.
    2. Applications submitted to the Marketplace will be code signed with a Marketplace certificate.
  • Shutdown Requirements:
    1. Applications must shut down gracefully.
    2. Clean-up when closing the application.
  • UI and Shell Support Requirements:
    1. User must initiate a Voice Call by choice or acknowledgement.
    2. 16x16 and 32x32 pixel icons for application and file types.
    3. Support for standard weight cursor
    4. Applications must maintain User Settings.
    5. User must initiate Data Download by choice or acknowledgement.
    6. Application title should be displayed on NavBar.
    7. Prohibited information on the NavBar.
    8. Display Soft Input Panel Button control only in prescribed locations.
    9. Applications must handle the input panel appearing and disappearing.
    10. Design applications to resize controls to fit the screen size.
    11. Applications should not have a Today Screen plug-in or component.
    12. Dialog Box controls must be stacked vertically.
    13. Back button performs Backspace in an Edit control.
    14. Spinner controls must be used if an application requires radio-button or drop-down list behavior.
    15. No information should be added to the Title Bar.
    16. Applications should not disable the Windows Error Reporting (WER) service.
  • Special Circumstances Requirements:
    1. Applications that use MFC classes must link statically to the MFC runtime.
    2. Support for Common Dialog Boxes.
    3. Support only one instance of each application or Control Panel.
    4. Input methods should be designed to a maximum of 80-pixels high and be docked on the device screen.
    5. Input methods must use Input Panel architecture.
    6. Device drivers must fulfill all relevant requirements for UI and SETK where applicable.
For detailed information on each of the aforementioned requirements, please click here. (link: https://developer.windowsmobile.com/resources/en-US/Application%20Submission%20Guidelines.pdf)
 
 
Rewards, Recognition and Fame MSDN - Subscribe Now Download IE8 - Win Prizes
MSDN Flash India Virtual TechDays MSDN Developer Resources
 
 
Terms of Use  |  Privacy Statement  |  Ask an Expert  |  Trademarks  |  Contact Us
© 2009 Microsoft