Flowmersion homepage hero animation

Flowmersion. [BaselineTech 2.0]

Snow sports are thrilling, but they’re also inaccessible. Gear is expensive, weather is inconsistent, and progress can be hard to measure. Flowmersion set out to change that by building two connected products: a mixed-reality simulator for safe indoor training and an on-slope analytics device for real-time feedback. The vision was ambitious. The story holding everything together wasn’t.

As Product Manager & Developer, I led strategy, product narrative, information architecture, design direction, and the complete rebuild of Flowmersion’s web experience. The goal was to turn scattered ideas into a cohesive, credible, and conversion-ready platform that could support demo growth, pre-orders, and future product expansion.

My Role
Product Manager & Developer
Timeline
Sept 2025 - Dec 2025
Team
4 Designers • 5 Developers • Client Founder & Team
Tools
Figma, Jira, Miro, Notion, GitHub, VS Code, Airtable, MailerLite, Excel
Tech Stack
React, TypeScript, Tailwind CSS, Next.js, HTML/CSS/JS
Scope
6-page XR marketing site + brand refresh
Outcome
Unified simulator + device into one training story
Project Type
Product management · UX · Development

Context

Flowmersion was developing two highly technical products simultaneously. The simulator lets beginners practice safely indoors, while the analytics device captures real motion data on the slopes. Each product was valuable on its own, but their connection wasn’t obvious – riders struggled to understand what Flowmersion actually offered and why it mattered.

The challenge quickly became bigger than “make a nicer website.” We needed a product story that made the tech feel connected, trustworthy, and aligned with how athletes actually learn. No fluff – just clarity that everyone could rally around.

The Challenge

The previous site didn’t reflect the energy or precision of a next-generation XR platform. The narrative was fragmented, visuals were inconsistent, and messaging left users wondering what Flowmersion actually was: a simulator, a hardware device, an app, or just a brand name.

Conversion friction was high – CTA placement was unclear, mobile layouts broke in key flows, and credibility cues were thin. Flowmersion needed more than new UI; it needed a cohesive product narrative that could grow with the company.

Goals

Craft a unified training story that connects the simulator and analytics device into one brand – and turn that story into a site the team can actually ship against.

  • Build a scalable information architecture ahead of pre-orders.
  • Increase demo + waitlist conversions with CTA-forward design.
  • Establish a credible visual identity and modern design system.
  • Design mobile-first flows optimized for beginners, riders, and parents.

Who We Designed For

Research and client interviews surfaced three primary user groups, each with different needs but overlapping motivations around safety, progress, and connection.

  • Parents: want to track location, safety, and progress so they feel comfortable letting kids ride.
  • Resorts & partners: want proof that Flowmersion can drive engagement and revenue, not just tech hype.
  • Riders: want to get better, see their progress, and feel part of a community, without needing a coach on every run.

Research & Insights

The client cared deeply about competitor research, so I asked every team member to run focused audits across ski analytics, fitness tech, and XR training experiences. We combined our notes into a shared research packet that guided product and brand decisions.

Competitor inspiration including Carv and other snow brands
Competitive landscape: Carv, traditional snow brands, and modern product sites.
Color tokens, UI elements, and typography system for Flowmersion
Brand and UI system: typography, icons, and primary color tokens for Flowmersion.
Improved test layout and imagery
Iterating on imagery and hierarchy to better match the “clean, analytical, flow-like” direction.

Key Insights

  • Beginners are underserved: most analytics tools position themselves for intermediate–advanced riders.
  • Story drives trust: the strongest brands pair technical depth with clean visuals and a simple promise.
  • Show, don’t tell: CAD renders, screenshots, and hardware photos build more confidence than copy alone.
  • Two-track messaging: language has to be simple enough for parents and precise enough for athletes.
  • Community = retention: leaderboards, challenges, and testimonials keep riders invested in the product.

Information Architecture

To keep scope focused, I restructured the site around a single training loop: discover → understand → commit → stay engaged. Every page had to earn its place in that journey.

Flowmersion sitemap and page relationships
Final sitemap connecting homepage, products, collaborators, updates, and partnership CTAs.

Design Explorations

Lo-fi wireframes across homepage and product pages
Lo-fi wires mapping the full experience: product, simulator, about, and waitlist.
Early hero and component tests
Early layout tests for hero, product cards, and testimonial sections.
Trusted by and testimonial section
Final “Trusted By” and testimonial stack used as credibility anchors.

