MeeGo Limbo

Several people have asked me to put my thoughts down on Nokia’s new partnership with Microsoft.  Twitter just isn’t the place for it; several 140-characters-or-less postings were met with responses quite distant from where I was going.  I’ll try to say something useful and coherent– but keep in mind this will be an opinion piece.  Very personal.  And lengthy.

To understand my take on things you need to understand where I come from.  Six years ago I was perfectly happy without a cell phone.  I had no need for one, even despised and sometimes pitied people enslaved to them.  And smartphones?  I dismissed the idea entirely.  What would I do with a “computer in my palm”?  How smart could a phone be?  

Then a strange thing happened.  I applied for a job with the world’s largest cell phone maker, a position that looked too cool to let pass.  It involved quality… research…process… data… a lab… and a factory.  My kind of playground!  Miraculously, they hired me, partly because I had no cell phone expertise. I could be objective.  Point out where the king had no clothing.

Working in that factory was the happiest time of my professional life.

And as I grew more competent and comfortable in the field of mobile phones, I came to understand that it wasn’t just about self-involved people annoying others nearby with their loud, proud conversations.  It wasn’t even about seeing who could drive the best while texting behind the wheel.

It was about connecting people.

And six years ago I wasn’t an open source evangelist, either.  I worked in a medical products laboratory and did some serious software development for product test purposes, using of all things, Microsoft tools.  Excel and VB.Net in particular.  I even wrote an application that automated the conversion of electric motor test data to marketing charts and tables in minutes, replacing a manual job that had taken days.  I was good at that sort of thing.  And I’ve always been pleased with Microsoft’s development solutions.

So I was in for something big and different when a few years later I was named the US factory quality engineer for the Nokia 770.  I was blown away by the product alone, but as I became more familiar with what it could do, I was truly impressed with its potential.  Suddenly the idea of a computer in my palm was no longer this abstract concept, but something I could see, feel, do.  And it ran Linux.

Linux at that time was something else I thought of in abstract terms.  To me it was this big collaborative geek project largely designed to keep Microsoft honest– and usually failing at that.  But now I had it in my palm and saw it was capable.  I could install a VPN client on it and access the databases I managed over the air.  I could free up our quality auditors from fighting over a few shared PCs.  And that was just the start!

The coolest thing though was that the 770 Came With Community.  One that looked to Nokia for guidance and support.  One that dreamed bigger than my employer did.  One that didn’t seem to mind that I was a Linux newbie with a largely Microsoft background.  I was a self-annointed envoy to the mothership; good enough!

The Maemo community was an exciting place.  I saw a lot more acceptance there than I had at other mostly-virtual organizations.  Certainly a great deal of can-do spirit.

And Nokia was a can-do company– at least, among the rank and file.  I didn’t realize it at the time, but there was a stubborn crust at the top, baked over a thick, resistant middle filling.  Maybe the average employee was can-do because he had to.

Regardless, Maemo was underfunded and underappreciated within Nokia’s walls, and ultimately the open source science project was displaced for MeeGo.

With MeeGo we have been accomplishing things we could not get going under the maemo.org banner.  Local and regional meetups, at least in favorable areas, have enjoyed incredible success… proving to me, at least, that the solution had potential.

Then, early this morning, Nokia announced it would embrace Windows Phone 7 and reduce its MeeGo involvement to around the level Maemo had suffered when the 770 came out.  In other words, life support.

Some observers have leapt to the conclusion that abandonment of the venture by principle partner Nokia will automatically spell doom for MeeGo in toto.  I find it difficult to accept that Intel, Texas Instruments and others will simply fold up shop simply because Nokia has elected to invest elsewhere.  Surely MeeGo is more resilient than that.

Other have suggested that MeeGo’s continued existence means partnering with competitors.  WebOS, itself Linux-based, has been mentioned.  There are others with possible synergy that could be approached.

