FPVTrackVote is not a generic utility app. It should feel like a premium creative cockpit for FPV pilots:
- Part precision tool
- Part creator portfolio
- Part sponsor-ready showcase platform
The experience should communicate control, speed, and craft.
The app should make browsing tracks feel inspiring, fast, and premium.
- Strong hero previews
- Clear difficulty and flow signals
- Minimal noise before the user sees a compelling build
The app should reduce anxiety while building in 3D.
- Editing modes must be explicit
- Recovery controls must be obvious
- Drafts and published work must feel like owned assets
The app should look credible enough for brands to imagine campaigns inside it.
- Premium surfaces
- Visible participation metrics
- Campaign cards that feel like launches, not placeholders
- Dark, cinematic, and intentional
- Industrial precision without becoming cold
- Fast and athletic without becoming gamer-chaotic
- Base background: deep graphite / blue-black
- Accent: signal orange
- Secondary accent: cool cyan
- Success / community growth: mint
- Avoid flat white-first layouts and random saturated colors
- Prefer layered translucent cards over plain gray blocks
- Use rounded corners generously, but keep spacing disciplined
- Strong contrast for key actions, quiet contrast for metadata
- Bold rounded headlines for product warmth and identity
- Clean system body text for speed and readability
- Compact caption layers for stats, chips, and metadata
- Primary navigation should highlight Discover, Studio, Partners, and Profile
- Each tab must feel like a distinct mode, not just another list
- Lead with curation, not volume
- Featured content should feel editorial
- Filters should be immediate and lightweight
- Every editing state should be legible at a glance
- High-risk actions must be reversible
- Camera and transform behaviors must never feel ambiguous
- Treat creator work as a library, not a feed
- Surface unfinished work clearly
- Show performance without making the page feel like analytics software
- Campaigns should feel sponsor-worthy
- Emphasize activations, participation, and repeat visibility
- Avoid hackathon aesthetics
- Use restrained spring transitions for selection, mode changes, and card emphasis
- Avoid decorative motion that competes with 3D editing
- Motion should clarify hierarchy, not show off
- New screens must start from a strong hero or strong first section
- Always ask: is this helping the user build, discover, or trust the platform?
- Prefer fewer, more intentional surfaces over crowded dashboards
- Preserve dark premium styling unless a screen has a strong reason not to
- Default white cards on plain backgrounds
- Too many equal-weight buttons in the same zone
- Generic “dashboard SaaS” layouts
- Neon cyberpunk overload
- Hiding critical editing state