According to https://mspoweruser.com/around-3-million-americans-still-hanging-windows-phones/
There was a time when Windows Phones held around 45% market share in USA. That was obviously a long time ago,
How Microsoft ruined Windows Phone and Windows Mobile?
If Microsoft build the UWP-like app ecosystem at the beginning of Windows Phone 7, which can run both old Windows Mobile 6 app and UWP-like app(compatible with windows 8.0 store app) , then the Mobile OS world would be much different from what it looks like now.
Question: Does Microsoft lost Mobile OS permanently? or there's still hope for Surface Phone?
@birbilis Thanks for share so many info.
Indeed, MS should give us clear plan/roadmap for .Net/XAMl, but they don't.
Microsoft abandon lots of technologies, Foxbase, J++, Windows Mobile, Windows Phone 7/8/8.1, Window RT, Silverlight, BizTalk.... They do not have clear strategy, and changes frequently.
If my memory is good, Bill Gates has an ambitious plan to write whole Windows with C# at the begging of year 2000.
May MS do not really want C#/XAML to be cross-platform, this suggestion has marked as "UNDER REVIEW" more than a year ago, and still have no more message from MS.
What we need is a universal framework, that write code once, run everywhere.
And with webGL/Html5 Canvas, there's a lot of new Library that can build Windowing system in web browser (see links below), that is , cross-platform UI system could be build with JS at the same time.
So, it looks Js has more brilliant future than .Net language (C#/VB/F#)?
(Don't get me wrong, I personally love C# much more than JS.)
thanks, Mike EEE, I know that is .Net Std 2.0. I mean MS should unify the name for .net framework.
Microsoft shoud discard mono after they acquired Xamarin, or at least merge Mono into .Net Core or .Net Framework, make just only ONE .net runtime/framework for every platforms (Windows classic , store app, ANdroid, Linux, MacOS...) They can have multipal implementation of .Net framework for different OSes, but from the developers point of view, they are all have the same BCL/API. for hardware/device specific APIs， I think this could be solved by additional Assemblies/Packages, such as iOS.dll, Android.dll.
After Google Chrome, Mozilla Firefox 52 will support web assembly on March 7:
====The major Web platform changes for Firefox 52 are Web Assembly and CSS Grid.
.Net renaissance, .net developers are live in a best era (soon)!
.Net standard 2.0 and .Net core 2.0 will be released this year (2017), I believe .net developers will go to a brilliant page in the book of .net history.
@MS, The next step is cross-platform xaml, don't forget it.
Google Chrome since v58 supports Web Assembly, that was released almost a month ago.
So, as Chrome has more than 50% market share, half of web browsers is ready for wasm.
@anonymous, totally agree with you.
Microsoft can build a basic (virtual) windows GUI engine, draw every thing from scratch.
The windows engine is responsible for draw window, button, checkbox, list-box (every windows widgets), Then, consume different operating system (or runtime)'s (such as Android, iOS, Windows legacy, windows 10 (for store app), as well as HTML5 canvas) draw 2D functions, MS can build a common GUI system, that can share everything for different OS/runtime and keep the same look and feel of the UI.
They have 30+ years experience (since MS-Window 1.0) for build GUI system + message system, this is not difficult for them.
WinJS has *already for a long time* stopped add new features, and go into maintenance status.
That indicates though JS+CSS+HTML is good for web site, but not suite for Application development. No one willing write apps with JS (or even TypeScript).
Instead, C#+XAML is promising! WebAssembly is almost ready to go, it's time to build a brand new web application runtime model, that is translate C#+XAML to wasm+html5Canvas (or webGL), code once, run everywhere (Windows Desktop, UWP, Xamarin, Web).
Microsoft is preparing Web Assembly for their Edge Browser:
Electron, another JS/HTML library for build cross-platform desktop apps.
It's time for Microsoft to beat back with .Net/C#/VB for really cross-platform apps development!
Why Microsoft not put Silverlight Runtime (or another .Net Rumtime) into the Edge browser at the beginning? if they did, the world may different, we could run UWP applications directly in the browser.
+1 @Roger good point!
Yes, we need single codebase that can run everywhere (or as many as it can).
Windows Phone failed as Satya Nadella admits (http://www.deccanchronicle.com/technology/in-other-news/180616/microsoft-ceo-satya-nadella-admits-windows-phone-a-failure.html ), so *may* ***'s time for MS to do their plan B, create their own Android brand, something like Microsoft Android, the MS android is based on Android open source OS, and has a windows API layer that can run all UWP applications and support download apps from android and windows app stores.
I know MS is design their Surface Phone, but if they insist target for business users with high price, obviously Surface Phone cannot save windows 10 mobile.
I'm in China, mainstream Android Devices in price range of 1000-3000 RMB (about 160$ - 500$), and the 160$ phones has very high hardware equipped and can run any business apps, who will buy a 600-900$ surface phone with less apps ready to run?
The world is change quickly, many people do not use PCs anymore and take a smart phone for daily works instead. If MS lost mobile OS, it will become a new SUN after 10 years.Anonee supported this idea ·
Xamarin's cross platform solution is good, but is far from perfect. There's still a lot of work need to do, I hope MS can integrate Xamarin forms into UWP in the roadmap of .Net Core 2.0, a really UWP that target different OSes much more smoothly with just one project only, and select build to Windows/iOS/Android/Linux as easy as we target different CLR (.net 4.0/.net 4.5) currently, that needs MS to build an universal .Net runtime/API for all the supported OSes.
So, I believe acquisition Xamarin is not the end, but a new start point.