Making connected fitness more connected than ever.
The problem
Between new hardware and new types of content, our existing system couldn't handle much more.
1
Most of our infrastructure was built around a single product (the Bike). But as the company evolved, so did our product offering. That system designed for one Bike could not be expected to work for an entire connected fitness ecosystem of hardware and apps.
2
Our content team had a lofty goal to establish itself as the "Netflix of Fitness." This meant producing a multitude of new content mediums — both in volume and variety — which put our already limited system at its breaking point.
3
The combination of new hardware mediums and content types expanded far past our original set of fitness disciplines. We were cramming more and more things into a finite space.
The objective
Our existing infrastructure was very rigid. There was no level of classification outside of Fitness Discipline. We wanted the flexibility to create any collection we wanted.
We wanted to be able to group common classes together, link to related collections, and delineate which have set orders of classes.
Our Bike and Tread experiences were the only ones with true homescreens. In order to achieve this we'd need a universal page structure.
The solution
Bike, Tread, App, Tablet, TV, and anything else in the future.
An infrastructure aimed at easily creating class collections and linking them to others.
Frictionlessly find a class on any device from a Tread to a phone.
A system of Collections and Series for content managers to deliberately create.
A system that can scale with time and new platforms.