-
Notifications
You must be signed in to change notification settings - Fork 1
Add connected-device details panel #31
Copy link
Copy link
Open
Labels
adbWork involving Android Debug Bridge integration, device communication, commands, and diagnostics.Work involving Android Debug Bridge integration, device communication, commands, and diagnostics.enhancementNew feature or requestNew feature or requesthelp wantedExtra attention is neededExtra attention is neededphase-1Work planned for the first development phase and initial usable project foundation.Work planned for the first development phase and initial usable project foundation.winuiWork related to the WinUI 3 desktop interface, windows, controls, styling, and user experience.Work related to the WinUI 3 desktop interface, windows, controls, styling, and user experience.
Milestone
Description
Metadata
Metadata
Assignees
Labels
adbWork involving Android Debug Bridge integration, device communication, commands, and diagnostics.Work involving Android Debug Bridge integration, device communication, commands, and diagnostics.enhancementNew feature or requestNew feature or requesthelp wantedExtra attention is neededExtra attention is neededphase-1Work planned for the first development phase and initial usable project foundation.Work planned for the first development phase and initial usable project foundation.winuiWork related to the WinUI 3 desktop interface, windows, controls, styling, and user experience.Work related to the WinUI 3 desktop interface, windows, controls, styling, and user experience.
Type
Fields
No fields configured for issues without a type.
Projects
StatusShow more project fields
Backlog
Summary
Create a WinUI panel that displays detailed information about the currently selected Android device or emulator.
The panel should update when the user selects a device from the connected-device list and should handle missing, disconnected, or partially identified devices safely.
Background
The dashboard device list provides an overview of connected targets.
A separate details panel will make the interface more useful by showing structured information without overcrowding the main list.
Dependencies
This issue depends on:
The details panel should consume the structured device model rather than parsing ADB text itself.
Information to Display
Display available values such as:
Only display values that are actually available.
Missing values should use a neutral representation such as:
Avoid displaying misleading invented values.
UI Requirements
The details panel should include:
The panel should follow the existing WinDroid Studio visual style.
Selection Requirements
When the user selects a device:
When the device list refreshes:
Tasks
Accessibility Requirements
Out of Scope
This issue does not need to:
Acceptance Criteria