Symbian to be another open mobile platform
The already crowded open source mobile phone software market just got more so as Nokia has announced plans to open up the Symbian operating system. Symbian currently has the biggest installed base of any mobile OS, which makes this announcement somewhat more surprising—market leaders generally do not radically change their successful methods. What it means for the various Linux mobile phone initiatives is unclear, but it certainly shakes things up a bit.
Nokia, along with many of the biggest players in the mobile phone market, has formed the Symbian Foundation to provide its members with the OS on a royalty-free basis. Several other components are being donated to the foundation as well, to create a complete platform for mobile applications. The plan is for all of the code to be released using the Eclipse Public License over the next two years.
In order to own the code, Nokia is purchasing the 52% of Symbian Limited that it does not currently own for more than $400 million. This will allow Nokia to donate Symbian, along with its S60 smartphone platform, which runs atop Symbian, to the foundation. Sony Ericsson and Motorola will donate their UIQ user interface layer, while NTT DoCoMo will donate its Mobile Oriented Application Platform (MOAP).
Nearly two dozen companies have come together to form the foundation, including handset makers, mobile carriers, and chip manufacturers. Interestingly, there is substantial overlap between Symbian Foundation members and those of the Open Handset Alliance—the umbrella organization for Google's Android effort—and the LiMo Foundation. Whether this reflects impatience with the pace of Android/LiMo development or just an effort to hedge their bets remains to be seen.
Membership in the foundation is open to all who are willing to pay the $1500 annual membership fee. That fee will allow the use of all of the components that make up the Symbian platform on a royalty-free basis. Any developers that wish to create software for the platform need not join as there will be a developer program available at no charge. The foundation is expected to start operations in 2009.
Opening up Symbian is seen as a reaction to Android and other free software efforts in the mobile phone space. One of the advantages touted for Linux solutions is the zero cost—particularly the lack of per-unit royalties. By moving Symbian to this model, the foundation undercuts that advantage. Because Symbian is already a dominant player in the smartphone market—with a large development community—there are some who believe it will redirect efforts currently focused on Linux to Symbian.
That remains to be seen, of course, but Linux-based smartphones are still in their infancy. MontaVista's Mobilinux has been installed in more than 35 million mobile devices, mostly in Asian markets, but, perhaps because of it being controlled by a single company, hasn't really generated a large developer community. It may also be targeting mobile carriers who are not very interested in allowing users to customize their phones—at least not to the extent Android and others envision.
There is a widening rift between the "free" and "locked down" camps for mobile devices. With this move, Nokia—and the other foundation members—seem to be moving toward allowing users more freedom, though undoubtedly some handset makers and carriers will opt for locking down their phones regardless of the openness of the underlying OS. One need look no further than the iPhone for an example of a tightly controlled application environment that is, at least so far, very popular with consumers.
In the long run, it is hard to imagine that mobile device users will be willing to stick with the limited choices of applications provided by their carrier or phone maker. As more open alternatives become available, there will be a pushback from handset buyers that will be harder for the carriers to resist. For many, their mobile phone is the most sophisticated computer they own and the history of personal computers would indicate that a thriving ecosystem of the third-party applications is an important part of the purchasing decision. That requires developers.
The current proliferation of open mobile phone software platforms is, in many ways, a battle for developer mindshare. LiMo, Android, and OpenMoko are all Linux-based development platforms that support multiple hardware devices, which should allow applications to run on many different mobile devices with minimal porting. How well that works in practice is still an open question.
For many of the established players in the mobile device market, Symbian is a known quantity. It has shipped on countless devices—its strengths and weaknesses are well understood. Turning it into a free software release will allow, at least potentially, members to move the Symbian code in the direction they want. But will that stop, or substantially slow down, the adoption of Linux-based solutions?
In order for that to happen, Symbian itself will need some kind of developer community, something like what currently exists for the kernel and user space applications on Linux. Whether the opening of the code will be enough to attract that community is an open question. It may be that developers at the member companies will be forced to form that community—something that could affect the bottom line.
One of the key problems that the various Linux-based efforts face is that of fragmentation. The vendors of royalty-based mobile platforms—primarily Microsoft and Palm—tend to point to the multiple incompatible Linux efforts as proof. They tout the control that a single vendor provides to ensure compatibility. Others, like Apple and RIM (maker of Blackberry email phones), do not license their software to others so they tightly control the hardware, which tends to avoid fragmentation.
Within a particular initiative, fragmentation is likely to be a very bad thing, but having multiple platform choices tends to provide healthy competition and thus help consumers. Over time, some of the current Linux-based platforms may fall by the wayside to leave fewer choices, but that will likely happen due to technical considerations, part of which will be determined by the third-party application developers.
One questions remains though: what happens with Qt, or more specifically the Qtopia Phone Edition? Nokia bought Trolltech early this year, at least partially for their mobile toolkit. Will they port it to Symbian and donate it to the foundation? They could, of course, port it but keep it separate, but that would seem to lead down the path toward fragmentation. It seems somewhat unlikely that they would change Trolltech's successful hybrid of GPL and commercial licenses, but before this announcement few thought that Symbian would be freed. Nokia has certainly adopted a more open-friendly stance of late—they clearly see it as a way to generate more business—so it certainly is not out of the realm of possibility.
While opening up Symbian may inhibit Linux adoption on mobile devices, it can only be seen as a good thing for consumers and the free software community as a whole. In many ways, it validates the free software development model along with the idea of freedom for users and developers. The competition between Linux and Symbian will also likely help both improve. Expect lots of interesting devices and applications in the next few years because of it.
Posted Jun 25, 2008 19:47 UTC (Wed)
by osma (subscriber, #6912)
[Link] (4 responses)
Posted Jun 25, 2008 20:53 UTC (Wed)
by roelofs (guest, #2599)
[Link] (1 responses)
I wondered the same thing, including whether it was a two-year-only restriction. But another possibility is that they plan to keep a fairly tight hold on the official version (i.e., more cathedral than bazaar), in which case the $1500 might buy you early/behind-the-scenes access to upcoming snapshots. I haven't followed Nokia's existing open-source efforts very closely, so I don't know if that's likely or not. But in my experience, embedded software development tends to be somewhat more controlled/constrained than software development in other areas is.
Greg
Posted Jun 25, 2008 21:08 UTC (Wed)
by Jonno (subscriber, #49613)
[Link]
Posted Jun 26, 2008 21:25 UTC (Thu)
by fredrik (subscriber, #232)
[Link] (1 responses)
Posted Jun 28, 2008 9:10 UTC (Sat)
by henning (guest, #13406)
[Link]
Posted Jun 25, 2008 22:53 UTC (Wed)
by aleXXX (subscriber, #2742)
[Link] (9 responses)
Posted Jun 26, 2008 5:02 UTC (Thu)
by kripkenstein (guest, #43281)
[Link] (8 responses)
Posted Jun 26, 2008 9:49 UTC (Thu)
by liljencrantz (guest, #28458)
[Link] (7 responses)
Posted Jun 26, 2008 9:56 UTC (Thu)
by kripkenstein (guest, #43281)
[Link] (6 responses)
Posted Jun 26, 2008 10:02 UTC (Thu)
by tajyrink (subscriber, #2750)
[Link]
Posted Jun 26, 2008 10:49 UTC (Thu)
by alex (subscriber, #1355)
[Link] (1 responses)
Posted Jun 26, 2008 13:10 UTC (Thu)
by rfunk (subscriber, #4054)
[Link]
Posted Jun 26, 2008 11:16 UTC (Thu)
by liljencrantz (guest, #28458)
[Link] (1 responses)
Posted Jun 26, 2008 12:35 UTC (Thu)
by mjw (subscriber, #16740)
[Link]
Also you could see it as the example that the java liberation is basically done now (Indeed through the help of the free software community at large): Java is finally Free and Open
Posted Jun 27, 2008 2:53 UTC (Fri)
by robilad (guest, #27163)
[Link]
Royalties for free software?
Thanks a lot for the excellent - and extremely timely - article. Just one question, which
baffled me when I saw this in the morning newspaper as well:
If all of the software is going to be published under an open license (Eclipse), what does the
$1500 membership payment pay for? You state (just like the newspaper) that it allows for
royalty-free use of the platform, but why is this necessary, if the code is as open as
claimed?
Are there patents that must be licensed in addition to the code?
Is this a temporary arrangement for the next two years, during which not all of the code will
be released under the open license?
Or is there still some closed code which forms an essential part of the Symbian platform?
Of course, $1500 per year is probably peanuts for any company that sells mobile phones.
However, there could be other interesting uses of the platform beyond phones, for example
projects like OpenMoko or future "learning devices" similar to OLPC XO-2 or Nintendo DS, for
which the initial fee could be an issue. Not that Linux wouldn't be a good choice, but having
other open alternatives is always nice.
If all of the software is going to be published under an open license (Eclipse), what does the $1500 membership payment pay for?
Royalties for free software?
Royalties for free software?
My, purely speculative, thought is that it would give you the right to
use "Symbian", rather than your own operating system built from Symbian
sources.
That is, you pay for the brand name and associated compability guarantee.
Similar to how (most) Java source code now is open source, but you still
need a license to offer a "Java" solution.
Royalties for free software?
Another possibility is that the Symbian Foundation membership gives you voting rights in some
form of ruling board the foundation will establish.
I'd imagine that even though it is open source, a such a huge and complex code base will be
maintained by a cathedral - mainly in the form of nokia employees - taking development
directions from the foundation. At least for the nearest couple of years.
As far as I have understood the EPL, it contains a patent retailiation clause, and requires
that you license patents for the code you release under it. So I do not believe the membership
fee has anything to do with patent licensing.
Take a look at the symbian foundation whitepaper PDF
(p6), the anual membership fee will buy you some voting rights and also
the possibility to distribute the code commercially. This will be
probably not possible as part of the free developer program.
Royalties for free software?
Symbian to be another open mobile platform
Would it be actually a "problem" if freeing Symbian slows down Linux
adoption on mobile phones ?
I mean, by then it would actually mean that one free OS (Symbian) would
be preferred over another free OS (Linux). I.e. both are free, and I
think my goal is to have more free software available, not specifically
having more marketshare for one specific free software (except the ones
I'm working on myself).
Alex
Symbian to be another open mobile platform
Well, Linux is free now while Symbian will be freed 'over the next 2 years' - which might
happen, or it might not.
Symbian to be another open mobile platform
True. But I don't know of a single gradual open source rollout by a larger company that didn't
happen according to plan (OpenOffice, Java, Netscape), so I'm willing to give Nokia the
benefit of doubt.
Symbian to be another open mobile platform
Well, Java is the example I was thinking about. Look how much time it's taking (still isn't
done!), far more than expected.
Symbian to be another open mobile platform
Agreed. My general rule of the thumb is "it's ready when it's in Debian main, fully
functional". In this case of course that'd mean Debian GNU/Symbian, at least on ARM port of it
:)
Slow Java open-sourcing
To be fair to Sun it's not like the control all the code from day zero. Proprietary code bases
tend to have all sorts of stuff in it and that takes a while to sort out.
Slow Java open-sourcing
Which is exactly why we should be skeptical of promises to open the
code -- the companies don't necessarily have the power to make the promise
reality.
Symbian to be another open mobile platform
I was under the impression that Sun said from the get go that some pieces might have to be
reimplemented since they didn't own the rights to them and weren't sure they could obtain
them.
Do you have a reference to Sun claiming this would happen faster than it already has? In my
world, the creation of IcedTea is evidence of how well the community can help out and pick up
the slack during a major code roll out like this.
In my world, the creation of IcedTea is evidence of how well the community can help out and pick up the slack during a major code roll out like this.
Java, Sun, IcedTea
Symbian to be another open mobile platform
It took Sun about a year to publish all of the JDK code they could under the GPL (~96 %), and
another year together with the OpenJDK community to finish off the remaining bits needed to
certify an implementation as Java6 compatibile.
The only comparison that remotely makes sense that I know of is the tri-licensing of the
Mozilla code base, which took 5 years until completion, afaik.
Two years from 0 to 100% is quite the opposite of slow for a radical licensing change on
codebase as mature and large as Java.