3 ms·
Nokia has to quickly post haste load android on all their smartphones. They will probably have to kick out Elop first, but that won't hurt at all. So (1) kick o
by hristov 14y ago
Nokia has to quickly post haste load android on all their smartphones. They will probably have to kick out Elop first, but that won't hurt at all. So (1) kick out Elop, (2) load Android.
It is fricking amazing how a board of presumably tech savvy businesspeople cannot understand the network effect. So let me put it simply -- it is over there are no more smartphone operating systems in the present smartphone segment. Google barely got in with android and the door slammed behind them. Meego was too late and Windows Phone was far too late. It does not matter how good Windows phone is, their DOA based on the network effect.
There are so many apps made already, there is so much investment in app production for both iOS and Android, that any new OS in the same space has unsurmountable obstacles to overcome.
There is actually an opportunity to make a new breakthrough in mobile devices, but one has to reinvent the market, like Apple did. The opportunity is for cheaper phones in the third world. Right now everyone wants a smart phone but most people in the world cannot afford the 600-700 prices (and no they cannot afford the higher subsidized monthly fees either). If someone comes up with a lightweight OS, that has similar features to modern smartphones, but perhaps with worse performance, worse screen, etc., that will be succesful. It will be succesful mostly because it will appeal to people that are outside of the network effects of Android and iOS. But that is not Windows.
- wallflower 14y ago> Google barely got in with android and the door slammed behind them. Meego was too late and Windows Phone was far too late. It does not matter how good Windows phone is, their DOA based on the network effect. This. If you draw a Venn diagram of competent iOS developers, Android developers, and Windows Phone developers - there is very little intersection in my experience. An individual developer's bandwidth is limited - they can't simultaneously easily grasp the intricacies of UITableView and ListView. It's like the old cliche about multi-tasking - it simply does not work in practice. I have met a few who claim to do both iOS and Android well but in practice they are sacrificing depth for breadth. Windows Phone is DOA for the reasons you stated and the fact that if there is a small consultancy or product shop that does iOS and Android - it is likely two different people. If you add Windows Phone, it will likely be a third person. From what I've heard from reading MSDN-type magazines about Windows Phone, those third persons are griping about how Microsoft keeps on changing the technology stack (e.g. WP7 is not compatible with WP8, Silverlight's evolution, etc.). Also, I have yet to see a Windows Phone in the wild in the hands of the coveted 18-39 Female demographic. That is dominated by iOS with some Android and Blackberry exceptions.