by brad
10. September 2010 08:00
Today’s Windows Phone 7 Development Tip comes from the official Windows Phone 7 Application Certification Requirements. If you are planning on having an application ready to go in October when the Marketplace opens, then you should definitely be familiar with all of the application policies.
Windows Phone 7 users a capabilities-driven security model in which each application must be up-front (to the marketplace and to the user) about the capabilities of the phone that it intends to use.
As of the Beta, the capabilities that an application can request to use are
- Networking (Including the Internet, of course)
- Location (Includes GPS)
- Microphone
- Media Library
- Gamer Services (XBOX Live)
- Phone Dialer (Starting phone calls)
- Push Notification (Alerts)
- Web Browser
When creating a Windows Phone application, the capabilities that your application is going to make use of are specified in your App Manifest file. When a user chooses to install your application they are told what capabilities your application will have access to.
Despite your responsibility to list all of the capabilities up-front, when your installation package (XAP) is repackaged during the certification process, your code will be analyzed and the capabilities that your application uses will be detected. These detected capabilities will then replace your originally declared list of capabilities.
The easiest thing to do then is just to list all capabilities up-front and leave it up to the certification analysis to detect the capabilities that you actually need. That being said, it’s always a good idea to be aware of the capabilities you will need rather than just leaving it to the Marketplace to figure out for you.
Other Resources
More Tips