Nokia and Open Source — a Trial By Fire
An anonymous reader writes "The H has a damning piece on Nokia's open source smart phone projects, Maemo and MeeGo, and why they failed. 'They did dumb stuff like re-writing the whole networking stack, duplicating as they went. So instead of re-using NetworkManager and improving it, and getting to market fast – they re-wrote, got something that still doesn't work well, failed to push Linux forward, and failed. Repeat that for every technology pick and you get the idea,' said Andrew Wafaa. 'The N900 was a great product. Immediately [after] it was launched it was announced that it was a dead product, ISV-wise. They announced a Qt re-write/project re-set. Then they merged Maemo into MeeGo, giving another project re-set. Then, when they were coming up to release in September 2010, there was another project reset to switch to a different Qt technology (even the Qt groups in-fight in Nokia). In consequence they have no shipping product.' At the same time, 'both Nokia and Intel were working on separate handset UIs using Qt, the former proprietary, the latter open-source. A better worked example of squandering your leadership role and wrestling yourself to the ground is hard to see. Nokia deserve their trial by fire – and I hope the people who truly screwed up the amazing Linux opportunity that was the N900 get shut down in the process.'"
Nokia's former CEO, a lawyer, failed to notice the product groups were in such disarray. How cool must his job have been? He got to fly around the world in his suit spending money, while his product guys are achieving nothing for years, and he didn't even notice!
Now the in-fighting cannot frequently cripple development of other projects.
Makes me feel a lot less bad for the Nokia employees that walked out. Although likely moving at the whims of management, this report makes them sound more like hobbyists that simply want to build their own and tinker, rather than shipping a good product.
It certainly makes a good case for replacing a lot of the management as well. If employees end up leaving as a result, then they probably weren't great employees anyway, or they did not understand the problems that they were causing to their own development cycle by diligently following those managers out the door.
That is Nokia's big problem IMHO. The US has the biggest GNP of any single nation. It is a large unified market and it is just dumb to ignore it. Nokia didn't adapt the the US model by working with carriers to offer subsidized smart phones and didn't offer CDMA smart phones. Way back when Sprint had no really interesting smart phones I would have jumped on a Nokia smart phone. Now we have Android, IOS, WebOS, RIM, and WP7. I just got an EVO 4g but I would have bought the N900 if I could have for the same price and on Sprint.
Nokia believed that it could live marketing to the rest of the world and it did for a good while. Thing is all the new smart phone OSs are coming from North America.
See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
Sounds like moving to a third party OS was smart
Yeah, smart in contrast to the disaster that the submission is highlighting. Somehow, I have to think there might have been a third option in there somewhere...
The soylentnews experiment has been a dismal failure.
It didn't take seeing all this happening with the N900. I had a N800 and developed for it and saw that stuff then. That's when I bailed to iOS. At least with that you had some OS maturity and a platform that knew where it was going. I liked the N800--an open linux *computer* for my pocket. But the disarray of Nokia...
I was successfully blinded by the promise of Maemo. I owned a Nokia in the late 90s and hated it to the point that I said "never again" to Nokia. But then the N900 buzz started and I was first in line to get one. It's a great phone, and the platform does have potential. But man, it has been a really depressing ride so far.
From a relatively free Maemo platform to a walled garden is not an improvement. That, and unlike the iDevices, you can do all the things that Apple decrees that you cannot do and have all the things that Apple decrees that you shall not have.
Some of the things you're missing:
Non-carrier dependent tethering
Out-of-the-box root access
A mature, true-to-form Linux stack
OS upgrades that dont obliterate your personal data
Integrated QWERTY keyboard
Removable / expandable internal batteries
A standard USB connector
Non-proprietary screws
While you're waiting for the next upgrade to be jailbroken, many others are doing things with the phone that would be breakthroughs for the iDevice. With the current release of software.
Twitter supports and protects racists - by smearing their critics with the "Hate Speech" label.
It's weird how many engineers fall into the trap of trying too much when settling for good enough would be the right solution. You can always improve stuff in the next version, even if part of the code is ugly. I think the Hurd project has shown how well it works when you insist on getting it "just right".
There are exceptions (Blizzard for example), but often Good Enough is just what you need. Especially with OSS, where the user base doubles as QA and a feedback channel for new ideas.
.: Max Romantschuk
HEADLINE: The two kids that couldn't get dates to the prom decide to dance together. RESET one more time.
That mountain of cash MS has might help them out for a bit.
Yeah, I'm sure that didn't hurt too many people in upper management's feelings. Only time will tell if it will be worth it in the long run for the shareholders. Windows Phone 7 is extremely speculative at this point. So far, it little more than an also-ran and that doesn't appear to be on any trajectory for change any time soon. Characterizing it as the "third choice" in the grand scheme of mobile OS's as it is in a lot of the media is just pure dishonesty. I'm sure RIM might have something to say about that.
The soylentnews experiment has been a dismal failure.
Four options, all would probably had been better than Windows Phone 7:
1) Keep on developing MeeGo if they think it's better than Android. Throw in Alien Dalvik, get access to the "eco-system" of Android.
2) Probably better in the current market: Switch to Android base, slap QT on it, port whatever MeeGo applications they had already made over to Android. Sell. Would work both with Android applications for everyone who want to and not abandon QT or QT developers.
3) Buy or co-develop a new OS with RIMM. I've read they asked them but RIMM wasn't interested, or something such. QNX-based OS with QT and Alien Dalvik?
4) Buy Palm and use WebOS as base.
They aren't doing dumbphones very well any more either. For example, the Nokia 6600 fold has a bug where if you press the "6mno" key three times in a row during texting then every so often the phone will lock up solid. The only way to get back a working phone is to pop out the battery.
Since the issue was found (and reported on Nokia's forums) they've released no less than 6 updates - none of which have resolved the problem.
Avantslash - View Slashdot cleanly on your mobile phone.
Moving to a third-party OS you have no control over is never smart. If history should teach us anything it's that those who give up control of their platform end up dead by the side of the road somewhere. The only right option is to man up and whip the company into shape.
I gave up on Nokia back in the mid 1990's. Their phones always seemed like they would be awesome on paper, and then when you actually tried to use them you realized what a giant piece of shit they are. It wasn't because the phone was a piece of shit, though, like you usually find with products that look good on paper - the phones hardware is solid. It's the UI. Nokia has never been able to develop a usable UI. This was true in the 90's and several years ago when the N95 was the rage, I figured they'd had time to fix their mistakes. I bought an N95. Again, the hardware was awesome, but guess what? The UI was total garbage.
Nokia simply can't develop a UI that people want to use. In the 90's, long before smart phones, the UI was simply too slow. I literally had the problem of dialing too fast on Nokia phones. The UI couldn't even keep up with dialing a phone number. In the late 2000's, again the UI couldn't keep up with input, but add in the quasi-featurephone/smartphone hybrid that is Symbian and you have a graphically intensive, slow UI that is cumbersome to use. Another recipe for disaster.
I wish Nokia would pull their head out of their asses and take a step back to assess the fact that they have nothing to offer in terms of quality when it comes to the software end of things. Everything they have been doing up to know is complete fail; they need to realize this and look at successful software applications. Android, iOS and yes, possibly even WP7. Their new alliance with Microsoft is a step in the right direction, but it probably wasn't the best choice. Nokia could have dug themselves out of the giant hole they are in by going with Android (since I doubt even they could license iOS), simply, easily and quickly. Then again, they may feel the need to modify Android so much and re-write whatever they can that they'd make a mess of that, too. So perhaps the stern hand of Microsoft might let them put out a phone that's actually usable. Time will tell.
So I got a N900 a year ago. My first Nokia phone (I was a Sony man before). It was and is almost exactly what I am looking for. I was even impressed by the way Nokia did the whole repository thing. I am basically a PM. And as I looked into the processes that Nokia employeed, I slowly became disappointed.
They had initiatives for :
- code refactoring for better UI/responsiveness
- Meemo to Meego migration
- Ovi Suite
- Better front camera software stack
- Qt in the works
- voice recognization
- Android compatibility
- etc.
What I see are a lot of "initiatives" but no project plans or defined deliverables. It just seemed to me that there was no direction or focus. The second something became almost, it's direction changed. I don't mean to be rude, but this is what in-experienced programmers do. I am not talking about good/bad programmers, but about immature/mature programmers. Mature programmers are the guys who also write the good help docs & APIs along with the code. In-experienced programmers reinvent wheels, lose focus on the big picture, and get too much into their super optimized code. And I am not placing the blame on them, but rather the PMs. It is their duty to notice this, put them back on the correct path, and keep the big picture in mind. It is the PM's duty to define and focus on the deliverables. They need to make sure they aren't wasting time on useless optimizations that give you 50% gain a module, but a meer 1% in the overall process.
Going with Microsoft may give Nokia the ability to quickly draw a common big picture, but it does really nothing to address the issues underneath. Even within that big picture, the issues will just resurface and you will end up like you did with the N900. I really like the N900, but it can be so much better. Before this whole Microsoft thing, I was going to buy another N900 and was recommending it to 2 others in my office as PDAs. But after almost convincing my wife to buy my phone, I dropped it at the last minute. Along with my recommendations in the office environment. A good product is more than just hardware or even software, and I don't think Nokia gets it.
Every other story in TFA basically goes like this: "Our platform started on X, and then we changed it to Y, using Z UI library but the developers from Y used some of their own." As far as MeeGo and Moblin go, there didn't seem to be any attention to creating the minimum specification and just choosing what they were going to support and refine.
Nokia seemed to have completely outsourced their technology strategy to their open-source community process, and things stagnated over the sort of squabbles people in OSS know and love. Unlike Apple or Google, which took off-the-shelf OSS software that the community had written, made it their own and now act as BDFLs for their own brands and make their money off supporting and extending the OSS core; Nokia did the exact opposite, putting a ton of effort into reduplicating OS work, and then leaving support and extension to the community. It seems like their community process was completely dysfunctional and nobody working on MeeGo ever knew where the platform was going next. Nokia and Intel were very tight-lipped, so the people in the community would do their own thing and the platform would drift and work would be done on all kinds of stuff that didn't benefit Nokia. And then Nokia would come in one day and drop Gtk. You don't see the sort of high-level coordination that Google nominally does through the OHA, and you don't see the sort of commitment Apple makes to promoting their platform to end-users and keeping the platform as consistent as possible.
Open Source is good for a lot of things. People can write your software for you! But Nokia seemed to have the idea that if they just kickstarted an OSS phone OS, they could just sell handsets and the software platform would take care of itself with magic bazaar pixie dust, while assuming that at any time they could completely drop or add whatever technology they chose and the community would go along for the ride.
Don't blame me, I voted for Baltar.
Then Nokia can save a ton of development costs and just port Meego to the E7, then slap the N950 label on it.
Make it the same color as the N9-00 or N900, and you have a damn good phone.
Twitter supports and protects racists - by smearing their critics with the "Hate Speech" label.
HTC, Motorola and Samsung are doing terribly these days.
Fujitsu has released a MeeGo netbook and I'm sure more will follow. MeeGo isn't just Nokia.
I wasn't aware they had their own platforms that they rely on for their current market share like Nokia do.
have they moved to Android then? 'cos you cannot mean Microsoft - the company famous for infighting between teams. The Kin was shut down because it was in competition with Windows Phone team, and really - if you want a good laugh, read this blog piece about putting the shutdown menu into Vista.
Now, when you consider that one of the options available to Nokia in taking Windows Phone 7 was that their teams get to work on the WP7 code and customise or improve it you begin to understand just what a total, epic, unmitigated, colossal fail WP7 is soon to be (not that its been a roaring success so far!)
Ah yes, the classic "SMS of the Beast".
Today is red jello day - all workers must eat all of their red jello. Failure to comply will result in five demerits.
I was wondering that too. I think Nokia and HP should have made a deal to put WebOS on Nokia's phones. This would be good for both companies. It would have instantly created a huge market for WebOS apps and created a real viable alternative to iOS and Android. I highly doubt HP on their own will be able to make much of a dent in the current market.
[OT: What's with the double/triple spacing of the comment text?]
I bought an N800 a few years back because it was most portable and semi-capable Linux-based computer at the time. It did many things very well, but it did the important things (web browser, video, email) poorly.
My biggest gripe was that, after the device was sold and the necessary source code released, there was really nothing in the way of community help from Nokia. The firmware and applications were developed in secret and released infrequently. There was an official website, but community-hosted forums were where the real action was happening. And aside from a kludgy SDK, there was little help for third-party developers.