Read-only archive of the All About Symbian forum (2001–2013) · About this archive

Symbian Foundation looking for comments on new Symbian Signed criteria

8 replies · 2,752 views · Started 03 August 2009

The Symbian Foundation have asked for input from Developers and interested parties on the newly drafted Test Criteria for Symbian Signed. The new criteria, v4.0.8, are still in draft (and developers should continue to follow the existing v3.0.3 criteria until told otherwise), but the Foundation "...believe that it's important to get as many eyes on this as possible as soon as we can."

Read on in the full article.

what he said ^ symbian signed should be destroyed. There are so many amazing apps out there that aren't signed (scummvm/quake3 etc), and kick ass.

get rid of symbian signed.

Help me understand symbian signed. I dont get the point of it. Currently i get so many prompts when installing an app its insane. And even just opening and connecting with a web runtime app yields 5 prompts. So i ask, what in god's green earth is the point of symbian signed? Just get rid of it already.

I can understand why manufacturers would want a signing process (especially with the publicity brought by Apple's justification for not allowing the 'jailbreaking' of iPhones, which equally applies to all mobile phones), however to the user and it seems from comments, to developers, the signing process is just a nuisance. Personally, I want to be the sole decider in what gets installed on my device.

It must be easier for developers and/or end users to 'self-sign' apps.

As an earlier poster said, a bunch of prompts EVERY time you use an app or a WRT-based widget is madness.

SymbianSigned as it currently exists is a set of reasonable requirements for all apps to conform to, and a couple of ludicrous ones. Demoting it from an expensive paid-for process (mandatory for anything involving networking, which, on a "smart" platform, should be more common but isn't due to the aforementioned expense), to an optional process that gets you more notice/higher profile when selling your app, and keeping the requirements as they stand for use as *recommendations* for common UI and behaviour for all apps, would be much more sensible.