At the time of writing, ideas.symbian.org contains 203 ideas. The site has been awaiting a facelift for several months, and its present appearance can be a bit intimidating. But don’t let that put you off – it contains plenty of interesting ideas, ranging through curious and clever to challenging and courageous.
If you like one of these ideas, please vote for it. (You can vote for as many different ideas as you like.) If you dislike it, you can vote against it – and please leave a comment, telling us why. You can jump into a discussion on any of the ideas, or raise an idea of your own, for community review.
(You can read the ideas and the associated discussion without logging into the site. If you want to participate more actively, you’ll need a login. Email me at davidw AT symbian DOT org, and I’ll ensure an invite comes your way. For more details of the intended operation of the site, see my previous article, “Looking for producers“).
Here are extracts from a few ideas you might enjoy browsing:
Multimedia Playability Database – posted by Martin Webb:
I’m sure many of you will have experienced the problems of playing multimedia on phones – much of your content won’t play, even though the phone apparently supports the format you are trying to use.
There are many reasons for this – e.g. bit rates for even SD content are too high for phones. However, another key issue is that testing multimedia content is hard – you can test multimedia , demuxers etc individually to death, and still have problems, due to the way things work at a system level (e.g. a bad encoding – not the phone’s fault, but still disappointing for the user and not an excuse with service providers).
The solution is to test with as much content as possible, but this takes time. Fortunately, this problem seems ideal for a collaborative community, and so I propose a playability database…
Choose appropriate licensing to better account for closed-source additions – posted by Ajay:
I congratulate the Symbian Foundation for choosing a weak copyleft license with the EPL, that doesn’t enforce open source on all authors of future modules that might be added to the Symbian platform. However, there are two problems with this choice that I’d like to see addressed: the EPL is not very well-written in this regard and there are possible licensing conceptions that might better enable closed-source additions. I will address each in turn…
Idea for a Sharing Application for S60 & Symbian Browsers – “Echo” – posted by Micky Aldridge:
Similar to the already familiar full sized web-based sharing extensions, such as ShareThis, Feedly, and ShareAholic, its high time that we had a mobile version for our S60, and Symbian Internet browsers, something very discrete, and simple to use to share any site’s url, with a comment, posting to one of several options, be it Twitter, Google Reader, Facebook, or email.
Basically, the already built-in Share URL, which is available by selecting the three horizontal lines in the right hand side menu whilst browsing, has potential, but it simply does not do enough. For example, the options are “Via message”, Via Bluetooth”, and Via Share on Ovi”. None of these do what people want…
Promotion of a Symbian applications prototyping solution – posted by Constantine Michailidis:
Making a worthy, useful mobile application with a potential to become a [commercial] success can be very difficult. As you may already know by the desktop environment, much is decided before you even start typing your code: while designing the application, its UI, its features as requested by the client, or simply by implementing the idea you had in mind. All these things have to come out perfect if maximum usability is what you are after.
I wanted to ask here: does Symbian Foundation have any official or semi-official program to help with the “design phase” of application development? Yes, I mean the initial one, while you design (maybe with pen-and-paper) the various screens and controls the application will show…
Healthcare application – posted by Suyog Vaidya:
I am starting this thread to discuss a potential application.
The application proposed is a mechanism to detect undue periods of inactivity of users (elderly or infirm) which might indicate an emergency. The app is provisioned with user specific information including the period of inactivity which might indicate an emergency.
On crossing of various thresholds, the app will throw up interaction dialogs which when attended to shall, in effect, reset the monitoring intervals. Simple movement of the device shall also reset the interval…
Adding More and Versatile Calendar Views – posted by Antoine RJ Wright:
Something that I wish were in the built-in calendar was this idea of additional views. Right now, we have day, week, and month views, but that should not be all the information, or presentation of information that we see.
One view that would come in handy is a call log view. In this view I would see a daily, weekly, montly log of calls, except it would be overlaid to my calendar so that I could do additional things with that information – make notes, send proof to others, etc.
Another view that would be suitable is the ability within the calendar to see all messages as they came in or were sent out. Again, this messages view would be overlaid to those traditional views, but it would give an alternate look to the data that we already want to manage and see…
Audible “call progress” information – posted by William Roberts:
I would like to have an audible indication of why a call has failed, preferrably a spoken one, so that I don’t miss the dialogue box which is displayed while I have the phone pressed to my ear, wondering what’s happening.
Whether you like these ideas or hate them – or whether you think you have better ideas that are worth sharing – your input will be welcome!

