Feeds

How Nokia managed to drive its in-house Linux train off the rails

When Meego lost its mojo

3 Big data security analytics techniques

Special Report Nokia's strategy to revive its fortunes with its home-grown Linux was derailed by academic theory, bureaucratic in-fighting and a misguided partnership with Intel, a new report reveals.

Finnish publication Taskumuro has published an extensive history of the Meego project which contains a mixture of old and new: some information that's familiar - and some intriguing new details. The report confirms what we know: that Nokia had developed a competitive successor to its ageing Symbian platform years before Apple's iPhone appeared - but fluffed the execution so badly, it would eventually junk almost all of its internal platform software development.

Since February 2011, Nokia has abandoned Symbian, cancelled Meltemi and mothballed Meego - and will license Microsoft software for its high- and mid-range phones. Nokia continues to develop only its venerable Series 40 software in-house.

In short, Meego arrived a dollar short and a year or two late. However, Meego's problems weren't over. As we know from earlier reports, Meego ran into political problems: Nokia wanted to license it as an industry platform, but rival manufacturers were wary. The Finnish giant therefore faced a choice of building its own "ecosystem" or partnering with Google or Microsoft, and ultimately plumped for the latter.

Ironically, Meego lives on. Ex-Nokia staff have formed a spin-out called Jolla, snaffled up some investment, and are pitching the platform (now called 'SailFish') at the Chinese market. The first fruits of the venture will be unveiled at the end of this month.

Trolltech, dev teams and working at cross purposes

Nokia's first Linux device, a touchscreen tablet, made its debut seven years ago, in May 2005. With considerable foresight, Nokia persisted with the Linux-based platform Maemo, leaving it with a mature platform by the time Apple entered the market. The iPhone saw a significant shift as demand for smart devices soared, and the devices themselves changed from being phones with data, to tablets that also did phone calls. Taskumuro confirms that by early 2009 Nokia had positioned Linux as the company's No 1 strategic platform.

This was confirmed in September 2009 at the annual Nokia World event, which was held in Stuttgart. Executive Anssi Vanjoki explained that Nokia's Linux was in its fourth generation, embodied by the N900 tablet, which made its debut at the event. Vanjoki said at the time that the fifth generation would be the first, true mass market iteration.

And indeed, we now learn, Nokia had a range of products sketched in for 2010 launch including a Meego communicator with slide-out keyboard, much like the ill-fated N97.

So what went wrong?

A Nokia Linux timeline

  • May 2005: Nokia unveils its first Linux device: a 800x480 pen-based tablet, the N770. It does VoIP calls, plays net radio, and uses the Opera web browser. It borrows UI design from Hildon, and the platform OS from Debian.
  • January 2007: Apple announces the iPhone; second generation Nokia tablet announced – the N800.
  • October 2007: Nokia's N810 sprouts a keyboard.
  • January 2008: Nokia acquires Trolltech, whose Qt cross-platform framework is used for Google Earth and Skype. The plan is to unify all of Nokia's platforms with one API.
  • June 2008: Nokia acquires Symbian, spins ownership out to a Foundation, and removes license fees, all in response to Google's free Android OS.
  • September 2008: Nokia announces cellular telephony is coming to Maemo 5.
  • June 2009: Nokia and Intel cosy up
  • July 2009: Third-generation iPhone appears.
  • September 2009: Nokia confirms the next, fifth iteration of Linux will be the future smart device platform. Apple loosens carrier exclusivity on iPhone, and Orange and Vodafone UK announce the device will be available on their networks.
  • October 2009: Android 2.0 released to phone manufacturers, with new UI, and wins widespread support. Devices incorporating the software spread like bunnies over the following spring and summer.
  • February 2010: Nokia and Intel announce they're pooling their respective Linux platforms – Maemo and Moblin – to create Meego - which will "support multiple hardware architectures across the broadest range of device segments". It'll come to netbooks, TVs and cars ... and smartphones.
  • May 2010: Nokia board begins hunt for replacement for CEO.
  • September 2010: Stephen Elop appointed CEO of Nokia, instigates urgent review of platform options.
  • February 2011: Elop announces partnership with Microsoft; Meego is relegated to "project" status for "longer-term market exploration" on devices, platforms, and "user experiences". Nokia's Meego chief and board member Alberto Torres resigns.
  • June 2011: Nokia quietly announces its first and last MeeGo smartphone, the N9, running what it calls "MeeGo 1.2 Harmattan". It's a stunning design with a radical new 'Swipe' UI, but only launches in selected markets.

Well, we know that Nokia wasted thousands of man years of developer time in-fighting. Even though the management made the right long-term call, acquiring Trolltech for its excellent Qt framework, it lost control of the engineering organisation. A huge project called Orbit vied for resources with a rival, a framework called libdui – or DirectUI. "Both teams had built the wrong thing," one developer later explained. Former Sun CTO Rich Green would cancel both.

What we didn't know is that Maemo, later Meego after the alliance with Intel was formalised, went through three different UI designs. Most of the time it was absorbed by a series of concepts drawn from theory.

Top three mobile application threats

Next page: Activity Theory

More from The Register

next story
This time it's 'Personal': new Office 365 sub covers just two devices
Redmond also brings Office into Google's back yard
Inside the Hekaton: SQL Server 2014's database engine deconstructed
Nadella's database sqares the circle of cheap memory vs speed
Microsoft lobs pre-release Windows Phone 8.1 at devs who dare
App makers can load it before anyone else, but if they do they're stuck with it
Oh no, Joe: WinPhone users already griping over 8.1 mega-update
Hang on. Which bit of Developer Preview don't you understand?
Half of Twitter's 'active users' are SILENT STALKERS
Nearly 50% have NEVER tweeted a word
Internet-of-stuff startup dumps NoSQL for ... SQL?
NoSQL taste great at first but lacks proper nutrients, says startup cloud whiz
Batten down the hatches, Ubuntu 14.04 LTS due in TWO DAYS
Admins dab straining server brows in advance of Trusty Tahr's long-term support landing
IRS boss on XP migration: 'Classic fix the airplane while you're flying it attempt'
Plus: Condoleezza Rice at Dropbox 'maybe she can find ... weapons of mass destruction'
Ditch the sync, paddle in the Streem: Upstart offers syncless sharing
Upload, delete and carry on sharing afterwards?
prev story

Whitepapers

Top three mobile application threats
Learn about three of the top mobile application security threats facing businesses today and recommendations on how to mitigate the risk.
Combat fraud and increase customer satisfaction
Based on their experience using HP ArcSight Enterprise Security Manager for IT security operations, Finansbank moved to HP ArcSight ESM for fraud management.
The benefits of software based PBX
Why you should break free from your proprietary PBX and how to leverage your existing server hardware.
Five 3D headsets to be won!
We were so impressed by the Durovis Dive headset we’ve asked the company to give some away to Reg readers.
SANS - Survey on application security programs
In this whitepaper learn about the state of application security programs and practices of 488 surveyed respondents, and discover how mature and effective these programs are.