Platform for RV travelers

01 (About)

Industry

Travel

Year

2024-2025

Team

1 Designer (Me)

2 Stakeholders

1 Project manager

1 Business analyst

2 Developers

1 QA Engineer

Links

App Store

Google Play

Role

Sole Product Designer

Deliverables

Mobile app

Web app

Admin panel

Design system

Links

App Store

Google Play

Project highlights

40%

faster trip creation in internal usability testing

3

Connected surfaces: mobile app, web app, and admin panel

6 of 8

Of travelers considered offline access essential during interviews

02 (The challenge)

The challenge

RV travelers combine routes, campgrounds, POIs, exact addresses, changing stops, and trip details—often with unstable connection on the road.

The challenge was to make this complexity manageable across mobile and web, supported by internal admin tools.

My responsibility

As the sole Product Designer, I owned the product structure, core flows, UX/UI, design system, documentation, and handoff across all three surfaces.

I worked with the stakeholders, PM, BA, developers, and QA to clarify requirements, cover edge cases, and support implementation.

From insight to decision

Budget planning came too early

Insight

Post-launch feedback showed that users hesitated or stalled when asked to plan a budget during trip creation. At that point, most travelers did not yet have enough information to estimate it.

Decision

I removed the Budget step from the Create Trip flow and moved budget planning out of this early stage. In internal usability testing with eight participants, the revised flow was completed 40% faster than the previous version, largely due to removing this step.

Budget planning came too early

Insight

Post-launch feedback showed that users hesitated or stalled when asked to plan a budget during trip creation. At that point, most travelers did not yet have enough information to estimate it.

Decision

Before

After

Offline access became a core requirement

Insight

Six of eight interviewed RV travelers considered offline access essential when planning and traveling on the road.

Decision

I translated this need into a core product requirement and designed offline access to trip overviews, maps, trip details, and individual stop details. The functionality was released across the product.

Offline access became a core requirement

Insight

Six of eight interviewed RV travelers considered offline access essential when planning and traveling on the road.

Decision

Map exploration needed a more scalable model

Insight

As stays, POIs, parks, and other locations grew, overlapping pins made exploration harder. Loading every location by default also created unnecessary paid Google API requests.

Decision

I identified the issue, worked with developers to understand the API and cost constraints, and proposed clustering. We grouped locations at wider zoom levels and progressively loaded details as users zoomed in.

Map exploration needed a more scalable model

Insight

As stays, POIs, parks, and other locations grew, overlapping pins made exploration harder. Loading every location by default also created unnecessary paid Google API requests.

Decision