News

Xamarin's Impact on the Death of Project Astoria

Predictably, Microsoft has pulled the plug on the Windows Bridge for Android, now that the company is absorbing Xamarin. Xamarin's cross-platform development capabilities can already be used to port Windows apps to the Android marketplace.

The writing has been on the wall for some time for Project Astoria, Microsoft's Windows Bridge for Android. And with Microsoft's plan to acquire Xamarin, it looks like the project has been killed. That's according to Kevin Gallo, Vice President of the Windows Developer Platform, who blogged on the status of the project last week.

"We received a lot of feedback that having two Bridge technologies to bring code from mobile operating systems to Windows was unnecessary, and the choice between them could be confusing," said Gallo."We have carefully considered this feedback and decided that we would focus our efforts on the Windows Bridge for iOS and make it the single Bridge option for bringing mobile code to all Windows 10 devices, including Xbox and PCs." Gallo said that developers who "spent time investigaing the Android bridge" should look at Xamarin's solutions moving forward.

While lots of developer and community activity surrounded the bridge projects, like Project Islandwood for iOS, after they were introduced at the company's Build event in late April/early May 2015, Astoria had faced a number of setbacks soon after it was introduced. Even as Microsoft solicited feedback and community involvement, it already appeared that work on that specific bridge piece had effectively gone dark just a month later. Comments related to a May 10 post about the project that went unanswered only fueled speculation.

That speculation crested in November, when a report from Windows Central, which is cited in this Redmondmag.com report from Chris Paoli, noted that "multiple inside sources have confirmed that the project has been put on hold and that 'the Android app porting is not going as planned.' "

What was causing the issues is anyone's guess, but a report from ADTmag.com's David Ramel pointed to several comments on Stack Overflow and Quora that called into question dodgy emulation performance, issues that Ramel confirmed in his own work with it. As Ramel noted at the time: "That's something I -- and thousands of other Java developers working on Android apps from a Windows machine -- could have confirmed ahead of time. Android emulation using the Eclipse IDE with the Android Development Tools (ADT) plugin was horrible."

For Gallo to suggest that developer who want to continue working with Windows-to-Android app porting start to use Xamarin is a good indication that Microsoft no longer intends to ignore this important apps niche.

About the Author

You Tell 'Em, Readers: If you've read this far, know that Michael Domingo, Visual Studio Magazine Editor in Chief, is here to serve you, dear readers, and wants to get you the information you so richly deserve. What news, content, topics, issues do you want to see covered in Visual Studio Magazine? He's listening at [email protected].

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube