I fully agree with that. If Nokia is going out of business than I beleive it is the lack of the management to understand that software is the key which makes the differen. I still beleive having hardware without own OS will not keep you alive for ever. If I look in Asia everyone can build a smartphone even never knew how it even works. Qualcomm, Mediatek they all have reference designs. So what differentiates someone using the same form factor turnkey solution? I believe this will be also the loss one day for Samsung and Co. What's the difference between them and anyone in the world. By the way one day might be Google waking up and decide not to give Android to the open market or stop development than everyone will be running out of options.
i think eventually microsoft will buy it.
i don't agree that they should have gone with android.
and i own a Asha phone, its no fun accessing it on a small screen, facebook application is waste, and nokia store is joke.
I am glad that you laid this all out. I do remember the days when Nokia actually had a lot of software options -- like Maemo and QT. But none of them really got the proper attention from the management (or they probably didn't know what to do with them) and they ended up being viewed as "taking too long" before turning into gold.
I never understood then why Nokia was making so much investment in so many different software options...
Weird that nobody mentioned how Nokia screwed up Maemo yet. Before Android and iOS, Nokia had the very best mobile OS, but through poor execution they failed to cash in on that advantage. At the time, Maemo was lightyears ahead in mobile web access and was establishing a thriving developer ecosystem.
Only, Nokia at first didn't put it in a phone, but made internet tablets only. Then they did make a phone (the legendary N900), but didn't really market it. You couldn't find it in brick and mortar stores. They were still pushing their Symbian phones.
Then Nokia bought Trolltech, and decided the Maemo GUI should be switched from GTK to Qt. Then they decided to merge with Intel's Moblin and Maemo became Meego, again switching internal technologies (like DEB to RPM packages). Then they decided all this was taking too long, and with an ex-Microsoft guy at the helm, they decided to ditch Meego and go to Windows. Of course through this whole mess they demolished their developer base, especially since most of them came from a Linux background.
I've never seen such a determined effort to fail. Windows 8 is a dog, and there's no way it's going to do Nokia any good. It's only going to drag them down more.
If only they had realized what a gem they had and given it the love it deserved, they would be at the top of the smartphone game now.
So, I use both the Nokia 6310i and the iPhone 5. Both fullfill in what they need to do: An ancient dependable cellphone and a state of the art well integrated smartphone. Don't like Android phones because these are too much of a hack job. That's why Windows phone might actually be a smart move. In Holland and France the Nokia Lumia 920 pre-orders already have beaten iPhone 5, so for now their future looks bright.
One of the build quality which Nokia is good at, consistently, is casing. The case of Lumia 9xx/8xx is simply awesome. In the world, Apple has demonstrated similar know-how but fail in terms of the colours offered. The colours offered by the Lumia-series are so attractive and so special.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.