Linked by Thom Holwerda on Sun 19th Jun 2011 18:26 UTC
Windows Way back in old and boring January of this year, Microsoft announced they would be working together with the Windows Phone 7 homebrew community, with the goal of creating a stable, supported way for homebrew developers and people interested in homebrew applications to enable side-loading on their WP7 devices. Well, they took their sweet time, but the ChevronWP7 team (Rafael Rivera, Chris Walsh, and Long Zheng) and Microsoft have just announced the results.
Permalink for comment 477780
To read all comments associated with this story, please click here.
RE: Hmmm...
by Neolander on Sun 19th Jun 2011 19:51 UTC in reply to "Hmmm..."
Member since:

Or better, for an individual description of each flavour of Symbian Signed :

***Open Signed Online****...

Free of charge, not for commercial use. Application is signed by Nokia for use on one single phone, then put online for 30 days and kept usable for 3 years. Access to relatively "sensitive" capabilities (power management, system settings alteration).

***Open Signed Offline***

Only for corporate developers. Requires a special certificate costing $200/year. Access to even more sensitive capabilities (direct communication with device drivers essentially). Deployment on up to 1000 devices, with the same 3-year validity limit as before. The application is still checked and certified by Nokia before signing.

***Express signed***

Only for corporate devs. Require the aforementioned certificate, plus a $10 token per signed application. Allows devs to sign their applications themselves (although they are still subject to random audit by Nokia). Applications are freely deployed, and their certificates have a 10-year validity limit. Access to same capabilities as Signed Online.

***Certified Signed****~@...

Similar to before, but the token costs $150 and applications must be submitted to some sort of VIP signing service that's trusted by Nokia (Sogeti HT). Applications may get full access to the device, although some capabilities require agreement with device manufacturers (ex : accessing the unprotected version of DRMd content, altering application's security capabilities and other system files).

Reply Parent Score: 1