Antony’s Mobile Blog

Finally… after being stuck in the Symbian Signed for around 5 weeks, Screenshot for Symbian OS (S60 3rd) version 2.60 is released. What’s new in this version?

• New icon. The icon looks like the picture on the right side. Thanks to Pietro Paschino who has kindly designed this new icon for us.
• Support backup/restore. Unfortunately, this feature does not work properly yet. The picture, which is supposed to be displayed on the main window, is not restored at all.
  You may ask, didn’t I test backup/restore feature before submitting it to Symbian OS. The answer is no, I didn’t test it. Why? Because there is a bug in the current Symbian OS version that we cannot test backup/restore using developer certificate.

Click here to download Screenshot for Symbian OS (S60 3rd) version 2.60.

I would like also to remind you that Screenshot for Symbian OS version 2.70 is already available on SourceForge.net. There are several versions available, i.e. S60 1st/2nd, S60 3rd and UIQ 2. The complete source code is also available there. Note that the version for S60 3rd Edition is unsigned. I need a couple of weeks to get sign it via Symbian Signed.

Dear Symbian Signed Authority,

I am writing this letter on my position as an independent developer for Symbian OS 9.1. Everything I write in this letter is purely my personal opinion and view. It is not related to the employer where I am currently working. The purpose of this letter is to explain the current situation of Symbian Signed route for freeware applications and provides some suggestions.

First of all, I am a developer of Screenshot for Symbian OS, an open source application to capture screenshots on Symbian OS platform, including S60 1st/2nd Edition, S60 3rd Edition and UIQ 2 devices. The version for S60 3rd is signed by CellMania via special route for freeware applications. In fact, it is one of the first applications for Symbian OS 9.1 that went through this special route.

After doing signing via the process for several times, I have identified several things that slow down development process for freeware applications. I have three suggestions to improve the whole process.

1) Improve waiting time of the signing process

The current waiting time of the Symbian Signed process is too long. According to the official documentation from Forum Nokia, the signing process should take around 2 weeks. Unfortunately, this doesn’t happen in reality. As an example, I have submitted Screenshot for Symbian OS version 2.60 on February 12, 2007, but I haven’t heard anything until today (March 18, 2007). It has been 5 weeks!

This experience has happened to other freeware developers too. Here is one posting on Symbian discussion groups:

On December 23, 2006 I submitted my freeware application (PhoNetInfo) on Symbiansigned.com.
Now after nearly two months and a fistful of email to symbiansigned.com I still don’t have any information about the status of my application…

Here is another posting on Forum Nokia discussion board:

Symbiansigned.com is really annoying!!!!!! I submitted a freeware application on December 25, 2006. And… I still have no information about the status of my application… even not in my Symbiansigned-account. The support only told my to wait a “little bit”. That’s really not normal. They slow-down the whole development process!!!

I know that Symbian has to invest a lot of money to support signing process for freeware applications. As freeware developers, we don’t pay anything to Symbian Signed. However, please remember that the freeware and open source communities indirectly help the platform to be success.

2) Allow more than 1 IMEI for developers without ACS Publisher ID

The current policy says that freeware developers without valid ACS Publisher ID can request a certificate for 1 IMEI at a time. In order to apply for more IMEIs, we need ACS Publiser ID. The cost of getting ACS Publisher ID itself is around US$ 400 (currently Verisign offers a discount at US$ 350). That amount of money is much for many freeware developers.

I don’t know the reason why developers without ACS Publisher ID can only request for 1 IMEI only. This just makes certificate management is time-consuming for us.

Normally, we have several beta testers for our applications. For each beta besters, we have to submit a new request for certificate. As an example, Screenshot for Symbian OS has been translated into more than 30 languages. Normally, the translator would like to test the localized version on his/her device(s). It means I have to request for new certificate for each of them.

3) Better signing process for updates and bug fix releases

There should be a better policy for handling updates and bug fix releases. Here is the strange clause from Symbian Signed’s FAQ.

As a guideline you should not submit updated versions more frequently than once every quarter. This helps create a manageable number of applications to test and gives the entire community a chance at equal treatment.

Why should we wait for 3 months to submit an update? What should we do if we want to fix a critical updates? What would happen if someone would like to translate the application into another language?

As summary, the current process of Symbian Signed for freeware and open source developers make our life very difficult. As an independent developer, I would like to see Symbian OS to be a success platform. I call upon you to take actions as soon as possible.

Best regards,

Antony Pranata

I notice that there are some freeware applications for Symbian OS 9.1 that are now distributed as unsigned SIS files. For example:

• ActiveFile - a free file manager for S60 3rd Edition.
• GNUBox - an application that allows you to use PC’s Internet connection from your phone.
• TaskSpy - a task manager for S60 3rd Edition.
• Screenshot - a screenshot capturing application (this application is developed by me).

Why do the developers release unsigned applications? I think the biggest reason is because Symbian Signed Authority normally needs a couple of weeks (and sometimes months) to sign an application. Although they said on their web site that signing for freeware applications should take 2 - 3 weeks, this will not happen in most of the cases. It had made frustration to many of freeware developers.

How do the users install unsigned applications then? There are some people who have provided step-by-step instructions how to sign them ourselves. Basically, a user who wants to sign an unsigned application has to register with Symbian Signed and then download a certificate/key pair for his/her phone.

If everyone can sign any applications using their own certificates, why do we need Symbian Signed at the first place? What is the point of having signing if the users can sign applications themselves? It just creates extra steps for the users and makes developers’ life more difficult.