Microsoft's Project Astoria and Android app emulation not happening anytime soon


Recommended Posts

During Microsoft's Build conference earlier this year the company announced their software Bridges for developers. Now the future of one of those bridges is uncertain.

These tools were to help developers port their software to Windows 10 and Windows 10 Mobile and were broken down into four projects, including:

  • Project Westminster - For porting Web apps
  • Project Centennial - For portingClassic Win32 apps
  • Project Islandwood - For porting iOS apps
  • Project Astoria - For emulating Android apps

The idea behind the bridges is to aid in closing the so-called 'app gap' on Windows and Windows Phone. However, while consumers would reap the benefits, Windows developers were not at all pleased with the announcement. The reason comes down to Project Astoria, which was the most controversial due to its implementation.

What is Astoria?

Reports of running Android apps on Windows 10 go back to 2014 including a report by Mary Jo Foley and a report by Tom Warren from February 2014.

Astoria is an Android emulator meaning devs do not have any real work to do. Instead, the phone ran the Android APK file directly. Early Insider builds of Windows 10 Mobile had this layer in the OS letting consumers sideload APK files directly. Not only did this project make app piracy easy, it undercut Windows developers who would have little reason to make native Windows apps anymore.

windows-10-platform2.jpg?itok=7JjKUuPi

Astoria was never released to developers openly. Instead, they had to apply to test out the tools, which were still under development. Developer feedback and their experiences would be gathered in a closed forum found at bridgeforandroid.windows.com. At the time of this report, the Astoria landing page to apply was still active.

Project Astoria was a brute-force solution to a persistent problem for Windows and Windows Phone. However, it may have been too brazen even for Microsoft.

Astoria status – 'Not going as planned'

Windows Central is now hearing from multiple sources that Project Astoria is on hold indefinitely, and maybe even shelved completely. Although Microsoft is not publicly — even privately — stating Astoria is cancelled, they are not openly talking about it anymore, or even privately discussing it with developers.

One source has told us that "the Android app porting is not going as planned."

The interpretation by others familiar with the matter is that Astoria is not happening anytime soon and Microsoft has yet to find a way to announce the news publicly. Indeed, while the news will be welcomed by Windows developers, it could come across as a failure by the company to execute on a publicly announced strategy.

Android_vs_Lumia_630.jpg?itok=boe3w-pW

Additional evidence supporting this conclusion comes from various sources besides the ones we spoke to, including:

  • The Project Astoria forums have gone silent since September with developer questions unanswered by Microsoft, including inquiries about the project's future
  • Recent Windows 10 Mobile Insider builds have had the Android subsystem completely removed including build 10586 (commercial shipping release)
  • Microsoft is no longer openly talking about the project even to those under NDA

There could be a few reasons as to why Astoria has been unsuccessful. Some of the people we have spoken too did not know the exact motive for the delay, although they did have some ideas, including:

  • Pushback – Developers were very unhappy about Astoria
  • Technical – There are reports that the Android subsystem caused Windows 10 Mobile to slow down over time
  • Legal — It is not clear what, if any, legal ramifications there in such an approach

Update: One other reason we have heard since publishing is that the Astoria team was 60-80 people versus the 5 it took for Islandwood. In the end, it may have been economic hurdles as much as technical ones.

Project Islandwood for porting iOS apps requires the apps to be recompiled, but it also needs developer intervention. Islandwood is for Objective-C and it follows a history of Microsoft supported programming languages. Astoria, however, was straight up emulation and could run into all sorts of legal and technical issues.

As to the status of Projects Islandwood, Westminster and Centennial, we hear those are all still happening — and with notable positive discussion about Islandwood. In fact, Facebook's upcoming universal app for Windows 10 looks to be an iOS port.

Perhaps not too surprisingly, none of the developers we spoke to were upset at Astoria's possible demise.

The future

We've reached out to Microsoft about our findings and a spokesperson provided the following statement:

"We're committed to offering developers many options to bring their apps to the Windows Platform, including bridges available now for Web and iOS, and soon Win32. The Astoria bridge is not ready yet, but other tools offer great options for developers. For example, the iOS bridge enables developers to write a native Windows Universal app which calls UWP APIs directly from Objective-C, and to mix and match UWP and iOS concepts such as XAML and UIKit. Developers can write apps that run on all Windows 10 devices and take advantage of native Windows features easily. We're grateful to the feedback from the development community and look forward to supporting them as they develop apps for Windows 10."

What this all means for the future of Windows Phone and closing the app-gap remains to be seen. Certainly Astoria offered a massive shortcut to getting new apps onto Windows Phone solving at least one problem. However, it did rely on developers giving consent to having their apps ported to the Windows Store, something that was not guaranteed to happen. Additionally, Microsoft stood a good chance of alienating its own developer base should the project be successful. On the other hand, Project Islandwood for iOS apps may be a better route — the iOS App Store is full of quality apps and recompiled apps will perform and behave better on Windows 10, not to mention the lesser potential for abuse compared to straight emulation.