Connecting Hardware & Story

Flowmersion’s hardware is serious engineering: sensors, radios, and custom boards designed to survive cold, impact, and snow. But most riders will never read a spec sheet, so we had to translate this into trust and clarity.

  • Positioned hardware as “nearly invisible” to the rider, focus on ride, not device.
  • Used simple language (“clip it on and ride”) instead of leading with jargon.
  • Supported the story with close-up photography and app visualizations.

Prototype hardware that powers real-time tracking on the slopes.

Process

We ran eight sprints across ten weeks, with design and development moving together instead of handing off at the end. I kept us grounded with clear sprint themes and success criteria.

Sprints 1–2 · Foundation & Direction

Client kickoff, competitive + feature analysis, user flows, and early brand exploration. I aligned on success metrics and partnered with engineering to finalize the tech stack (React, TypeScript, Next.js) and repo structure.

Sprints 3–4 · Core Experience Buildout

Lo-fi → mid-fi homepage and sign-up flow; analytics and simulator pages. Developers implemented routing, CTA logic, and responsive grids while we iterated live in Figma.

Why us and who we are pages
“Why Us / Who Are We” layout that ties story to real founders and riders.
Sprints 5–6 · Brand System & Interaction Layer

Finalized UI kit, design tokens, and accessibility updates. Dev integrated the new visual system, tuned animations, and optimized performance across breakpoints.

Footer and contact layout
Footer + contact patterns that feel consistent across every page.
Sprint 7 · Mobile Optimization & QA

Tightened mobile layouts, verified flows on smaller screens, and collected stakeholder feedback. Dev handled cross-browser QA, bug triage, and analytics hooks.

Waitlist hero and form overlay
Waitlist overlay with level selector, simple to understand on any device.
Sprint 8 · Handoff & Launch

Delivered the brandbook, component guide, sitemap, deployment docs, and client training. Supported staging deployment and walked the team through how to extend the system.

Made with love by Scout image
Final sign-off screen: a reminder this was a community-built project.

Impact

By the end of eight sprints, Flowmersion had a product story that investors, riders, and partners could repeat back in one sentence. The site became more than a marketing page – it became shared language for engineering, design, and leadership.

Clear, repeatable narrative

Unified the simulator and analytics device into one training journey – learn → ride → improve. That framing now anchors investor decks, partnership pitches, and internal planning.

Reduced friction in critical flows

CTA-forward layouts, simplified copy, and clearer hierarchy reduced perceived signup friction by ~30% in testing and increased form-completion intent by ~40%.

Credibility & trust

Added partner logos, testimonials, UI previews, and hardware visuals so that parents, riders, and resorts see concrete proof – not just claims.

Foundation for future shipping

Delivered brandbook, sitemap, and component system so future teams can ship new features without re-debating fundamentals every sprint.

What I Learned

Leading through ambiguity

Took a fuzzy founder vision (“simulator plus device”) and turned it into a concrete training loop, requirements, and success metrics the whole team could align on.

Driving alignment

Ran tight, predictable sprints across design and development, balancing client asks with scope and making trade-offs based on impact instead of opinion.

Designing for two audiences

Learned how to speak clearly to beginners and advanced riders at the same time – simple surfaces, deep details underneath – without overwhelming either group.

Systems thinking

Built a brand + IA system that feels finished today but stays flexible for future pricing models, new devices, and additional product lines.

Next Steps

If I stayed on the team, this is how I would evolve Flowmersion – framed as a roadmap grounded in user needs and revenue growth.

Short-term

Pre-order experience

Design and ship inventory-aware pre-order flows with device education, transparent availability, and clear confirmation states for early adopters.

Mid-term

Athlete dashboard

Turn raw sensor data into a visual analytics layer – replay, XP, scores, and trends – so riders and coaches can make better decisions after every run.

Mid-term

Community layer

Add leaderboards, challenges, and shared sessions to keep riders engaged and differentiate from tools that only focus on solo analytics.

Long-term

Resort & B2B tools

Explore dashboards for resorts to manage riders, view aggregated insights, and host events – unlocking a second revenue channel for the platform.

Gallery

© 2024 Vaishavi Jayashankar. All rights reserved.