Symbian: Moving Towards Openess
I’ve been going to Symbian smartphone shows now since the Developer Expo in 2000 in the conference hall of the Hilton London Metropole, so I have a good perspective on how Symbian has evolved since then.
The first Symbian Exchange & Exposition a couple of months ago confirmed that Symbian is an organization in transition. You knew that, right?
More importantly, it revealed the direction and pace of that transition. So, what’s coming, and is it good or bad for customers and partners? Let’s start big picture and drill down.
Transitioning
Symbian is transitioning from a closed club model to an open model. Why say “closed club” rather than “proprietary”? Symbian has always had multiple stakeholders, all of whom exerted influence on the direction of the product. Now the range of stakeholders has dramatically increased.
This is very different to the Apple, Microsoft, RIM, or even Google model, where one organization “reads” the market and drives the product in the direction they believe it should go. Don’t be confused by Android’s open source status – Google is the indisputable lead in that project and open source is an after-the-fact reality. (A simple way to put it is “Google writes it, everyone reads it; Symbian allows everyone to write and read.”)
This transition from closed to open is occurring at many levels, and the expo introduced several, such as:
- The Ideas process
- The Horizon application publishing framework
- The Beagle Board and OMAP Zoom debug hardware.
These introductions help end users because the Symbian Foundation is now:
- Open to new ideas via an open, rapid, practical requirements elicitation process in ideas.symbian.org
- Open to all applications and app stores via horizon.symbian.org

- Open to all ISVs (the guys that make the “smart” in smartphone) via open/cheap source combined with cheap debug hardware via beagleboard.org
and omapzoom.org
Let’s look at each of these points and see how they help end users of Symbian phones.
Ideas
The Ideas process introduces a completely open requirements elicitation process, allowing Symbian to hear directly from the end user and not just their closed club of traditional customers (device manufacturers and operators). This speeds improvement of the UI and features of your smartphone.
Horizon
The Horizon application publishing framework reduces barriers to market for ISVs and supports a wide range of app stores (allowing improved service and specialization) while maintaining a single point of distribution for the ISVs. This encourages a healthy diversity of third party applications for your smartphone.
Debug Hardware
Cheap debug hardware and software allows ISVs to develop for future versions of the platform well before they’re commercially available. This allows the development of well designed and integrated, cutting edge applications available right from the release of your new smartphone.
Symbian in Transition
These are all signs of the direction Symbian is heading in. But it still has a long way to go:
- the source base is not all open sourced yet
- Nokia is defining the next generation UI almost entirely in-house
- most development effort is still sourced within Nokia
- other factors are still keeping parts of the platform less open than they could be.
However, it is clear that Nokia values the idea of community participation, it is clear that the Foundation understands something of how to achieve this, and it is clear that the platform has the strength and potential to really benefit from this.
The key is for all of us to ensure that these benefits flow through to the end user (you) as quickly as possible.

Insight 8
