Imagine the following use case:
- I developed an application which only requires "Self Signing". For this I use an allocated UID in the unprotected range, sign the app myself and distribute it through usual means (web, etc)
- Now either because I've added some new features (which require System Capabilities) or decided to publish through Ovi Store or whatever (ie. don't like the user getting the typical warning dialog shown in self signed apps) I'd need a new UID, given that "Express Signed" would require me to use an UID in the protected range. This would even apply should I decide to publish my app through Ovi Store (regardless the use or System Capabilities) from what I understand.
- Now for some reason I decide to offer the app through alternative channels besides Ovi Store. As I don't own the UID, I'd need to request a new one in order to "Express Sign" the application. A similar case would happen should my application require Restricted Capabilities (and thus Certified Signing, which Ovi Store currently doesn't support) even though this is a more special case, I admit.
How many UIDs changes have we had? I've lost count.
IMHO, this is completely unacceptable and unneeded. Specially now that Nokia literally owns Symbian (including Symbian Signed) I'd really expect a more flexible approach. I've been listening for months / years about changes and improvements, but have to say the current situation is far from ideal (and practical)
Let me stress that I completely understand Ovi keeping the signed file to themselves for the case they sign it (after all, they're "paying" for it), but I don't see why the developer wouldn't own the UIDs allocated to him. This would at least alleviate the pain to be switching UIDs here and there.
If you think switching UIDs is just changing a number, think better. It makes application updates completely unusable and in cases where the application stores data (in private folders for example) it forces the use of unorthodox techniques to save the user of this added hassle. Symbian already poses some "complications" just to add one like this..