Windows Marketplace for Mobile 'Certification Testing, Hopper, and Multiple Screen Support'

Failing Windows Marketplace for Mobile certification testing can be a frustrating experience, but it doesn’t have to be. Failing certification costs a submission credit (or another $99 if you’ve exhausted your initial five credits), you’ve to correct and resubmit your application – likely not what you planned. This post cover a few tips that should […]

Failing Windows Marketplace for Mobile certification testing can be a frustrating experience, but it doesn’t have to be. Failing certification costs a submission credit (or another $99 if you’ve exhausted your initial five credits), you’ve to correct and resubmit your application – likely not what you planned. This post cover a few tips that should help you increase the first time pass rate and have your app published to Marketplace sooner:

  1. Understand Certification Requirements: As Windows Marketplace for Mobile developer, you’re notified via email when Application Submission Requirements for Windows Marketplace for Mobile is updated. You can also check Windows Marketplace for Mobile forum for important announcements including availability of new requirements.
  2. Run Hopper early and often: From the requirements document: 1.17. Hopper Test
    Application must complete two hours of Microsoft’s Hopper test without exhibiting unpredictable behavior, hanging or crashing
    . Also Hopper has been updated to support Windows Mobile 6.5, correct version of Hopper can be downloaded here.
  3. Adapt Your App: From requirements document: 1.13. Multiple Device Support
    Developers must identify required device functionality during Windows Marketplace submission process. Apps must've ability to run on multiple WM device platforms, for e.g., multiple Standard or multiple Professional devices. Although not recommended, apps can support a limited number of WM devices
    . This requirement also includes proper handling of screen rotation. Just about every WMP device now supports dynamic rotation. Typically this’s triggered when sliding out an on-device keyboard or titling the device. The Adapt Your App section in WMD center is a great resource for information on how to ensure your app properly adapts to different screen orientations, sizes, and DPIs. When changing orientation the OS will send your app a size event. Make sure you’re taking action on this event: OnSize (if a managed) or WM_SIZE (for native code). For e.g., you may need to reposition some of your user interface elements. For a great in-depth article on this topic, check out: Adaptable Apps For Windows Mobile.

[Source]