Device Profile Launcher
The UI effectively uses a dark theme with clear typography and distinct grouping to separate device selection and profile options, enhancing readability. However, improvements are needed in button prominence and affordance, and more guidance or tooltips could help users understand profile impact better.
Public

Design Score
Polish Opportunities
Design Perspectives
0To Review
Recommended Fixes by Impact
0Total
Fixes by Category
4
Color & Contrast1
Content Readability & Clarity2
Visual Consistency, Imagery & Media1
Navigation & Structure2
Conversion & Actions0
Tone, Friendliness & Delight3
Accessibility & Input Ergonomics3
Efficiency & Cognitive Load3
Flow & States Completeness2
Strategic DesignRecommended Fixes by Impact
1Critical
8Major
11Moderate
2Minor
No Enabled Start/Connect Button for Launching Connection
Critical
Flow & States Completeness
The Problem
The 'scrcpy starten' (start scrcpy) button at the bottom right is disabled and there is no alternative enabled option visible to proceed with launching the connection after choosing a device and profile.
Why it Matters
Users cannot proceed to connect to or control the device, which is the primary purpose of this interface, creating a critical dead-end.
How to Fix
Enable the 'scrcpy starten' button once a device and profile are selected or provide feedback on what is missing to enable the button.
Issue Highlights
Disabled button text contrast too low
Major
Color & Contrast
The Problem
The text 'scrcpy starten' on the bottom right button appears disabled in a low-contrast grey on dark background, likely below WCAG AA contrast levels for normal text.
Why it Matters
Users may not clearly perceive that the button is disabled or even that it is a button, reducing clarity and usability.
How to Fix
Ensure disabled state text conforms to at least 3:1 contrast minimum or distinguish the disabled state with more than just color (like opacity or icon change).
Issue Highlights
Low contrast for non-primary text in left sidebar
Major
Color & Contrast
The Problem
The grey text 'Suche nach Geräten ...' in the left sidebar has low contrast against its dark background, likely below WCAG AA 4.5:1 contrast ratio for normal text.
Why it Matters
Users with mild visual impairments or in poor lighting conditions may have difficulty reading this text, reducing the usability of the device search feature.
How to Fix
Increase the contrast by using a lighter grey or white color for the text or darken the background color further.
Issue Highlights
Low contrast for secondary text under device name
Major
Color & Contrast
The Problem
The secondary text 'Smartphone · WLAN' below 'SM-S908B' on left panel and in top center panel appears in a muted gray tone on a dark background, likely failing WCAG AA contrast ratio.
Why it Matters
This text is important device information, and poor contrast can make it difficult for users to read, especially users with visual impairments or in low-contrast situations.
How to Fix
Use a lighter text color or increase background darkness to ensure at least 4.5:1 contrast ratio.
Issue Highlights
Profile cards not horizontally aligned
Major
Visual Consistency, Imagery & Media
The Problem
The profile cards labeled 'Balanced', 'Low Latency', and 'High Quality' are not perfectly aligned along the top edge; the 'Low Latency' card appears slightly lower.
Why it Matters
Misalignment increases cognitive load and creates a less polished, less professional user experience.
How to Fix
Adjust the vertical positioning of the profile cards to ensure they share a consistent top baseline.
Issue Highlights
Primary action button label 'scrcpy starten' is disabled and not prominent
Major
Conversion & Actions
The Problem
The primary call-to-action button labeled 'scrcpy starten' is visible but disabled (greyed out), reducing clarity on when and how users can start the main operation. It also visually lacks prominence compared to the other smaller buttons, which might confuse the user about the primary next step.
Why it Matters
Users might be uncertain about how to proceed to start or activate the main feature, potentially causing frustration or delay in task completion.
How to Fix
Enable the primary action button when appropriate and ensure it stands out visually as the main call to action, with clear label and distinct style from secondary buttons.
Issue Highlights
Lack of Clear Call to Action for Profile Selection
Major
Flow & States Completeness
The Problem
The screen displays three profile options (Balanced, Low Latency, High Quality) for the selected device, but there is no explicit button or instruction indicating what happens after selecting a profile or how to proceed to the next step.
Why it Matters
Users may be confused about what to do after selecting a profile, leading to hesitation or abandonment since no clear next step is provided.
How to Fix
Add a clear call-to-action button (e.g., 'Start', 'Connect', 'Apply Profile') once a profile is selected, or provide instructions to clarify the next step.
Issue Highlights
Unclear actionable affordance for profile selection
Major
Strategic Design
The Problem
Profile cards do not provide clear interactive affordance such as hover or selection states, making it unclear if users can click to select or what the current selection is.
Why it Matters
Users may be uncertain about how to choose or switch profiles, causing confusion or errors in setup.
How to Fix
Add clear visual feedback for clickable profile cards including hover effects and selected state styling to indicate user interaction possibilities.
Issue Highlights
No Feedback for Device Search or When No Devices Found
Major
Flow & States Completeness
The Problem
The left sidebar shows a device list and a search bar, but no indication of loading, no devices found, or guidance if no devices are detected.
Why it Matters
Users may be unclear if devices are being searched for or if none are found, causing confusion and uncertainty about what actions to take.
How to Fix
Add empty state messaging or feedback (e.g., 'Searching for devices...', 'No devices found. Please connect a device or refresh.')
Issue Highlights
Lack of clear active state or breadcrumb for current selection
Moderate
Orientation Missing (Environment/Role/Location)
The Problem
The left sidebar lists devices with one device highlighted (SM-S908B), but there is no distinct visible active state or breadcrumb that explicitly indicates the current context or navigation hierarchy beyond the selection highlight. The right pane shows profile options, but it is not visually clear how these are related to the left selection in terms of navigation context or role.
Why it Matters
Without a clear indication of where the user is within the navigation hierarchy or environment, users may get confused about their current location or role, especially when multiple devices or profiles are involved.
How to Fix
Enhance the active state with more prominent visual cues or add breadcrumbs or headers that explicitly label the navigation context and clarify the relationship between side pane selections and the main content area.
Issue Highlights
Multiple Profile Options Require Extra User Decision
Moderate
Efficiency & Cognitive Load
The Problem
Users must choose between three similar profiles (Balanced, Low Latency, High Quality) with technical details under each, which may be confusing without clear guidance on differences.
Why it Matters
This extra decision step can slow down users and increase cognitive load, especially if they are not familiar with the technical terms.
How to Fix
Provide clearer explanations or default selections based on common use cases to reduce the burden of choice.
Issue Highlights
Insufficient visual hierarchy for device and profiles
Moderate
Strategic Design
The Problem
The sections for device selection and user profiles have similar styling and low visual contrast, making it hard to quickly distinguish the main focus areas on screen.
Why it Matters
Users may struggle to quickly identify where to focus for important actions, reducing efficiency and satisfaction.
How to Fix
Increase visual contrast between the device list and the profile selection by using clearer section headings or different card styling. Consider adding stronger emphasis to the selected device and active profile.
Issue Highlights
Low contrast for descriptive profile details
Moderate
Color & Contrast
The Problem
The smaller secondary text under each profile title ('1920 / 8M / stay-awake', etc.) in the center profile cards is a muted gray on dark background, likely with insufficient contrast to meet WCAG AA for normal text.
Why it Matters
Important details about the profile settings are harder to read for users with mild visual challenges, potentially causing confusion.
How to Fix
Lighten the text color or slightly darken the card background to ensure sufficient contrast ratio (4.5:1).
Issue Highlights
Insufficient visual distinction between section headers and content
Moderate
Content Readability & Clarity
The Problem
The section headers like 'Launcher' and 'Profile' use the same font size, weight, and color as other nearby text, which results in a weak visual hierarchy making it harder to distinguish sections at a glance.
Why it Matters
Users may struggle to quickly scan and understand the structure of the interface, reducing usability and efficiency.
How to Fix
Use larger font size, bold weight, or distinct color for section headers to clearly separate them from the regular content text.
Issue Highlights
Inconsistent font weight and text size in buttons
Moderate
Visual Consistency, Imagery & Media
The Problem
The buttons at the bottom row have inconsistent font weights and some appear smaller or less bold (e.g., the 'scrcpy starten' button is lighter and different from others).
Why it Matters
Inconsistent button styles confuse users about interactive elements and harm the perceived quality of the UI.
How to Fix
Standardize font weight and size across all buttons in this row for a cohesive visual style.
Issue Highlights
CTA button 'Manuelles Setup anzeigen' has unclear action implication
Moderate
Conversion & Actions
The Problem
The button labeled 'Manuelles Setup anzeigen' (Show manual setup) at the bottom center is a standalone call to action but does not clarify what will happen or how it differs from the profile selection above. It may confuse users about its priority.
Why it Matters
Vague or unclear CTA phrasing can confuse users, leading to hesitation or abandonment of the workflow.
How to Fix
Provide more descriptive CTA text or additional context explaining the next step or benefit of clicking this button, to improve clarity.
Issue Highlights
Small buttons in the bottom bar
Moderate
Accessibility & Input Ergonomics
The Problem
The buttons labeled 'Aktualisieren', 'Shortcut-Sheet', 'GitHub', 'Log anzeigen', and 'scrcpy starten' are smaller than recommended tap target size (approximately less than 40x40 pixels) and may require precise tapping, especially on touchscreen devices.
Why it Matters
Small touch targets increase the likelihood of user errors and make it difficult for users to accurately tap on the intended button, leading to frustration and slower task completion.
How to Fix
Increase the size of each button to have at least 40x40 pixels of interactive area and ensure adequate padding inside and around each button to ease tapping.
Issue Highlights
Insufficient horizontal spacing between bottom bar buttons
Moderate
Accessibility & Input Ergonomics
The Problem
The horizontal gaps between the buttons in the bottom bar, such as 'Shortcut-Sheet' and 'GitHub', appear narrow, possibly less than 8-10 pixels, increasing chance of accidental taps on adjacent buttons.
Why it Matters
Close proximity of clickable elements can cause users to tap the wrong button unintentionally, increasing error rates and user frustration.
How to Fix
Increase horizontal spacing between buttons in the bottom bar to at least 8-10 pixels to improve touch accuracy and reduce accidental taps.
Issue Highlights
Manual Setup Option Adds Extra Step
Moderate
Efficiency & Cognitive Load
The Problem
The 'Manuelles Setup anzeigen' button adds an additional step for users who may want to avoid manual configuration but it's not clear if manual setup is necessary or optional.
Why it Matters
Extra steps complicate the process and may cause users to hesitate or abandon configuration if manual setup is confusing or unnecessary.
How to Fix
Offer a more integrated setup process or clearly indicate when manual setup is recommended or optional.
Issue Highlights
Small manual setup toggle button
Moderate
Accessibility & Input Ergonomics
The Problem
The 'Manuelles Setup anzeigen' button above the bottom bar is narrow and may have a low vertical tap size requiring precision.
Why it Matters
Small tap targets make it harder to activate the control, increasing the risk of user frustration and interaction errors.
How to Fix
Increase the vertical height and padding of the 'Manuelles Setup anzeigen' button to meet minimum touch target guidelines (around 40x40 pixels).
Issue Highlights
Multiple buttons at bottom lack spacing and grouping clarity
Minor
Navigation & Structure
The Problem
There are six buttons arranged in a single horizontal row at the bottom, with minimal spacing between some buttons and inconsistent grouping (e.g., 'GitHub' is visually grouped with 'Shortcut-Sheet', but other buttons are distributed unevenly). This causes slight visual clutter and difficulty in distinguishing groups or primary actions.
Why it Matters
Crowded button groups can cause hesitation and misclicks, reducing user efficiency and increasing cognitive load.
How to Fix
Introduce clearer visual grouping and consistent spacing between buttons, possibly organizing them into logical clusters or separated sections.
Issue Highlights
Technical Profile Details Create Clutter
Minor
Efficiency & Cognitive Load
The Problem
Each profile shows technical specs (e.g., resolution, FPS, stay-awake) that might overwhelm typical users without contextual or simplified explanations.
Why it Matters
This could distract or overwhelm users, making it harder to quickly select a suitable profile.
How to Fix
Use tooltips or collapsible explanations to simplify the information visible by default.
Issue Highlights