Peloton Just Work Out Offline Mode

an offline experience for the tracking feature









My Role

Nari Park
- Senior UI Designer
Jackie V.
- Engineering Manager
Nimit Shah
- Product Manager



Project Lead
Associate Product Designer

7 weeks to deliver the design handoff

Android & ios mobile devices



Currently, Peloton's 'Just Work Out' feature requires an internet connection to start a workout, record accurate workout metrics, and complete the workout. We aim to address situations where members attempt to begin a workout without network access, to truly empower our users to work out anywhere, anytime with Peloton.

Peloton users can't use Just Work Out without internet connection


By empowering users to initiate and complete workouts offline, our engineering team investigated the backend's capabilities and constraints, while the design moved forward. I worked closely with these experts to understand the feature's infrastructure and constraints, ensuring that the design and engineering teams were aligned with the technical constraints.

The main business goal of this project is to increase the retention rate of the Just Work Out feature and reduce user complaints about lost and incomplete workouts. The secondary API to monitor would be the duration of Just Work Out sessions, as well as the started and finalized rates.

Unlock the ability to start and complete workouts in areas with no internet connection

My Role

As the lead designer on this project, I was responsible for leading feature research initiatives, facilitating workshops with stakeholders, and establishing the Offline mode infrastructure settings in the Peloton app.

Working closely with a product manager and the engineering team, we were able to drive alignment among various stakeholder teams, such as the app team, wearable experience team, engineering teams, and teams working on future projects that will also need to utilize the offline mode.


Explore the capabilities of the 'Just Work Out' feature

Improve the consistency of the workout experience

It begins with defining the user flows, while our engineering team investigates the backend constraints. Mapping out use cases helped us identify an opportunity to craft a solution for issues related to internet connectivity. As I was learning about the feature, I noticed that the internet connectivity could cause an inconsistent experience.

By communicating with the engineers of the concern on internet connectivity, we were able to set up two checkpoints in the task flow for detecting connections. This leads to controlling various possible flows into two cases.

The 'Just Work Out' feature will be default in offline mode, where the data will be saved and stored locally. The next step is to develop solutions for a synchronization system for workout metrics.


Working with engineering experts, we defined three different use cases depending on how the synchronization system copes with requests when the user taps the 'End' button to end the workout. The three possible situations are as follows:

1. Device detected no internet connection.
2. Device detected internet - Packet loaded - Device succeeded in receiving the packet from client.
3. Device detected internet - Packet loaded - Device failed to receive the packet from client.

In establishing the user flows responding to the synchronization, we conducted investigations into its capability and personalized the solutions based on different user flows. We also learned that the average time taken by synchronization ranges from one to two seconds, with a maximum of four seconds. However it has the potential for failure, which will lead to the third use case.

Personalize the offline experience

Given the opportunity to reimagine the landing page of the Peloton app for offline mode, we decided to highlight the 'Just Work Out' feature while ensuring the implementation of the reconnect function.

Obtaining the user's consent for the Heart Rate Monitor disclaimer and Terms of Service is necessary in their first use. 

After discussing this requirement with the engineering and legal teams, it has been confirmed that we can surface these two agreements during offline usage. The agreement data will be synchronized once the device connects to the internet.

Communicating findings with cross-functional teams


While exploring the capabilities of the feature, I discovered three edge cases that could be improved to enhance user experience. The three edge cases are as follows:

1. Member's app crashes or the battery dies during a 'Just Work Out' session before completion.
2. Member pauses their workout for an extended period, considering whether to treat it as ended.
3. User experience for offline 'Just Workout' sessions, especially concerning HRM/sensor callouts and disclaimers.

Collaborating with PMs and engineers from both the API and client teams, we embarked on strategic planning to address these issues. Our focus was on developing solutions to improve user experience, while also carefully considering the project's timeline.

Committing to resolving edge cases


During design sprints, sharing design treatments with domain experts ensures the technical feasibility and a seamless user experience for this feature enhancement. Each solution undergoes review by product, software engineering, and legal teams for approval to move forward.

After the design handoff, I maintained close dialogue with the engineering team to stay updated, particularly regarding constraints. While we anticipated several edge cases during user interactions, finding the balance to ensure timely feature implementation was crucial for a consistent workout experience.

I collaborated with the product and data analytics teams in an agile setting to define tracking metrics. This allowed us to monitor the frequency of these edge cases, ensuring informed prioritization for post-MVP enhancements.

Detailed design and design handoff

Implement the solutions within the established timeline


Following the handoff, I took a moment to reflect on the recent weeks. Within Peloton's design sprint framework, I've not only been working hard to learn how to tackle complex problems but also learning how to communicate and listen to different domain experts as a designer, and as a better person. This project provided me with a deeper insight into the development aspect, ensuring I could make essential adjustments while maintaining a commitment to allow our user work out anywhere, anytime.

Work out anywhere

During week 8, I carried out an anonymous survey among the engineering and app design teams. The goal was to collect feedback and insights to refine my contributions and elevate my future performance. Ultimately, I received 12 anonymous responses from the Design and Engineering teams.

Gathering Insights from teams