UX case study · retrospective

RockClimb

Designing clearer route discovery and navigation for climbers—especially when dependable cell service cannot be assumed.

Role
Sole UX designer & researcher
Scope
Research through high-fidelity prototype
Original project
2022
A sequence of RockClimb app screens, from route discovery to destination

01 · The challenge

Useful route information should not disappear when reception does.

Climbers need to judge whether a route matches their ability, understand current safety conditions, and find the route itself. Existing information could be fragmented across maps, comments, and external tools—an especially poor fit for remote areas.

The concept centered on one question: How might a single mobile experience help climbers confidently choose, prepare for, and navigate to a climb?

Design goals

01

Assess the climb

Make difficulty, distance, and essential route details visible early.

02

Learn from others

Surface practical advice and recent experiences from other climbers.

03

Navigate with confidence

Keep route guidance inside the experience and account for low-service conditions.

02 · Starting the design

From broad possibilities to one clear route.

I began on paper, comparing homepage structures and prioritizing three repeatable actions: discover nearby climbs, review route information, and start navigation.

First page of hand-drawn RockClimb homepage concepts
Early homepage options explored content density and entry points.
Second page of hand-drawn RockClimb homepage concepts
The selected direction emphasized tips, nearby routes, and recent activity.
Low-fidelity route detail screen Low-fidelity map and navigation sequence

Digital wireframes

The map became the primary interaction—not a handoff.

The low-fidelity flow connected route discovery, details, community guidance, and turn-by-turn navigation. Keeping the map inside the app reduced context switching and made the path from decision to action easier to follow.

At this stage, the interface intentionally stayed plain so testing could focus on structure and expectations rather than visual polish.

Low-fidelity prototype

The complete interaction model came before the visual system.

The connected prototype tested the full experience—from the home screen and navigation menu through tips, search, route details, mapping, destination feedback, comments, contact information, and profile. Individual route states let me test whether people understood when navigation was preparing, active, and complete.

Complete low-fidelity RockClimb prototype map showing connected screens and interactions
Complete low-fidelity interaction flow
Low-fidelity route detail screen
Route details
Low-fidelity first navigation countdown screen
Get ready · 1
Low-fidelity second navigation countdown screen
Get ready · 2
Low-fidelity third navigation countdown screen
Get ready · 3

03 · Usability study

Testing changed the navigation experience.

The study asked participants to find a nearby climb, review other climbers’ experiences, and route to the location. Four themes shaped the next iteration.

01

Keep the map integrated

Participants preferred completing the route flow without leaving the app.

02

Confirm routing has started

A visible countdown could remove uncertainty after selecting Route.

03

Expand location search

Users wanted to look beyond suggested locations and discover other climbs.

04

Simplify community input

The comments area needed clearer hierarchy and less visual competition.

04 · Refining the design

Feedback became visible, actionable, and easier to reach.

The revised flow gave routing a clear start and end state, strengthened route information, and kept community advice close to the map rather than separating it into another journey.

Before testing · low fidelity Low-fidelity navigation screen before usability testing
After testing · high fidelity High-fidelity route screen after usability testing

High-fidelity prototype

One connected journey from discovery to direction.

The final concept combines nearby route discovery, filters, detailed safety information, peer advice, and in-app navigation.

RockClimb nearby routes screen
Discover
RockClimb filtered search results
Search
RockClimb route information and comments
Prepare
RockClimb map detail screen with Route button
Navigate
Complete high-fidelity RockClimb prototype map showing connections from discovery through route navigation
Complete high-fidelity interaction flow

05 · Looking back

What I would reconsider today.

01

Validate the offline model. Define what data is downloaded, how freshness is communicated, and what happens when a route changes.

02

Test accessibility earlier. Include keyboard and screen-reader behavior, touch-target sizing, contrast, motion preferences, and nonvisual map alternatives from the first prototype.

03

Reduce visual noise. Give safety status, route difficulty, and the primary action stronger hierarchy than secondary community content.

04

Research in context. Observe climbers preparing at home and navigating at a real site, where light, weather, gloves, stress, and poor connectivity affect use.

What carried forward

This project taught me to design the whole experience—not only the final screen.

RockClimb was an early foundation for the work I do now: understanding the user’s mental model, making the core action testable, observing where expectations break, and using feedback to make the next move clearer.

Return to selected work