Whether Microsoft revives Project Astoria depends on the real reasons for its end and whether those can be overcome. For now, however, it looks like Android apps are not coming to Windows 10 Mobile anytime soon.

Source: http://www.windowscentral.com/microsofts-project-astoria-delayed

Phones late + priced to high + Windows 10 Mobile buggy + no Android app compatibility = Purchase of Nexus 6P to upgrade my Nexus 5

Good job Microsoft...

"Developers were very unhappy about Astoria"

Microsoft could have literally herded all of the Windows Mobile app developers in one room then shot them in the head and just have them replaced with new developers with better attitudes. /s

Edited by oldtimefighter

Project Islandwood is alive and well - http://twitter.com/tomwarren/statuses/665273632709591040. Looks like Facebook is using it for their Win10 universal app:

Screenshot_(40).thumb.png.7768e303d5bc0d

 

Personally, I could care less. I'd rather native universal apps. Android apps have zero appeal to me.

Edited by Dot Matrix

Project Islandwood is alive and well - http://twitter.com/tomwarren/statuses/665273632709591040

Personally, I could care less. I'd rather native universal apps. Android apps have zero appeal to me.

Me, I'd love to be able to run Android apps on my Windows Phone. Though the important (to me) stuff is available for WP.

But my preferred phone OS coupled with games that likely will never be released for Windows? Yes please! I don't know why you're so against the idea - it isn't like you'd be forced to use the Android apps.

I'm not going to complain. As long as I use a Windows Phone, I want native Windows widgets.

Definitely preferred I agree, but I still wouldn't mind being able to play Doctor Who Legacy on my phone.

That's the only reason I'm even slightly interested in this project - Android games. Everything else I want to do on my phone I can already.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Free Software Foundation Europe pushes EU to force Google to allow AI uninstalls on Android by Paul Hill Credit: Pexels Users should be able to fully uninstall AI-based features from Android devices and be able to access interoperability functions, free from Google’s verification requirements, the European Commission has heard as part of an Android interoperability consultation under the Digital Markets Act. These measures were proposed by the Free Software Foundation Europe (FSFE) last week when it submitted its documentation. The FSFE noted that Google had started silently installing AI models without telling users. It noted that the EU’s DMA requires companies like Google to allow users to uninstall pre-loaded software from their devices, but in the case of the AI models Google is installing, they reinstall if you delete them, contravening the DMA. To get Google back under control, the FSFE has told the European Commission that there needs to be improvements within the Android Open Source Project (AOSP). First, it said that users should be able to fully remove pre-loaded AI components from their devices, with companies being prohibited from silently reinstalling or reactivating them. Second, access to Android interoperability features should not be contingent on registration, authorization, or contractual relationships with Google. This pertains to Google’s attempt to force developers to register with Google, even to publish apps to alternative app stores like F-Droid. Discussing its submission, Lucas Lasota, FSFE Legal Programme Manager, said: Google is planning to roll out its Android Developer Certification in September 2026. This will force every Android app developer to register with Google before their software can be installed on certified Android devices, but it should affect those who have removed Google Apps from their device. The program is controversial because it entails the signing of contracts and payment of account fees to Google, as well as the handing over of the identities of developers. It said: The FSFE said that if the Commission’s draft measures remain unchanged, then Google will be allowed to make developers verify their identity. The FSFE believes that asking developers to register is contrary to the text and spirit of the law. In summary, the FSFE has told the Commission that no developer should need a Google account, a Play Store presence, or any agreement with Google to access Android’s interoperability features.
    • You could disable this "functionality/feature/whatever" with 2 registry keys, ages ago.
    • My Photos app is version 2026.11050.1001.0 and it remembers the window size and position. My Snipping Tool is version 11.2602.49.0 and it can capture the taskbar.
  • Recent Achievements

    • Conversation Starter
      sumytbe earned a badge
      Conversation Starter
    • One Year In
      B4dM1k3 earned a badge
      One Year In
    • One Year In
      DarkWun earned a badge
      One Year In
    • Dedicated
      Almohandis earned a badge
      Dedicated
    • Dedicated
      JuvenileDelinquent earned a badge
      Dedicated
  • Popular Contributors

    1. 1
      +primortal
      519
    2. 2
      +Edouard
      184
    3. 3
      PsYcHoKiLLa
      87
    4. 4
      Michael Scrip
      81
    5. 5
      Steven P.
      72
  • Tell a friend

    Love Neowin? Tell a friend!