A React and Node contribution to ifit.com focused on class discovery, scheduling, and a smoother fitness-focused browsing experience.
A React and Node contribution to a major fitness platform, representative of our front-end work on consumer health and fitness products.
Fitness platforms live on how quickly a user can find a workout they actually want to do. If class discovery is slow, the next tab wins. iFit needed a browsing experience that could handle a large, growing library of classes and instructors while still loading instantly on a phone propped on a treadmill. The older flow was making users work too hard to find the next workout.
We contributed to the React front end and Node services supporting class discovery and scheduling, focusing on performance, filterability, and a layout that rewards casual browsing. The goal was a consumer-grade feel: smooth scrolling, meaningful previews, and information architecture that makes "what should I do today?" a one-tap answer. Backend interactions were kept crisp so the front end never stalled on data.
Here's how we thought about the implementation, the choices we made, and how we delivered it—without sharing anything that would compromise client privacy.
Optimized the React component tree and data loading so class listings and filters respond without jank.
Shaped the information architecture around how people actually pick workouts — by length, intensity, instructor, or studio.
Made the scheduling experience fast enough to be usable one-handed on a phone mid-workout.
Kept the Node service contracts clean so the front end and backend teams could move independently.
Platform-level metrics belong to iFit, but the rebuild improved browsing speed and reduced the number of steps between "open the app" and "start a workout."
