RIP, Nokia (1865 - 2014)
pandodaily.com
RIP, Nokia (1865 - 2014)
1–10 of 53 posts
Re: RIP, Nokia (1865 - 2014)
#2Nokia get rid this problem by doing some encouragement to develop in their old J2ME/Symbian platform in such country that still have good market share like Indonesia. In Indonesia, Nokia encourage developer to develop games in their platform in a contest named "Developer War", and now it has 4 episode/chapter.
Re: RIP, Nokia (1865 - 2014)
#3Nokia get rid this problem by doing some encouragement to develop in their old J2ME/Symbian platform in such country that still have good market share like Indonesia. In Indonesia, Nokia encourage developer to develop games in their platform in a contest named "Developer War", and now it has 4 episode/chapter.
I hear Blackberry is still going strong in Indonesia as well. Still, worldwide, they're doomed.
Re: RIP, Nokia (1865 - 2014)
#4I don't think it's necessarily game over for Nokia, but they've got to drastically rethink their game plan.
They burned through cash getting the Lumia phones ready, gorgeous as they are, which is a gamble not yet to pay off. They're using the third horse in the race, a platform which it's creators have yet to successfully manage into the mainstream consciousness. Too many flaws to stand next to Android and iOS, but not completely down yet.
Lets not forget Nokia is still one of the biggest mobile handset companies in the world, they've got a solid brand name appreciation in areas of the world yet to be opened up.
Essentially they've still got chips left on the table, it just depends on the next run of cards whether they grow their stack or not. But lets not get in the way of a snappy headline.
Re: RIP, Nokia (1865 - 2014)
#5Nokia won't last until 2014. They are declining too fast. They went from 45% market share to 18% in China, one of their strongest and biggest markets, last year alone. This year they will probably fall way below 10%. Nokia will most likely be acquired by the end of this year or in the first half of next year (or go bankrupt otherwise).
Re: RIP, Nokia (1865 - 2014)
#6While I certainly wouldn't call Nokia's position anything but worrisome, I think it might be a little early to start planning the funeral.
One of the benefits Nokia has by going with Windows Phone is the relationship it now has with Microsoft. I'd be very surprised if Nokia's tablet offering isn't front and center in just about every piece of marketing MS does.
The biggest issue that Windows Phone has currently is a lack of third party applications. I really do think that standardizing the platform across Phone/Tablet/PC will help in a big way with this problem (not pushing them to higher numbers than iOS/Android, but much, much closer than they are today).
Re: RIP, Nokia (1865 - 2014)
#7"If Nokia had gone with Android, the best that it might have achieved was to become an also-ran—another in an endless stream of me-too commodity smartphone makers."
No. Nokia could've been Samsung, which has the lion's share of the Android market. And Android Lumia would be the prettiest Android handset on the market.
Re: RIP, Nokia (1865 - 2014)
#8Nokia get rid this problem by doing some encouragement to develop in their old J2ME/Symbian platform in such country that still have good market share like Indonesia. In Indonesia, Nokia encourage developer to develop games in their platform in a contest named "Developer War", and now it has 4 episode/chapter.
old J2ME/Symbian platform
No. Just... no.
I'm really pleased that Symbian is dead (or on life support). It is, so far, the worst platform I have ever had to deal with. Eclipse-based IDE for €300-1300, partner-only premium APIs, completely unusable multi-gigabyte emulator (if you needed to run two instances, you had to install... two copies in different directories!), awful documentation, terrible system libraries, and quirky Symbian C++ dialect... it was quite an experience, but I will never miss it.
Anything we have today is better than Symbian.
Re: RIP, Nokia (1865 - 2014)
#9While I certainly wouldn't call Nokia's position anything but worrisome, I think it might be a little early to start planning the funeral. One of the benefits Nokia has by going with Windows Phone is the relationship it now has with Microsoft. I'd be very surprised if Nokia's tablet offering isn't front and center in just about every piece of marketing MS does. The biggest issue that Windows Phone has currently is a…
For the average non-tech user, is the lack of third party apps really that big of an issue? In all honesty, all they need is Facebook, Twitter, Angry Birds and sudoku, which WP7 has. You're really not at a loss for apps when it comes to the popular 1st tier apps.
The bigger issue, from my personal experience seeing people pick up and use a WP7 device, is that it's awkward to use compared to the grid of icons in iOS and Android. They're utterly confused and have no idea how to even begin. Metro, as executed by MS, is simply not intuitive. The starkness of the white on black text is cold and unfriendly. Interaction paradigms they learned from iOS and Android are slightly different in WP7, which results in frustration around every corner. The pure icon based menus make it a guessing game on which icon does what. From my personal experience, regular people have a much easier time switching between Android and iOS. WP is just too different.
Re: RIP, Nokia (1865 - 2014)
#10Is this a serious piece of writing or just trolling?
> 2003-2008 = back when euro was worth real money.
1 euro was worth between 1.1 and 1.5$. Now, it is worth 1.25$...
> Rather than spend its resources on building an OS that depended on novel interfaces and sensors,
Like the first (and best) GPS phones?
> that allowed for outside development
Like symbian and the nokia owned qt creator.
> If Nokia had gone with Android[...] Windows Phone, on the other hand [...]
Aren't you forgetting the numerous other hands that are symbian and its successors: tizen, meego and meltemi?
> Elop [...] clear-eyed
Humm. Choosing to ditch their own system to use another one may have been a bold and smart move, but still developping 2 or 3 different systems while trying to integrate an external new (and unproven) one seems to me like increasing the problem rather than solving it.