But the biggest question, one that apparently could not be answered satisfactorily for new Nokia CEO Stephen Elop, was: how do you build a profitable ecosystem around mobilized Linux?

I don’t see it as that difficult to address.  Adoption of an open source solution like MeeGo significantly reduces a company’s OS development costs, freeing resources up to focus on the two profit drivers that will be most important as many aspects of mobile computers are rendered into commodities: hardware, and services.

Hardware is tougher to to solve.  Gaining a technical advantage in the consumer device space means locking up exclusive high-tech from suppliers loathe to do so.  Even MeeGo partner Intel likes to cover all of the bases.  And today’s exotic must-have hardware is tomorrow’s boring commodity.

Service is different, and it manifests in two ways: the software solutions that differentiate one experience from another, and then the service of making good on your products’ promises.

Nokia struggled with both types of service, but if Elop is blaming that on MeeGo or its hard-working supporters when he speaks of burning platforms, he’s out to lunch.  Nokia screwed up in many ways, and in my humble opinion one big one was in trying to copy short-term business practices of the US that end up being self-defeating.  And here’s Stephen Elop, dishing out more of the same.  Time alone will tell if he’s right… but if he’s wrong, will Nokia recover?

What about Maemo, then? If MeeGo itself was prematurely put to death, Maemo would be the first place to which I would turn.  The recent community SSU shows that there may still be some life there.  But what if Maemo can’t survive?  It certainly been enjoyed some association with MeeGo.  If the latter goes, is a community-supported Maemo unsustainable?  Maybe not if Nokia released the entire platform… but I can’t see that happening.

If MeeGo survives Nokia’s diminished attention, still under the auspices of the Linux Foundation, nothing really has to change with regards to my involvement.  I’m running MeeGo 1.1 on my Intel-gifted ideapad, and mostly pleased.  However, rumor now has it that the Netbook UX has lost Intel’s support.  I don’t get that.  And I’m also not sure what I do with the marketing materials I’ve been creating, as well as the local meetup groups I’m supporting.  We’re looking for a strong signal from the Linux Foundation and especially Intel.  Interestingly, I was informed before Nokia’s announcement that Intel is working on a MeeGo brand refresh, one that emphasized community more.  That makes a great deal of sense now, and I’m looking forward to the results.

If MeeGo AND Maemo fizzle, that leaves me looking for a new hobby altogether.  Supporting these communities has been a time-consuming, often nerve-wracking ordeal on one hand… but it’s also blessed me with a wealth of friends who would likely drift off to other endeavors and we might eventually lose touch.  Not to mention the opportunities to travel to places, like Dublin and Amsterdam, I might not otherwise have ever enjoyed.  Will it end, or are we perhaps looking at something else entirely– a reboot?  A remix?  A stronger, clearer, sharper commitment to open source solutions?

I’ll leave the in-depth analysis of Nokia’s move to people better suited.  But I’ll talk on this subject some more, from different angles, until there’s nothing more to talk about.

One way or another.

About these ads

