Routley is a conceptual web and mobile travel planning app designed to simplify booking bus transportation across Europe. I designed this project solo to explore how product design decisions can reduce stress in complex, real world scenarios like international travel.
The core idea behind Routley was simple. Travelers should not need to jump between multiple platforms just to understand where they are going, how to get there, and what to expect when boarding. My goal was to design a product that felt calm, predictable, and trustworthy from search to boarding.
While researching travel booking platforms, I noticed a consistent pattern. Booking bus tickets across Europe often requires navigating multiple websites, comparing inconsistent information, and dealing with unclear boarding instructions. Even experienced travelers described the process as frustrating and time consuming.
This fragmentation creates unnecessary stress, especially when users are traveling in unfamiliar cities or across language barriers. I saw an opportunity to design a product that brings clarity and structure to this experience.
From a product perspective, this problem also presents a business challenge. When users are forced to leave a platform to complete bookings or clarify details, trust erodes and conversion suffers.
Routley is designed for travelers who value efficiency and clarity.
The primary users are international travelers, including both business and leisure travelers, who often book transportation on their phones while on the move. These users are comfortable with technology but have little patience for unclear interfaces or unnecessary steps.
From a product standpoint, my goals were to:
Rather than competing on the number of features, Routley focuses on doing fewer things exceptionally well.
Early on, I framed a guiding question for the project.
How might we help travelers plan and book bus routes as effortlessly as checking a map or calendar?
This question helped me stay focused on product fundamentals rather than surface level UI decisions. It pushed me to think about how Routley could fit naturally into a traveler’s routine instead of feeling like yet another app they had to learn.
Although this was a conceptual project, I grounded my decisions in qualitative research patterns and competitive analysis.
What consistently stood out was how much users valued clarity over flexibility. Travelers wanted to understand exactly where they were going, when they needed to be there, and what would happen next.
Key insights that shaped the product:
These insights became the foundation for the product experience.
To humanize the problem, I created a primary persona named Nathan.
Nathan is a 27 year old business analyst from Chicago who frequently travels across Europe for work and vacation. He values speed, organization, and reliability. He often books transportation on his phone and double checks details to avoid delays.
Designing for Nathan helped me prioritize what mattered most. He does not want to explore an app. He wants to complete a task quickly and feel confident that everything is handled.
This mindset influenced decisions around layout, information hierarchy, and flow structure.
As I moved into wireframing and early layouts, I focused on simplifying entry points and reducing hesitation.
One major challenge was helping users immediately understand where to begin. Early layouts made the route input feel secondary, which caused hesitation. I revised this by visually prioritizing the input experience and placing it prominently within the interface.
I also learned that showing too much information too early worked against the product. By progressively revealing details, users felt more in control and less overwhelmed.
What did not work was dense screens that tried to solve every edge case at once. What worked was guiding users through a clear, predictable journey with reassurance at each step.
The final design presents Routley as a calm and reliable travel companion.
Users can search for routes, compare providers, and book tickets within a single flow. Routes are presented visually, stops are clearly labeled, and boarding instructions are easy to find and understand.
Every screen is designed to answer a simple question. Where am I, what should I do next, and what happens after that?
This approach reflects my product design philosophy. Good products remove uncertainty rather than adding features.
If Routley were to move beyond concept, I would focus on validating the design through real world testing.
Next steps would include usability testing with travelers, measuring booking completion rates, and identifying drop off points. Additional product opportunities include offline ticket access, location based boarding reminders, and deeper map integrations.
These future considerations reinforce how the product could scale while maintaining clarity.
This project strengthened my ability to think beyond screens and focus on product outcomes.
I learned that product design is as much about restraint as it is about creativity. By prioritizing clarity, structure, and trust, I was able to design an experience that feels supportive rather than overwhelming.
Routley represents my approach to hybrid UX and product design. I focus on understanding user needs, defining clear product goals, and translating both into thoughtful, intentional experiences.
