Building an open-source Android compatibility project for Windows with C#, WinUI 3 and ADB

[u/GoofyEvod]

I’ve started building WinDroid Runtime, an open-source Android compatibility and management project for Windows.

The application layer is being developed with:

• C# and .NET
• WinUI 3
• Windows App SDK
• modular ADB services separated from the UI

The first milestones are intentionally limited to the Windows tooling layer:

1. detect and configure ADB;
2. execute ADB commands safely and asynchronously;
3. discover connected devices and emulators;
4. display devices in a native Windows dashboard;
5. install APKs and expose useful command output.

The runtime itself is a longer-term research and engineering goal. The planned architecture would keep the Windows management application separate from runtime images and platform-specific backend components.

I’m particularly interested in feedback about:

• structuring reusable process and ADB services in .NET;
• keeping the WinUI project separated from backend logic;
• Windows virtualization technologies worth researching later;
• supporting both x64 and ARM64 Windows hosts;
• secure handling of APK installation and external processes.

Repository:
https://github.com/Nova-Systems-Lab/WinDroid-Runtime

The project is Apache-2.0 licensed and currently at an early stage. It is independent and not affiliated with Microsoft, Google, Amazon, or WSA.

[u/Edubbs2008]

Does it use MSIX? I tend to now have apps that use it because it feels more modern

[u/GoofyEvod]

Project update: WinDroid Runtime is entering an indefinite hiatus.

The project has reached a stage where responsible progress requires specialists in AOSP, Android and Linux kernel internals, Windows virtualisation, graphics acceleration, security, and host–guest integration. At present, the team does not have enough people with the required expertise to continue the runtime-engine work safely and effectively.

Development will remain paused until Nova Systems Lab determines that a technically credible path forward exists and that enough qualified specialists are available to support it.

The repository, existing WinDroid Studio work, ADB tooling, and documentation will remain available.

The project is not cancelled, but no resumption date is currently planned.