You Are Here:

Community: Blogs

Who am I?

mopius

Thinking about what mobile phones can do except messaging and voice calls is one of my main interests. At the department of Mobile Computing at the University of Applied Sciences in Hagenberg (Austria), I can work on those ideas every day by collaborating with students, researching and - well - thinking.

 

Calendar

« April 2007 »
Mo Tu We Th Fr Sa Su
            1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
30            
 

Andreas Jakl's Forum Nokia Blog

Freeware Symbian Signed: 2 Months+?

mopius | 18 April, 2007 22:48

The Journey
New title screen of "The Journey" - now based on pure vector graphis.
Currently, I’m trying to release the S60 v3-port of the location based freeware game called “The Journey”. It uses the cell ids of the mobile phone network to determine the relative movement of the player, and connects this real-world information to the virtual gaming world of a small detective story.


Back in the days when the game was initially released, retrieving the cell id had been an undocumented feature. Meanwhile, the situation has changed and it’s possible to get the id through an official API. Unfortunately, accessing it requires Symbian Signed. So I decided to go through the Freeware Symbian Signed process.


Well, this was two months ago. If you go to the game website, you’ll see the game is still not released. This is not because the game has failed the tests. The reason is that I’m still waiting for the results.


I contacted the Symbian Signed-team twice. They told me that they can’t do much as the whole process is in the hands of Cellmania. So I decided to contact Cellmania, but never got a response…


Improvements


I think that it’s great that there is an opportunity to get freeware applications signed for free. However, in my opinion there are a number of things that have to be improved (well, in case this has not already happened lately):

  1. Improve the test criteria: It took me a very long time to go through the extensive test criteria document.  Especially time-consuming was the privacy dialog at the beginning, as it required a new .ini-file, a dialog, translated text, etc. It would be a lot easier if there was a reference implementation for something like that, along with the standard text translated to all major languages.

    To go even further, wouldn’t it be possible to make the criteria less strict for freeware applications, where some unpaid developer has to do everything himself? Are the privacy dialog, low memory startup, backup and restore, … really crucial to a small freeware app.?

  2. Improve the test criteria, part II: Even more time consuming has been figuring out that the backup process can’t be tested with a developer certificate. Also the AppTest Lite-tool didn’t recognize the incoming call and failed this test (along with a few similar ones).

    I had to search the internet to find “solutions” for those two common problems. As everyone will experience them, issues like that should be highlighted in the test criteria, instead of letting developers test the backup process over and over and read long documents - until they finally decide to consult some developer forums and discover that everything was correct in the first place.

  3. Improve the signing process: There should be immediate feedback that the application has been received and is starting to be processed. Then, there has to be a way to query the current status, along with a guaranteed maximum time, which should be shorter than two months :)

Summary

Screenshot of "The Journey"
"The Journey" lets you walk around in your real surroundings.
Developing mobile applications can be fun – as some of you might remember, I recently released HourPower, which was developed in just one day and was released the next, as it didn’t require Symbian Signed. Up to now, it has already been downloaded more than 1000 times, with many positive comments and not a single complaint. As I said, it's fun.


For “The Journey”, the story is different. In total, I spent a week working on Symbian Signed (eating up the limited free time). While this isn’t very motivating, the fun is now really gone when I already have to wait more than two months to be finally be able to release the otherwise 110% finished application. I don’t think the quality improved so much that all this is justified.


Please don’t understand this article as a criticism to Symbian Signed in general or the team working on it at Symbian. They’re doing a great job and are quick and helpful with their responses. However, the good idea of the Freeware Symbian Signed process has to be taken further and improved in many areas.


It might also be possible that I just had bad luck. I’d be very interesting in comments from other developers who have already gotten their freeware applications Symbian Signed – or are still waiting for it.

RSSComments

Re: Freeware Symbian Signed: 2 Months+?

antonypr | 18/04/2007, 23:39

antonypr Good point. I have similar experience with Symbian Signed too. I have written an open letter to Symbian quite some time ago, http://mobile.antonypranata.com/2007/03/18/an-open-letter-to-symbian-signed-authority/.

One more thing, if you want, you can distribute your game unsigned. Then ask your users to sign it themselves. It is a bit of work for the end users, but it's better than waiting for Symbian Signed and you have nothing.

There have been some freeware developers do it this way, including myself. You can check it out at http://mobile.antonypranata.com/2007/03/18/why-do-we-need-symbian-signed/.