17 responses to “MeeGo Limbo

  1. I hope MeeGo survives too. It’s funny because I just made the similar comparison of MeeGo joining Maemo on life support on Twitter!

    It’s a shame Elop couldn’t have come in, seen Maemo and gone “Let’s use that!” instead of just having a hard on for WP7, which contrary to my devil’s advocate role on Twitter, I strongly believe I be true.

    But, we shall see. Nokia is only putting the entire future of the company on this decision, so no pressure for them.

    None at all.

  2. Pingback: Tweets that mention MeeGo Limbo « Tabula Crypticum -- Topsy.com

  3. What about the phoone Nokia mentioned that will come with MeeGo. Maybe it would help to show Nokia that’s what we want if we all buy and promote iz more so that it outsels any WP7 phone they put out. And maybe we should be asking at mobile phone providrs and mobile stores for that specific phone so we put more pressure from this side.

    I myself am not that terrirbly exited with the netbook UX yet, still waiting untill they switch to Qt/QML for it to see if it is any better. At this moment I really like the KDE Plasma netbook interface much more.

    Anyways, I sure hope that other MeeGo commercial partners like Intel, AMD, Amino,…. continue full speed and that this shows the Linux Foundation that they have much more work to do wehn it comes to marketing MeeGo and creating hype and mindshare behind it. And as MeeGo community we should really have more faith in us, if we lose it than ….

    • My guess is Meego will survive not on Handset but tablets/netbook.

      However there is a bigger issue with the Qt framework?

      What will happen too this? In the longer run Microsoft coulod well buy Nokia… And guess what will happen to Qt…

  4. I have heard a rumor that Nokia already had a prototype of the first MeeGo device, but MeeGo was not performing very well on it. Then they tested WP7, and were very pleased with the results. That would explain the news that Nokia “gave up” on the MeeGo device: it would have actually been converted into a WP7 phone. Does anybody have more information about that?

    This handset MeeGo version must have been really terrible for a system without multitasking and cut-and-pate to give a better impression. And the hardware must be something radically different from N900…

  5. From what I have heard, the Nokia customization of MeeGo was nowhere close to being ready. I think Elop ran out of patience and made a run to his old boss. It would have been tough to sustain an interest on a platform if no phone is planned to be commercially ready for another year.

  6. Afterthoughts:

    Stephen Elop attempted to clarify Nokia’s position vis-a-vis MeeGo during Mobile World Congress 2011, but what I’ve read so far looks like rehash of what we heard last Friday– MeeGo will be part of a limited test bed for interesting technologies. In addition, he reiterated that Qt is not in the picture for mainstream development.

    My take is that Nokia has to convince Microsoft they are serious about supporting their mobile vision. That is, Windows Phone 7 is expected to create a third ecosystem to compete with Apple and Google. The unspoken portion is that all other ecosystems will be relegated to insignificance at best.

    Granted there should be enough differentiation with WP7 to pull off such a thing. The only questions will be selling consumers (I have some doubt) and instilling confidence in developers (I have major doubts).

    MeeGo could very well have occupied that third slot, and in my opinion has the potential to do it better than anything Microsoft based. Linux has the momentum, and the advantage of pulling in many more developers than any alternative. Qt would have been (and still can be for others) a great enabler for that. But I think the new Nokia is afraid of openness. Those who championed it in Nokia are gone.

    I suspect Nokia fears if it places any reasonable emphasis on MeeGo, that it violates part of their agreement with Microsoft. At the same time, Nokia would be stupid not to be hedging their bets to some degree. If Elop is smart, he will put in place the agility necessary to rapidly ramp up on MeeGo if/when necessary. But could he regain the trust of the open source community?

    • Based on a number of things, including his ducks comment to AllThingsD, I have a sneaky suspicion that Windows Phone is a short-term solution designed (partially) to take much of the focus off of MeeGo (which has been pressured to launch to consumers for the past 12+ months, despite everyone knowing full well that it’s nowhere close to being ready). By averting everyone’s attention for another 12-18 months, this gives MeeGo room to breathe and focus. Of course, that’s making a tremendous amount of assumptions, but it’s at least a little bit logical.

  7. I will tell you what is nice to see. Many posts have looked back to why. Why did I get involved with this, where do i come from and then I can answer this.

    I still feel vaguley positve about all of this..strange? maybe …maybe not..we will see.

    However I do see light at the end of the tunnel…otherwise this would be being written on an Ubuntu machine ;)

    • Thanks!

      I was finding myself fending off “Microsoft hater” assumptions, so that was one reason for the background. Heck I enjoy VB.Net and T-SQL– but I’m more fond of open development.

      *typing from my MeeGo-powered ideapad :D*

  8. I know this will seem blunt, but you know me, so you know I’m just being honest. To Nokia, Maemo = MeeGo. Both in terms of what the company *wanted* it to be and the pitiful amount of resources the company gave it to do so.

  9. No issues, especially since I no longer blog here.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s