Hi Lusipher,
the whole point of this poll was to determine if we should release a self-signed version of the Reader or not. The problem is that we have to use some APIs that require capabilities and that therefore absolutely require Symbian Signing to work. So, a self-signed version of the Reader would do the basics but would have the following limitations:
- eBooks that are DRM encrypted (purchased books) won't open at all
- OS integration with the MIME type recognizer will not work (opening Mobipocket files in the File Manager will not work, downloading Mobipocket files from the browser will not open them, Mobipocket files in messages (attachments or beamed files) cannot be opened...)
- the "send" feature in the Reader will be missing
Just a note for everyone following this thread:
the Symbian Signed process is not new to Symbian 9 (Series 60 3rd / UIQ 3), it was introduced a while ago. What's new is that:
- Symbian 9 introduces "capabilities". Some of the OS APIs require one or several capabilities to be used by an application. Applications that require capabilities need to be signed to run on a Symbian 9 device.
https://www.symbiansigned.com/How_has_Symbian_Signed_evolved_with_Symbian_OS_v9.pdf
- on Symbian 9 there are ranges for protected UIDs and unprotected UIDs. Application that have a protected UID need to be signed to be installed on a Symbian 9 device.
https://www.symbiansigned.com/app/page/uidfaq
Before Symbian 9, any application could be delivered unsigned, the user simply had to confirm after a warning message was displayed during the installation process.
Best regards,
Fabien