38 lines
2.4 KiB
Markdown
38 lines
2.4 KiB
Markdown
# Product
|
|
|
|
## Register
|
|
|
|
product
|
|
|
|
## Users
|
|
|
|
Islandflow is for serious individual traders and researchers working in live market conditions. They use real-time options flow, equity prints, inferred dark/off-exchange signals, and deterministic replay to investigate market behavior under pressure, where speed and confidence both matter.
|
|
|
|
## Product Purpose
|
|
|
|
Islandflow exists to help users quickly decide whether unusual market activity is meaningful, explainable, and actionable. The product should surface evidence fast enough to support real-time decisions, while preserving enough context and traceability to trust or dismiss a signal with confidence.
|
|
|
|
## Brand Personality
|
|
|
|
Precise, composed, forensic (with tactical tone when needed). The interface should feel like an instrument panel: utility-first, calm under load, and trustworthy. Brand voice should appear in orientation moments, empty states, onboarding, and high-level framing, while core workflows prioritize clarity, speed, and evidence.
|
|
|
|
## Anti-references
|
|
|
|
- Meme-stock or finfluencer-style trading apps that rely on hype, gamification, urgency theater, or promotional calls to action.
|
|
- Generic SaaS analytics dashboards with decorative gradients, vague card stacks, and non-actionable vanity metrics.
|
|
- Bloomberg-style visual density used as aesthetic cosplay instead of as a genuinely useful information structure.
|
|
|
|
## Design Principles
|
|
|
|
- Evidence before impression: every important signal should be explainable with clear supporting context.
|
|
- Utility over theater: visual choices must improve legibility, prioritization, and decision speed.
|
|
- Composure under volatility: interactions and layouts should remain stable and readable during bursts of market activity.
|
|
- Trust through precision: labels, states, and data semantics should be explicit, unambiguous, and internally consistent.
|
|
- Workflow-first framing: the interface should support investigative flow from detection to validation to action.
|
|
|
|
## Accessibility & Inclusion
|
|
|
|
- Target WCAG AA contrast at minimum across all core interfaces.
|
|
- Support reduced motion preferences, especially for live ticks, pulses, chart transitions, and alert animations.
|
|
- Never rely on red/green color alone for directionality or status; pair with text, icons, shape, and/or position.
|
|
- Keep real-time updates readable by avoiding flashing effects, excessive animation, and layout shifts during high-volume periods.
|