Buzz
Most smartphones in today's market run on either Android or iOS. However, a few years ago, Microsoft also entered the game with Windows Phone and Windows 10 Mobile.
Windows 10 Mobile represents the final effort of the Redmond giant to capture attention in the mobile operating system market. W10M boasts a unique Live Tile interface, a distinctive desktop mode when connected to an external screen, and support for Windows Universal apps. Unfortunately, the Achilles' heel of this operating system remains unchanged since the Windows Phone era—the severe lack of apps compared to Android and iOS. This critical factor led to the downfall of the platform. However, little did we know that Microsoft had once explored a project nearing completion to support Android apps directly on Windows 10 Mobile.Astoria Project
Initially, Microsoft undertook various projects to port software from different platforms to W10M. They referred to these projects as software 'bridges,' with the aim of helping developers easily port their applications from Windows, iOS, and Android to W10M.
The first 2 'bridges,' codenamed Project Islandwood and Project Centennial, were designed to port apps from iOS and Windows. These projects were brought to light, leaving the remaining project undisclosed.
The third 'bridge,' codenamed Project Astoria, faced unfortunate circumstances and was withdrawn from W10M before its commercial release. However, the Android sub-system was already present in preview builds of W10M at that time, giving us a glimpse of what this OS could achieve back then.
Subsequently, Microsoft decided to cancel Astoria
Unfortunately for enthusiasts and Windows Phone users who always hoped for more apps for their smartphones, Microsoft chose to cancel Project Astoria before the official release of W10M in 2015.We have received numerous feedback stating that using two Bridge technologies to bring code from mobile operating systems (Android and iOS) to Windows is unnecessary, and the choice between them can be confusing
Another hypothesis is that Microsoft abandoned Astoria because it posed a threat to its Universal Windows App initiative, and native apps took full advantage of all the features of Windows Phone, such as Live Tiles, Metro UI... Ultimately, preview builds of W10M containing the Android sub-system could run many APK files without any modifications and did not officially materialize.
Ars Technica also suggested that Microsoft might have scrapped Astoria to avoid legal troubles with Google. Specifically, Microsoft planned to create a 'clone' of Google's APIs not present in AOSP, but this would attract legal scrutiny as the lawsuit between Google and Oracle over Android was quite tense at that time.
While Project Astoria wasn't supported in the official W10M version, there's no assurance that W10M would still exist if Microsoft had taken the opposite route. BlackBerry 10 also proudly supported Android apps similarly when it launched in 2013. Despite later improvements to better support Android apps, BlackBerry still discontinued its platform to fully transition to 'pure' Android in the following years.
However, the legacy of Astoria still lingers; a Microsoft engineer confirmed that the Linux subsystem on Windows 10, allowing the execution of Linux tools and command-line programs on PC, originated from the activities of the Bridge tool for porting Android apps to Windows in the past.
At present, there are still unofficial solutions to activate Project Astoria on W10M, although the process is quite complex. Even though Astoria is no more, its presence serves as a clear reminder of how Microsoft's ill-fated mobile operating system once had its 'potential' 😊Source: AndroidAuthority
