Flex is a new riding experience app, built to move the e-bike ecosystem beyond a utility companion app. I led the product from zero to App Store launch, turning everyday rides into a loop of tracking, progress, rewards, sharing, and return usage.
WHAT I LED
DURATION
Jun 2025 to Present
MY ROLE
Product Manager / Product Owner, leading 0 to 1 product definition, delivery, and launch
TEAM STRUCTURE
iOS, Backend, Firmware, Design, QA, outsourced Android team, Marketing, Customer Support, Legal counsels
PRODUCT STATUS
Closed beta launched July 2026; iOS v1.0.0 released on the App Store September 10, 2026
PLATFORM
iOS mobile app; Android in development
TOOLS
Notion / Figma / Amplitude / Segment / Firebase / OneSignal / VitePress / VS Code
1. Defined the product from zero to a shippable rider platform
Flex started as a broad ambition: build Hyena’s next-generation e-bike experience app. The challenge was not a lack of ideas, but too many possible directions across ride tracking, rewards, social features, environmental campaigns, challenges, bike management, and third-party sync. I turned that ambiguity into a focused MVP by defining the core loop: Ride, Review, Progress, Reward, Share, Return. This helped the team move away from feature stacking and toward a product system that could be launched, measured, and iterated after real rider usage.
What I learned: 0 to 1 product work is not about adding more ideas. It is about choosing the smallest system that can prove the product direction.
2. Translated connected e-bike complexity into product rules
Flex is not a phone-only fitness app. Its core experience depends on real e-bike data, Bluetooth connection states, GPS behavior, firmware constraints, backend records, and iOS background behavior. I defined the ride lifecycle across start, pause, disconnection, resume, finish, save, and sync states so the product could behave consistently when the bike is powered off, out of range, or left in an unfinished activity. These decisions directly shaped ride recording, Weekly Goals, Streaks, XP, EcoGems, badges, activity history, and support messaging.
What I learned: the hardest part of a connected product is making invisible system constraints feel simple, reliable, and trustworthy to users.
3. Measured activation by completed rides, not just onboarding
I separated onboarding success from product activation. For Flex, a user is not truly activated just because they sign up or complete setup. Activation happens when they connect a bike, start a ride, finish it, and see their progress. I used Amplitude to track the journey from Add Bike intro to Ride Finished, which revealed a 44.2% activation funnel conversion. During closed beta, Flex recorded 88 active users, 743 ride starts, and 569 ride finishes. After App Store release, the first tracking window recorded 68 active users, 114 ride starts, and 117 ride finishes.
What I learned: a good metric system protects the team from optimizing easy numbers instead of the user behavior that proves value.
4. Led the launch across product, engineering, support, and legal
I coordinated the release across iOS, backend, firmware, design, QA, outsourced Android development, marketing, customer support, and external legal counsel. My role was to keep product behavior, system reality, analytics, support content, privacy documentation, and launch communication aligned. Flex v1.0.0 moved from development close to QA, App Store submission, and official release, launching on September 10, 2026. The result was not only a shipped app, but a product foundation for Hyena to build long-term rider engagement beyond basic bike support.
What I learned: launch readiness means the product, data, policies, support materials, and user-facing messaging all need to tell the same truth.