Skip to content

Latest commit

 

History

History
41 lines (23 loc) · 2.71 KB

PRODUCT.md

File metadata and controls

41 lines (23 loc) · 2.71 KB

Product

Register

product

Users

Icarus is for Valorant players, in-game leaders, coaches, and small teams who need a focused desktop workspace for planning rounds. They are usually reviewing maps, building strategies, marking utility, saving reusable setups, or preparing material to share with teammates.

The user context is practical and time-sensitive: they need to place agents, abilities, drawings, notes, images, and lineups quickly without the interface getting in the way of tactical thinking.

Product Purpose

Icarus is an interactive Valorant strategy and lineup tool. It exists to make strategy creation feel fast, local, organized, and easy to revisit. Success means a user can move from an idea to a usable tactical map with minimal friction, then save, organize, import, export, and refine that work over time.

The app should make complex strategy work feel manageable. The map and placed tactical objects are the main artifact; surrounding UI should support scanning, editing, and control without competing with the canvas.

Brand Personality

Minimal, intuitive, tasteful, and fast.

The product should feel refined and deliberate. Controls should look like they belong where they are placed, workflows should feel obvious after a short glance, and dense tools should remain calm enough for repeated use during planning sessions.

Anti-references

Icarus should not look disorganized, noisy, or arbitrary. Nothing should feel placed only because there was space for it. Avoid flashy color, novelty effects, cluttered panels, inconsistent spacing, and features that look shoehorned into the interface.

The app should not feel like a generic gamer overlay, a marketing page, or a decorative dashboard. It should not rely on loud gradients, excessive glow, glass effects, or visual noise to create excitement.

Design Principles

  1. Canvas first: the strategy map is the work surface, and every surrounding control should preserve focus on that surface.
  2. Every control earns its position: placement, grouping, and hierarchy should reveal why something is available at that moment.
  3. Fast beats ornate: common actions should be quick to find, quick to trigger, and visually stable.
  4. Refined density: the app can be tool-rich, but it should stay orderly, scannable, and calm.
  5. Tactical clarity: markings, agents, abilities, and annotations should be legible before they are decorative.

Accessibility & Inclusion

No formal accessibility target is currently defined. Use sensible product defaults: clear focus states, keyboard-friendly controls where practical, readable contrast in the dark interface, reduced-motion respect for nonessential transitions, and color choices that do not make tactical meaning depend on hue alone.