Re: Freeware Symbian Signed: 2 Months+?

mopius | 19/04/2007, 00:04

mopius Thanks for the link! It's great - well, not great, but interesting - to know that others have the same problems with Symbian Signed. The suggestions you made are very thoughtful and true and would certainly make everything a lot easier!

I guess the best thing would be if someone from Symbian / Nokia / UIQ officially collects all those suggestions from your article, this one and the others that may exist. Then, every single one should be rated according to the real-world practibility. And finally, the best ones have to be put into practice.

About distributing the game unsigned: It's not what I'd like to do. The point of the game is that it's simple to use and that it provides location based gameplay without complicated or expensive equipment / setup. If the user would have to sign the downloaded game himself, this would ruin the whole experience. It's true that it's better than nothing, but I fear it's far too complicated for the average user. Well, at least I wouldn't do it if I put myself in the role of a potential user :) But I'll certainly release it that way it if nothing changes anytime soon...

Re: Freeware Symbian Signed: 2 Months+?

ptrmn | 20/04/2007, 14:03

I absolutely agree about letting the user sign the SIS file. It's too much hassle. I couldn't be bothered to do it unless I _really_ wanted to use an app, and I know all this signing stuff inside out. Already downloading and installing a SIS file seems too complicated to many users.

Re: Freeware Symbian Signed: 2 Months+?

coultonp | 19/04/2007, 10:53

coultonp Andreas

First of all nice to see you have done an update of the journey and I will be interested in trying it so I hope you get your problems resolved soon . Speaking as an academic who likes to test applications in the real world I also have issues about the v9 signing regime which IMHO does restrict my ability to perform this type of innovative research.

Re: Freeware Symbian Signed: 2 Months+?

mopius | 23/04/2007, 01:11

mopius Great to hear that you're looking forward to the re-release of the game! While the game will still be a proof-of-concept project instead of a real game, it will look a lot better with the new graphics.

And that's true, applications like that are the typical academic research project ("The Journey" was originally also developed for my Bachelor's Thesis). For this, certificates are making the life a lot more difficult...

This can even be said in a more general manner: an hour ago, I just wanted to download an official skin for the OggPlay-application. It didn't install as the certificate was already expired. Well, I don't really see the reason. Is there any advantage for the users, the operators or developers if the certificates expire after half a year? It just makes everyone annoyed. I guess there are a lot of things that might have their reasons, but those are not really obvious to the standard user or developer...
You must login to post comments. Login
 

Rate This

 
 
