Skip to content

Latest commit

 

History

History
22 lines (18 loc) · 1.85 KB

File metadata and controls

22 lines (18 loc) · 1.85 KB

Design Context

Users

IT technicians managing fleets of endpoints (primary), IT managers reviewing dashboards (secondary). Techs are often multi-tasking across monitors, triaging alerts, running scripts, remoting into machines. They need information density without overwhelm. Managers need quick status reads.

Brand Personality

Fast, reliable, approachable. Breeze should feel like a calm control center — not frantic, not sterile. Confidence-inspiring without being corporate or cold. The name "Breeze" implies effortlessness.

Aesthetic Direction

  • Tone: Business/professional with warmth. Think: competent colleague, not enterprise software.
  • Reference: NinjaOne — clean, functional, professional RMM UI. Take inspiration from the clarity and information hierarchy, not the specific visual language.
  • Anti-reference: AI vibe-coded aesthetics — gradient text, glassmorphism, neon-on-dark, identical card grids, generic system fonts with no personality. The current UI acknowledges this is the starting point to move away from.
  • Theme: Light mode primary, dark mode supported. Both should feel intentional.
  • Typography: Open to evolving beyond system defaults. Should feel professional but not generic.
  • Color: Open to evolving beyond default blue. Should support status semantics (green/red/orange/yellow) clearly.

Design Principles

  1. Calm control — Reduce cognitive load. Surface what matters, hide what doesn't. No visual noise.
  2. Information-first — Data density over decoration. Every pixel should earn its place.
  3. Instantly scannable — Techs glance, they don't read. Visual hierarchy must be ruthless.
  4. Professionally warm — Not cold enterprise, not playful startup. Competent and approachable.
  5. No AI tells — Every design choice should look like a human designer made it deliberately.