Skip to content

Milestones

List view

  • Add the first developer-focused diagnostic tools to WinDroid Studio. This milestone begins with a safe, responsive logcat viewer and may later include screenshot capture, file push and pull, basic ADB shell access, advanced log filtering, and exportable diagnostic reports. Developer tools must handle long-running ADB processes safely, avoid blocking the WinUI thread, prevent unbounded memory use, and avoid exposing or automatically uploading sensitive device logs.

    No due date
    0/1 issues closed
  • Document the project architecture and contribution workflow. This milestone should make it easier for new contributors to understand the repository structure, current scope, development workflow, and pull-request process.

    No due date
    1/3 issues closed
  • Build the first Android application-management workflow in WinDroid Studio. Users should be able to select and install APK files through ADB, view installed packages on a connected device or emulator, launch supported applications, uninstall packages with confirmation, and see clear command results in the output panel.

    No due date
    1/6 issues closed
  • Create the first usable WinDroid Studio interface. This milestone connects the WinUI 3 application to the ADB backend and displays connected devices, device states, command output, errors, and refresh controls. The goal is to produce the first demonstrable working application.

    No due date
    0/5 issues closed
  • Build the initial WinDroid Runtime foundation and ADB backend. This milestone establishes the .NET solution structure, ADB configuration, path detection, command execution, device enumeration, and output parsing. The goal is to have a tested backend capable of detecting ADB and returning structured information about connected Android devices and emulators.

    No due date
    2/10 issues closed