Product Teardown - Nike Training Club - Mobile App

April 8, 2020

Nike has been pushing boundaries in health-tech for some time. I remember their early Nike+ Sports band kit (2008) and Nike+ FuelBand (2013) that promised individuals an active lifestyle. They were pioneers in bringing accessible tech to consumers, and eventually other companies followed: Pebble, Fitbit, Adidas (MiCoach), and Apple.

I have been a fitness, health, and nutrition enthusiast for years. Over time, I have tried gym workouts, functional fitness, and CrossFit. I used to cycle and occasionally run to my previous workplace. Being a curious person helps me to think, question, and analyze many things — from signboards on highways and supermarket aisle arrangements to mobile apps and much more.

Since the lockdown, various fitness apps have helped me plan workouts daily. I particularly liked Nike Training Club over the others. Their plans integrate a running module in addition to strength and conditioning. I have used it several times but had never paid attention to several aspects of the app.

I took time to understand different elements of the app as a user. Below is my understanding, observations, and thoughts on Nike Training Club.

Nike Training Club (NTC) helps individuals work out at any place, without any cost, and tailors the workouts to individual needs.

Overview

This teardown covers:

  • Registration
  • Onboarding
  • Core experience
    • Workouts
    • Feed
    • Activity
    • Inbox
  • Overall assessment
  • Learnings

Registration

Nike has always been community-centric when it comes to product launches, and that reflects in the language used throughout NTC. When a new user opens the app, the screen says 'Join' instead of 'Sign up' or 'Register.' That small choice makes the experience feel like participation rather than account creation.

Once the user registers, the app asks a few questions to personalize the experience. At this stage, a few things stood out:

  • I didn't receive any email from NTC after registering
  • The registration page says 'sign-in' instead of 'login'
  • You cannot skip the onboarding process
  • The app does not distract the user by asking for a display picture at this stage

Onboarding

When you click 'Get Started,' the app asks two questions: your gender and current activity schedule.

I like how the screen clearly shows 'Female' and 'Male' as options, and the screen indicates the onboarding progress (1/2 and 2/2). That lightness matters — it keeps the path to the core product short while collecting enough info to personalize recommendations.

NTC does not ask about goals. It focuses on your current activity schedule and recommends workouts from there.

Observation: The individual has to choose one of two genders, with no option for 'other' or 'prefer not to say.'

After selecting gender and activity schedule, users see two more screens: the Achievement Locker (virtual badges — a gamification element) and a language selection screen, which appears surprisingly late in the flow.

Experience: Core Functionality

Workouts

After clicking 'Okay,' NTC recommends a personalized workout. It takes users directly into the workouts section — a strong product choice because it leads immediately to the app's core value.

  • NTC directs users straight to workouts after onboarding
  • It still does not ask for a display picture
  • 'Top Picks for You' enables lightweight discovery
  • Horizontal scrolling helps users find new workouts

When you click Browse, the app opens a wider set of possibilities: muscle group, workout type, and equipment. Scrolling further reveals options based on time and athlete-specific workouts.

Observation: The early discovery logic prioritizes muscle group, workout type, and equipment over time. This makes sense — choosing a 5-minute workout without the right equipment quickly becomes frustrating. The large selection of roughly 200 workouts also acts as motivation by reducing excuses.

Collections also group workouts into themed catalogues for easier browsing.

Feed

The Feed helps users connect with people they may know on NTC. At this point, the app asks permission to access contacts to support the feature.

Observation: NTC does not front-load a bundle of permissions. It introduces consent at the moment it becomes useful — a strong example of contextual permission design.

The feed also nudges users toward activity by highlighting the 'workout of the week,' showing duration, and demystifying common workout myths. When you enter a specific exercise, the app reiterates the length, intensity level, and workout level. It also offers options for AirPlay, audio preference, and music source.

Activity

The Activity section reinforces the behaviors Nike wants users to build. It shows activity history, achievements, and a simple way to add a workout by clicking the '+' icon at the top right of the screen. This turns discovery into continuity by making progress visible over time.

Inbox

The Inbox is where Nike communicates directly with users. What stood out was the wording under 'Progress Starts Today' — NTC emphasizes progress over goals. That distinction matters. By framing activity as process rather than outcome, the app feels more supportive and sustainable, especially for users trying to build a routine rather than chase a one-time milestone.

Process > Result. This mindset is the holy grail of lasting excellence.

Overall Assessment

Here are the key takeaways from this teardown:

  • NTC does not overwhelm users with permissions at the start of the journey
  • It keeps users focused on workouts rather than distracting them with secondary features
  • It uses product structure and language to make progress feel achievable
  • There are some flow inconsistencies, particularly around CTA language and the late timing of language selection
  • It is interesting that NTC does not offer Facebook or Google sign-in — I wonder why.

Learnings

  • Focus users on core features before introducing secondary elements
  • Keep CTA language consistent across all registration and onboarding surfaces
  • Let users choose language at a more natural point in the journey
  • Contextual permission requests are more effective than front-loading consent

I am hoping to write more teardowns like this to improve my understanding of products. Thank you, Vindhya, for helping me write this article.

If you have suggestions, thoughts, or feedback, please share with me on Twitter @anifooty.