Bookmark this page: DeliciousDiggFacebookGoogleYahooStumbleUponRedditDiigoTechnocratiTwitter  Share this page Share this page Print this Page Print this page Invite a friend Invite a friend
京ICP备05048969号    Email Newsletters Press Terms & Conditions Privacy Policy Sitemap Contact Us © 2009 Nokia 
RDF Facets: qdcZdescriptionQSxAsE20anE20AssistantE20ProfessorE2cE20IE27mE20teachingE20SymbianE20OSE20atE20theE20UniversityE20ofE20AppliedE20SciencesE20inE20HagenbergE2cE20AustriaE2eE20MyE20companyE20E22MopiusE22E20isE20developingE20mobileE20softwareE20withE20aE20specialE20focusE20onE20SymbianE20OSE2eE20mopiusE20E7cE2018E20AprilE2cE202007E2022E3a48E20NewE20titleE20screenE20ofE20E22TheE20JourneyE22E20E2dE20nowE20basedE20onE20pureE20vectorE20graphisE2eCurrentlyE2cE20IE92mE20tryingE20toE20releaseE20theE20S60E20v3E2dportE20ofE20theE20locationE20basedE20freewareE20gameE20calledE20E93TheE20JourneyE94E2eE20ItE20usesE20theE20cellE20idsE20ofE20theE20mobileE20phoneE20networkE20toE20determE2eE2eE2eX qdcZidentifierQSxhttpE3aE2fE2fblogsE2eforumE2enokiaE2ecomE2fblogE2fandreasE2djaklsE2dforumE2dnokiaE2dblogE2f2007E2f04E2f18E2ffreewareE2dsymbianE2dsignedE2d2E2dmonthsX qdcZpublisherQUxhttpE3aE2fE2fswE2enokiaE2ecomE2fidE2fc764fd1cE2d8b06E2d499aE2d9a6aE2d17c3903d5a65E2fforumE5fnokiaE5fcrawlerE5fagentX qdcZtitleQSxAndreasE20JaklE27sE20ForumE20NokiaE20BlogE20E7cE20FreewareE20SymbianE20SignedE3aE202E20MonthsE2bE3fX qdcZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qdcZtypeQUqfntypeZBlogContentQ qdcZtypeQUqfntypeZBlogE45ntryQ qdcZtypeQUqfntypeZCommunityContentQ qdcZtypeQUqfntypeZE52esourceQ qdcZtypeQUqfntypeZWebpageQ qdcZtypeQUqmarsZManagedE52esourceQ qdcZtypeQUqwebZInformationE52esourceQ qdcZtypeQUqwebZPageQ qdcZtypeQUqwebZE52esourceQ qdcZtypeQUqrdfsZE52esourceQ qrssZdescriptionQSxAsE20anE20AssistantE20ProfessorE2cE20IE27mE20teachingE20SymbianE20OSE20atE20theE20UniversityE20ofE20AppliedE20SciencesE20inE20HagenbergE2cE20AustriaE2eE20MyE20companyE20E22MopiusE22E20isE20developingE20mobileE20softwareE20withE20aE20specialE20focusE20onE20SymbianE20OSE2eE20mopiusE20E7cE2018E20AprilE2cE202007E2022E3a48E20NewE20titleE20screenE20ofE20E22TheE20JourneyE22E20E2dE20nowE20basedE20onE20pureE20vectorE20graphisE2eCurrentlyE2cE20IE92mE20tryingE20toE20releaseE20theE20S60E20v3E2dportE20ofE20theE20locationE20basedE20freewareE20gameE20calledE20E93TheE20JourneyE94E2eE20ItE20usesE20theE20cellE20idsE20ofE20theE20mobileE20phoneE20networkE20toE20determE2eE2eE2eX qfnZdistributionQUxhttpE3aE2fE2fblogsE2eforumE2enokiaE2ecomE2fX qfnZtopicQUxhttpE3aE2fE2fswE2enokiaE2ecomE2fFNE2d1E2fBlogTopicE2fgeneralXRqdcZtypeQUqrdfsZE52esourceQRqmarsZrelevanceQNx100X qfnZtopicQUqfnTopicZtestingQRqdcZtypeQUqrdfsZE52esourceQRqmarsZrelevanceQNx100X qfnZtypeQUqfntypeZBlogContentQ qfnZtypeQUqfntypeZBlogE45ntryQ qfnZtypeQUqfntypeZCommunityContentQ qfnZtypeQUqfntypeZE52esourceQ qfnZtypeQUqfntypeZWebpageQ qfnZupdatedQDx2007E2d04E2d22X qfnZuserE5ftagQSxtestingX qmarsZdescriptionQSxAsE20anE20AssistantE20ProfessorE2cE20IE27mE20teachingE20SymbianE20OSE20atE20theE20UniversityE20ofE20AppliedE20SciencesE20inE20HagenbergE2cE20AustriaE2eE20MyE20companyE20E22MopiusE22E20isE20developingE20mobileE20softwareE20withE20aE20specialE20focusE20onE20SymbianE20OSE2eE20mopiusE20E7cE2018E20AprilE2cE202007E2022E3a48E20NewE20titleE20screenE20ofE20E22TheE20JourneyE22E20E2dE20nowE20basedE20onE20pureE20vectorE20graphisE2eCurrentlyE2cE20IE92mE20tryingE20toE20releaseE20theE20S60E20v3E2dportE20ofE20theE20locationE20basedE20freewareE20gameE20calledE20E93TheE20JourneyE94E2eE20ItE20usesE20theE20cellE20idsE20ofE20theE20mobileE20phoneE20networkE20toE20determE2eE2eE2eX qmarsZlanguageQUxhttpE3aE2fE2fswE2enokiaE2ecomE2flanguageE2d1E2fenX qrdfZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qrdfZtypeQUqfntypeZBlogContentQ qrdfZtypeQUqfntypeZBlogE45ntryQ qrdfZtypeQUqfntypeZCommunityContentQ qrdfZtypeQUqfntypeZE52esourceQ qrdfZtypeQUqfntypeZWebpageQ qrdfZtypeQUqmarsZManagedE52esourceQ qrdfZtypeQUqwebZInformationE52esourceQ qrdfZtypeQUqwebZPageQ qrdfZtypeQUqwebZE52esourceQ qrdfZtypeQUqrdfsZE52esourceQ