WP8.1 added some good things, but also added the ability for the homescreen to swap out; loading... when starting a backgrounded app was bad enough. Anyway, there were new cheap options that were decent and shipped with WP8.1, so.
Then came WP10 -- the promised upgrades for WP8 devices didn't really pan out, the majority of WP8 devices aren't eligible because they don't have enough ram, and very few of the rest were offered the upgrade through the update system, you have to jump through a bunch of hoops.
That's really for the best because the first year of WP10 releases seem like nobody actually tested them on a phone, until Creators Update, which was actually pretty decent -- except for Edge, which is so much amazingly worse than IE, but Microsoft didn't want any other browsers on their store. It doesn't help that there's only about 5 phones available that ship with WP10, three of which are high end, and the low end ones are more expensive than the WP8 phones upgradable to WP10, and have at best, equivalent hardware.
I'm not saying a good WP10 release would have somehow gotten windows phone into 2nd place (even worldwide, where Apple is way behind Android), but it would have kept them out of speculation for which platform would finally fail first -- Symbian, Blackberry, Blackberry 10, or Windows Phone.
Edit to add -- each flavor of Windows Phone strongly encouraging developers to throw out the SDK and start again doesn't help either. There may never been more WP10 users than there are WP8 users right now, rewriting the app to better support WP10 is a waste of effort, and the proposed update to WP10 to stop supporting apps that can also run on WP8 is a great way to kill both platforms.
It's worth noting that Microsoft did actually do this in 2014 - they made windows free for devices sized 9 inches or less: https://www.neowin.net/news/microsoft-officially-makes-windo...
Granted, this is long after Windows Phone 7's initial release back in 2010.
I blame Experiment 19: https://www.microsoft.com/en-us/research/project/experiment-...
The prototype proved that Windows NT and the CLR could deliver better performance than Windows CE and the .NET Compact Framework on identical hardware. Within months of the completion of Experiment 19, Microsoft launched efforts to build what would become Windows Phone 8 and Windows RT for ARM tablets.
AFAIK, they wanted developers to use native code and Windows API. This is especially needed for games and other resource-demanding apps.
Windows CE is just too old. The security there is comparable to Windows 9.x, i.e. almost no security. It was very hard to design a CE-based OS that would allow arbitrary native code to run, while denying the ability to access user’s private data and break the device.
WP7 only allowed C++ code for close MS partners. Regular developers had to use .NET, which has its own very advanced security model built-in.
Probably, MS thought that once they allow C++ development, third-party developers start to port their older Windows games to WP 8 + Direct3D 11 feature level 9.3.
Eventually the plan didn’t work. MS bought Minecraft, convinced Rockstar to port GTA San Andreas, but the platform still hadn’t gain enough traction, and most third party developers passed.
Look at Apple and compare the iPhone and Mac versions. They share the same architecture and a lot of code and that is not just on the surface but for real. This allows Apple to have one very, very good codebase for their OS. Microsoft did not have that solid foundation and additional challenges particularly in the area of security. There was no way for them to catch up if they maintained multiple platforms. To see where trying to have multiple platforms lead just study Nokia.
The WP7 -> WP8 thing was unforgivable.
Swapping the hardware is the easy part but integrating new components with your SAP powered warehouse (with custom things your $1k+/day SAP specialists have flown in and written and left undocumented) itself is generally a massive project.
The other thing to do would have been to offer Android app compatibility. I wonder if it would have been possible to spend that money they paid developers to port apps on developing a decent compatibility layer that would have made the porting unnecessary. Or provide tooling that made APK -> Windows app compilation super easy.
As is, they had a sad story of a phone with some neat features but no big steps forward, in a market already saturated by good-enough competition.
Aren't iPhones and galaxy "active" or something are waterproof?
There are "survival" type phone that have weeks of battery life and shock/water proof, but it's not what the market wants, there is a minority of people who would sacrifice the look/dimensions/weight of he phone for the N week batter life. Most consumers would go for the looks and portability I think. That's why iphone sells as much and those "survival" phones don't. Do you think if iphone would stick a twice as thick of a battery in its next iPhone many people would buy it? I certainly would not
iOS lacks a lot of the features I take for granted (MTP for arbitrary file types, support for app stores like HumbleBundle, ability to run different browsers and servers like ssh on-device). The iPhone hardware itself: non-removable battery, no external storage, and current models don't have a headphone jack. I'm not a fan of wireless audio devices. I'd have a fair amount of software to re-purchase. I've got an iPhone 6 available to me, that was originally a work phone. It's nice, in a lot of ways. Not something I'd consider for my "daily driver".
So, what prevents me? The fact that those devices would still be unsuitable, even if I got a battery case. I would've considered the Sony Xperia X Compact, if it had been released when I was last phone shopping. Seems Sony's got a bad habit of not updating their phones, I doubt their commitment to supporting them, and that's a particularly niche model, anyhow. Not much third-party support.
Not sure what this guy means by water proof, but you will never have a truly 100% water proof phone, since you can't really have a truly water proof any expensive electrical device. Since nothing can withstand the water at really low depths/high pressure, even submarines.
Waterproof is not the same as pressure proof. Typically the rating is set by the seals used. If hard seals were used or single piece ultrasonic welded cases, the device would really be waterproof. Soft seals will start leaking water because the seal material compresses.
Submarines are waterproof unless damaged. They have a crush depth though.
After Nokia switched from Meego to Windows Phone with the Microsoft deal a group of Meego devs left and ceated the new company Jolla, where they developed the Sailfish OS as a branch of Meego.
Sailfish has a built-in Android emulator, it's a version of Alien Dalvik. I've actually found it quite good, although there's a slight input delay, it uses additional battery power since it's emulating the apps, and it's getting a bit out of date now (it supports a relatively old version of Android, although I think they're currently working on updating it to some extent).
Supposedly, the tried and gave up - but whatever effort was spent doing that eventually resulted in WSL.
There was a 3rd party BlueCard project that attempted to bring Android apps to Windows 8, but it only supported older versions of Android at the time.
The only other phone I know of that kind of tried to do this was the atrix, which afaik was a failure
So in my eyes if they could've gotten top app support from coming out with W7 earlier or just somehow getting that support when they did release things, it would've salvaged things. The insane Nokia purchase price would still need to be heavily written down along with a lot of layoffs. Just not as much as what actually happened.
Ah well. Most of all I will miss webOS, then Windows 8 Mobile.
For many users, the everyday experience of using the Internet surrounds watching videos on YouTube, finding their way with Google Maps, and communicating using Gmail.
Google's mission statement, of course, is "to organize the world's information and make it universally accessible and useful"... however, that is an abridgment: the full version continues in a whisper with "(except on Windows Phone)".
What follows are a selection of stories of Google's process of systematically isolating Windows Phone, each backed up with articles of the time (though it is of course trivial to find references: even mainstream media started to realize that the whole is greater than the sum of the parts and started questioning the underlying motives).
Microsoft was forced to write their own YouTube application, which did not show ads and so was blocked by Google. I will note that Apple also effectively did this, though working with Google (a key difference), so this isn't crazy on the face of it: the original iPhone came with a copy of YouTube written by Apple that did not play any advertisements.
In the aftermath of this debacle, they wrote a new one, working along with Google this time (as far as I understand), that did show advertisements and was designed to satisfy Google's other demands... but Google seriously waited until it was not just completed but fully released and then went ahead and blocked it anyway.
Recently, Google decided that users of Gmail would not be able to access their email using Outlook on Windows Phone... even though it isn't like Microsoft is bad at email of all things.
However, this isn't the first time that Google messed with Windows Phone on email: when they removed the Exchange ActiveSync protocol, it was seen by many as a direct attack on Windows Phone.
And who could forget the saga of Google Maps, which was blocked by Google on Windows Phone, even though it was accessible on other phones which used the exact same web browser engine, and even though the renderer was shared by the desktop version of IE.
At one point Google's AdMob started to see a massive drop in revenue... only on Windows Phone. This was later claimed to be a "bug", but of course took Google a long time to come up with a fix, undercutting developer revenue on the platform.
Of course, Google refused to bring any other software to the platform, such as for Google Voice; and while you used to be able to use this from the web, once Apple relented and allowed Google Voice in the App Store, Google mostly stopped bothering maintaining their web version.
This wouldn't be so bad, but Google also tends to throw its weight around to get third-party clients for their products pulled from places like the App Store... now, I personally think they have no legal basis to do this, but Apple goes along with it (as Gooogle does support their platform ;P) and it creates a chilling effect on people writing their own clients elsewhere.
Regardless, someone did write a third-party Google Voice app for Windows Phone, and Microsoft (who had even been frantically writing their own third-party apps) let it stay around. So, Google had to change their terms of service and figure out how to block it on their server, as again: their unabridged mission statement clearly reads "(except on Windows Phone)".
I think Google could have only employed this strategy against an already failing adversary: they haven't tried the same against the iOS platform.
Microsoft isn't paying Google to please its users, so I don't see how MS can reasonably expect Google to do so. They are competing, for-profit companies. Google isn't responsible for the Windows Phone platform, Microsoft is.
Too bad there were never enough apps, IE mobile was buggy, and I felt that my Lumia never had the build quality Nokia was once famous for.
I loved the Lumia 1520 device. It was beautiful, felt extremely good in the hand, was only slightly hefty, and the IPS display was phenomenal -- no AMOLED screen can compare to a Lumia IPS display when it comes to reading text. It was so good.
However, it was a death by a thousand paper cuts -- as many others have already pointed out. Even though I adored the device, I couldn't help but notice how useless it was. I was lucky enough to find several apps that I wanted to have on both my S7E and the L1520 but in the end, they were written by enthusiastic underpaid devs and were lagging behind in features, and some of their bugs I continuously observed throughout my full year with the device.
I was saddened to sell it but hoarding tech whose death clock has been running for a while is not sensible.
No one asked for another restricted platform.
The UI is still arguably more advanced. Instead of just another take on the old desktop model, a sea of icons, it had useful tiles. It has neat features like when disabling WiFi, it'll ask for how long -- something I always forget in Android, ending up costing me mobile data.
But hey being too late to market and coming out with underwhelming devices then abandoning them repeatedly... no thanks. Didn't help their app story was weak, and their app store filled with shit - (Windows Store STILL is). Used to be that a search for "Netflix" would result in fake Netflix apps. Even now, searching for HBO or Game of Thrones results in fake apps.
Update: I mean, other than Android :)
Update: I'm reading about Tizen now and Sailfish
Now if only I could work sony's naming scheme. Apparently the x series is the replacement of the z series (what happened to the y series?). Then looking at local retailers, all I can find are the XZ phones, so who knows what they are. Haven't looked at specs yet because I'm lost in code names. I really wish buying from any other manufacturer was as simple as buying from apple.
By that time, 1 billion Android devices had already been sold. The first Android phone was sold in October 2008. The iPhone was released in June 2007.
Ubuntu entered the market six years later and had to take on these two market giants, as well as other competitors like Microsoft still trying to get a seat at the table.
Windows Phone was complicated, and all about the enterprise. The business model was all about selling more server licenses, and everyone having a phone that tied them into that ecosystem was good.
Once Apple put out a phone that normal (non-techy) people could use, it really was over. Their UI was much, much better, and although it had less features to start, all their features worked.
It was all downhill from there.
And yes, I agree with the story that culture was the real culprit:
> We know who/what killed Windows Phone, and it’s not Android. We could point fingers at one or more Microsoft execs as the culprits, but that misses the point: Microsoft culture did it. Culture is dangerous; under our field of consciousness, it sneakily filters and shapes perceptions, it’s a system of permissions to emote, think, speak, and do.
Haha this closing admission explains entirely the goofy anachronisms and non sequiturs that comprise the rest of TFA. The dream of windows on the phone could have come true, if only it had been a decent phone OS, before either of the two actual decent phone OSes had been introduced, and also it had been completely free... JLG has lots of uncles but no aunts.
We still make fun of my brother's Lumia phone, that he "got for really cheap". Why was that, I wonder?