Client

Go Vanlife

Go Vanlife

Date

Date

Evolving a travel platform across mobile and web

Evolving a travel platform across mobile and web

Improving location discovery, community content and publishing flows across an established travel product and its new web experience.

Go Vanlife
Go Vanlife location discovery on mobile and web
Beyond the first scan

Plantix is a graduation project exploring what happens after a plant is identified. A scan can name a plant or suggest a problem, but people still need to understand the result and decide what to do next.

I led a two-designer team, owning product direction, UX architecture, core flows and final design decisions. I also worked on research, prototyping, UI and testing.

Research shifted the focus to ongoing care

Interviews, a survey with 30 plant owners and a review of existing apps showed that identification only solves a brief moment. People needed to know why their plant was changing, how serious it was and which advice applied to them.

Beginners wanted a plain-language answer and a next step. Experienced owners wanted history, trends and control. I used progressive depth: a clear answer first, with detailed information available when needed.

Evolving a product people already use

Go Vanlife connects location discovery, routes, articles, trip planning and community knowledge. I joined an established mobile product and worked on its evolution alongside a new web experience.

As Product & UX/UI Designer, I covered audits, information architecture, flows, prototypes, production UI and developer handoff. The challenge was to simplify the product while preserving behaviour people already relied on.

Go Vanlife: location discovery across mobile and web

Understanding the whole system

The app already included locations, routes, articles, moments, profiles, chats, reviews and events. I audited how these features worked together and researched comparable travel, content and community experiences.

Important content was getting lost in secondary information, similar actions behaved differently and publishing took more steps than necessary. I used these findings to clarify hierarchy, reduce unnecessary decisions and make primary actions easier to find.

One product, two contexts

Desktop needed its own navigation, layouts and information density. I kept shared terminology, interaction patterns and visual rules, while adapting the experience to a larger screen.

Go Vanlife web experience and content layouts

Helping travellers choose a place

A useful location is more than a map pin. Road conditions, access, services, weather, photos and community knowledge all inform the decision. I reorganised this detail so people could scan the essentials first and explore further when needed.

Location details and practical travel information

Community content that supports the trip

Profiles, routes, articles, moments and reviews connect travel knowledge to the people behind it. I clarified authorship and activity, and simplified the path from creating content to previewing and publishing it.

Each content type still asks for the information it needs, but the flows use consistent patterns and avoid unnecessary steps.

Community profiles and publishing flows

A shared foundation for mobile and web

I brought typography, spacing, cards, controls and reusable components into a more consistent system. Because locations, routes, content and profiles are connected, each decision had to work beyond a single screen.

Go Vanlife reusable interface patterns

Designing alongside implementation

I worked with stakeholders and developers throughout the process, accounting for existing functionality and technical constraints. Flows, responsive layouts and handoff specifications helped the team improve the product without breaking established behaviour.

Go Vanlife responsive interface designs

Progress and perspective

Go Vanlife had 150K+ downloads, 20K+ locations and 1.5K+ daily active users when I joined. These describe the scale of the existing product, not outcomes of my redesign.

The work described here is still being implemented. Its focus is continuity: understanding what people rely on, deciding what should change and creating a system that can keep evolving across platforms.