desktop-native-designlisted

# Desktop Native Design Own one product-specific visual thesis while respecting genuine desktop behavior. Desktop-native is not responsive web at a wide viewport. ## Start with product and environment Inspect product, audience, tasks, content, incumbent interface, brand, stack, target operating systems and versions, window model, input methods, accessibility, system integrations, and current changes. Treat Electron, Tauri, Flutter, Qt, .NET, Avalonia, MAUI, and Java as implementation contexts, not visual identities. Proceed when requirements and direction are sufficient. Otherwise inspect first, then ask one focused batch about target systems, primary jobs, density, command model, document lifecycle, identity, integrations, and non-negotiable conventions. When examples exist, extract their system rather than cloning surfaces. When direction is delegated, state material assumptions and choose. Read [references/platform-behavior.md](references/platform-behavior.md) when platform behavior, windows, commands, documents, system integration, adaptation, or accessibility affects the result. For operational information design, read [../frontend-design/references/operate-and-dashboards.md](../frontend-design/references/operate-and-dashboards.md). ## Commit to one desktop direction Define product thesis, hierarchy and primary action, density, window and command model, typography, color, geometry, material, imagery, motion, signature, platform commitments, adaptation, lifecycle/r