Product Design

App | Citya

Designing a shared, on-demand ride service from scratch, with one app for passengers and one for drivers, to connect Prague's suburbs with the city center.

Background Line
My role

Lead Designer: design delivery, and the growth of 3 other designers

Timeline

2022, 4 months

Team

3 designers, 1 Product Owner, 4 developers, 1 Agile Coach. Scrum, fully remote

What we built

Passenger app and driver app, both from scratch

Status when I left

MVP ready to launch in the Czech Republic

The problem

The suburbs were badly connected

Prague has great public transport, but people living in its suburbs have few options to reach the city center.

What I did

Led design from first assumption to tested apps

I ran weekly discovery workshops with the business, planned the design backlog with the Product Owner, led research and testing, and guided the team through both apps.

The outcome

Two apps, developed and tested, ready for launch

The passenger and driver MVPs were built and tested, with a plan to learn from real rides after launch.

01The problem

Prague, like many cities, has a great public transportation system. For people who live in its suburbs, though, there are few options to reach the city center.

Citya solves this by picking up passengers heading in the same direction in larger vehicles, with up to 6 passengers. The vehicle picks people up at a stop near them and drops them at a stop near their final destination.

The design challenge: this is a new kind of service. People have to trust a ride that isn't a taxi and isn't a bus, walk to a stop that only exists in the app, and share the trip with strangers. And drivers need to handle it all while driving.

02My role and how we worked

I was the lead designer, responsible for the design delivery of both products and for the professional development of the other designers.

Align every week

Weekly discovery workshops with the business management team to understand the needs, present designs and build the next steps together.

Plan with the Product Owner

Together with the Product Owner and the business, we defined the steps to launch the MVPs of both apps.

Make our pace visible

Design tasks were sized as small (1 point), medium (3) or big (5) by effort, written in Jira and split between us, so we could check our performance every sprint.

Research and test

Competitor analysis, user interviews, usability tests and user journey maps, so we knew we were building something valuable.

The backlog, split into "pilot launch", "after launch" and "unsure", with task sizes and owners.
One journey map for both sides of the ride: passenger above, driver below.
03From assumptions to evidence

A brand-new service comes with a lot of beliefs. In our workshops we wrote them down as assumptions, turned them into hypotheses and questions, and tracked what we found.

"What do we think we know?" Our board of assumptions, hypotheses, questions and findings.

How we researched

Competitor analysis

We studied similar services, including Citymove, Savvy Mobi, Via and MOIA, and wrote down what we learned from each.

Interviews

Semi-structured interviews about daily habits: how people get to work, and what kind of transport they use.

Usability tests

Participants performed tasks on a prototype while thinking out loud. We tested the prototype, not the person.

Our research workspace: interview script, usability test guide, competitor analysis and findings.

What the research showed

Finding 1: walking distance

500 m is a lot to walk to a stop. So the pick-up screen shows the walking time and distance before the ride is confirmed.

Finding 2: waiting time

Waiting felt too long beyond 15 minutes. So the passenger sees a time range, "10 to 15 minutes", instead of an open-ended search.

04Key decisions

These are the beliefs from our workshop board that shaped the passenger app most, and where you can see each one in the design.

We believedOur target audience is willing to walk to and from virtual stops.
→

Show the walk before you commit. The pick-up screen shows the walking time and distance to the stop, and the ride summary repeats it as "1 to 5 min walk", so nobody is surprised.

We believedPeople are willing to wait for the transport.
→

Make the wait concrete. After confirming, the passenger sees "10 to 15 minutes" with the car arriving at the pick-up point, instead of an open-ended "searching".

We believedPeople will be anxious with stops and route changes.
→

Show the route as it happens. The "On route" screen has a progress bar with every stop and the estimated arrival time, so extra stops feel expected.

We believedSafety is one of the main concerns of our customers.
→

Say who is coming. Before pick-up the passenger sees the driver's name, the licence plate and the vehicle model.

Passenger app: one ride, six moments

Where to?
1Where to?Search a destination, or pick an available point on the map.
Pick-up point
2Pick-up pointThe stop to walk to, with time and distance.
Ride summary
3Ride summaryStart, pick-up, destination, seats and price, before confirming.
Car arriving
4Car arrivingWaiting time, driver and vehicle details.
On route
5On routeProgress along the stops, with arrival time.
Arrived
6ArrivedRequest, pick-up and drop-off times, seats and price.

Driver app: one clear action at a time

Each screen gives the driver a status, the next stop and a single main button.

Go online
1Go onlineEnter the licence plate of today's vehicle.
First request
2First requestThe pick-up address and one button to accept.
Pick-ups and drop-offs
3Pick-ups and drop-offsUpcoming stops in order, with "Start ride" and "Call passenger".
Going offline
4Going offlineNo new rides are received while preparing to stop.
Finishing rides
5Finishing ridesOnly the remaining drop-off, with "Finish ride".

Why: drivers can't read much while driving, so each screen has one action.

05Outcome and what came next

The passenger and driver apps were developed and tested. When I left the project, the MVP was ready to launch in the Czech Republic. I don't have post-launch results to share, so this case study focuses on the process.

Learn from real rides

The team planned to take rides with different passengers and drivers, to take notes, run interviews and observe behaviour.

Operations dashboard

A dashboard to manage the whole service was being built, so fleet operators could support drivers and passengers.

New features

New features were in development, like pre-booking a ride for passengers.

What I took from it

The three designers grew a lot in their careers over these four months, and we kept sharing knowledge after the project ended. Looking back, I wouldn't do anything differently.

Let’s make it happen.

Whether you’re ready to start a project or just want to chat about your ideas, feel free to reach out! I’m always open to discussing new opportunities.