Microsoft Ends Effort To Bring Android Apps To Windows 10 Mobileby Brandon Chester on February 25, 2016 4:50 PM EST
- Posted in
- Windows 10 Mobile
At the 2015 BUILD developer Conference Microsoft demoed four application bridges that they hoped would improve the number of applications available for Windows 10 Mobile, which would benefit the Windows platform as a whole. The two most interesting showcases were Project Islandwood, which helps developers to port their Objective-C applications to Windows, and Project Astoria, a subsystem for running existing Android applications right on a Windows smartphone. Today it looks like the latter of those projects has officially met its end.
The death of Project Astoria won't come as a big surprise to those who have been keeping track of Windows 10 Mobile's development process since BUILD. Back in October of last year, preview builds of Windows 10 Mobile stopped including the Android runtime and there wasn't really any explanation as to why. Since that time, Project Islandwood has continued to be promoted by Microsoft while there hasn't been much news about Astoria. This led many in the development community to suspect that Microsoft had decided to kill the project, although there was no official confirmation until today.
In my view, the death of Project Astoria has both good and bad elements. Since it was essentially packaging Android applications to run on Windows 10 Mobile, the applications never fit in with the rest of the platform and so the question then became why you wouldn't just go buy an actual Android device. On the other hand, it did provide an easy way for developers and users to bundle up applications that didn't exist at all on Windows 10 Mobile, which would help fill the app gap in a less than optimal but usable manner.
Source: Microsoft Windows Blog
Post Your CommentPlease log in or sign up to comment.
View All Comments
DerekZ06 - Friday, February 26, 2016 - linkIt all makes sense now, why you think c# is slow. You're looking at C# compiled for the Mono VM and mistakingly concluding that C# compiled to Microsofts CLR VM is slow. C# on CLR (windows) is is very fast.
lmcd - Friday, February 26, 2016 - linkHe's also ignoring that Roslyn is bringing .NET to Linux. No doubt, Android will be a follow-up target of that particular branch of .NET.
lilmoe - Thursday, February 25, 2016 - link"even slower than Java"
"result in applications which are not portable"
That behind of yours sure talks big...
ddriver - Thursday, February 25, 2016 - linkUnlike yours, which only talks silly ;) Performance figures can be empirically proven, it is not a matter of subjective opinion, if you have something factual to say on the subject - put up or shut up.
MartenKL - Friday, February 26, 2016 - linkDDriver, didn't see you post actual benchmarks on mobile devices. C# does pretty well on iOS according to this post https://medium.com/@harrycheung/mobile-app-perform...
Guspaz - Friday, February 26, 2016 - linkPerformance can be proven, but only with relevant comparisons. Comparing the performance of C++ to a third-party .NET runtime (Mono) is not indicative of the performance of the official runtime or pre-compiled C# code.
The_Assimilator - Friday, February 26, 2016 - linkYour posts show an amazing lack of understanding of how C#/.Net actually work.
lmcd - Friday, February 26, 2016 - linkQt shill. Yes, it's a great toolkit, but it's not exactly Christ-like.
ddriver - Saturday, February 27, 2016 - linkI am one of the most vocal Qt critics, and unlike most of its user base, I have no problems admitting that it sucks, and the only reason I use it is that it is the least sucky solution.
boozed - Saturday, February 27, 2016 - linkCalling someone a "shill", the new corollary of Godwin's Law.