IRONMAN UX

Overhaul

How

I

redesigned

key

flows

in

the

IRONMAN

App,

simplifying

the

UX,

improving

the

accessibility,

and

bringing

it

in

line

with

the

Human

Interface

Guidelines

Role:

UX Review, Design System, Wireframes, Prototype

Setting:

Unsolicited Redesign

Tools:

Figma, Figjam, After Effects, Lottie

Context

The IRONMAN Tracker App is an app for fans, friends, & family to track athletes’ times & progress in any of the 40 races worldwide each year. Users can see race info and set up trackers to follow along or view the results of past events.

Problem

Currently, the IRONMAN Tracker App has a number of navigation and accessibility issues that conflict with the Human Interface Guidelines and contribute to an unfamiliar UX.

UX Review
01

The bottom navigation bar behaves unexpectedly

When a user opens a race event, the bottom navigation bar changes to display navigation options specific to that event. This experience is inconsistent internally and with the Human Interface Guidelines. As a result, users need to adjust their expectations and re-learn what is otherwise a familiar mechanic.

02

The text sizes and backgrounds make it hard to read

The IRONMAN Tracker App’s visual accessibility is impaired by its choice of font sizing - especially when combined with image backgrounds. With small white text, the current designs also fail to draw users’ attention towards key info.

03

It’s hard to revisit trackers you’ve previously set

In the current designs, as soon as the race is over, the user must search for the event in the top bar to revisit the tracker they’ve set. The app also misses the opportunity to introduce an investment mechanic by allowing users to keep a history of their trackers.

Wireframes

User must be able to find and view information about a particular event

User must be able to set up a tracker for a particular race participant

User must be able to revisit any athlete tracker they've added

Wireframes

User must be able to find and view information about a particular event

User must be able to track a race participant's live progress and results

User must be able to revisit any athlete tracker they've added

Design System

In order to address the visual accessibility issues in the current designs, I created a new design system with the same core colouring but with higher contrast and more consistent iconography.

From this:

To this:

Prototypes
01

Revised information architecture

Viewing race information

The key changes to this flow are in the information architecture of the race event page.

When users open an event, they're now greeted with information prioritised in an F pattern to match natural eye movements. All available actions are contained in a vertical scroll component, simplifying the navigation & enabling the user to find to their next step faster.

02

Streamlined flow

Setting up a tracker

Adding trackers to particular athletes is the app's core flow. Bringing the entry points for this flow to the homepage highlights its value earlier and helps the user reach their goal faster.

Once a tracker is added, the user is immediately taken to the athlete's map where they can see visually how far along the athlete is along with their split times.

03

Stored action history

Revisiting your tracker

Once a tracker has been created, its stored in the 'trackers' page accessible within the event and on the 'trackers' page in the bottom navigation bar.

Having a history of created trackers enables the user to find a particular tracker even if the event has past, and develops an a sense of investment as they follow more races over time.

Solution
01

Step-by-step flow changed to a central hub with sub pages

To reduce the number of potential drop off points

02

All detail fields except the title are given defaults with optional editing

To reduce the number of barriers to posting

Wireframes
01

Detail options are grouped by importance

To incrementally encourage users to add detail optional without overwhelming them

02

A bottom sheet is used instead of a full page

To clarify the connection between the creation process and the home feed.

03

Most assets from the previous iteration are reused

To reduce development
cost and maintain our release cycle.

Solution
01

Step-by-step flow changed to a central hub with sub pages

To reduce the number of potential drop off points

02

All detail fields except the title are given defaults with optional editing

To reduce the number of barriers to posting

03

Detail options are grouped by importance

To incrementally encourage users to add detail optional without overwhelming them

04

Most assets from the previous iteration are reused

To reduce development
cost and maintain our release cycle.

Outcome

75%

% increase in % of active user base that are ‘creators’

23%

% increase in # of events created per month per active user

67%

% increase in creation flow completion rate

Converting Users to Creators at ClyxConverting Users to Creators at Clyx