← Back to projects

Netherland’s favourite parking app

Goal

This project was part of the EasyPark's global effort of bringing all group apps under a single platform and brand. The Dutch market was particularly challenging due to local functionality that users were extremely attached to.

Outcome

The launch was successful. Conversion in the main flow was kept at 95%+, with a task on time of 3 seconds and very small churn. Based on user feedback, additional features was added right after the first release.

95% conversion
3s time on task
2M users
Main parking flow: select area, confirm parking with an optional end time, reminder notification, and the active session timer

My contribution

The Dutch users' mental model was fundamentally different than our global parking flow: for more than 10 years, people opened their app and just tapped “start parking”. Many users forgot to stop their sessions, often overpaying. My role was to find solutions that balanced Dutch users' needs, while introducing EasyPark global solutions. I’ve tried subtle and expressive things.

Grid of automatic-stop and set-an-end-time explorations, in variant states across the confirm parking screen

Explored a multiple approaches early on, using different angles for offering the feature of setting an end time.

Photos of early field testing in the office, next to the select-area screen and the stop-parking-automatically pop-up

Tested first versions with users from Amsterdam and Rotterdam, in the office. They weren't big fans of the pop-up version asking them to set a time for their parking.

Variant explorations of the stop-parking-automatically pop-up, testing different copy and layouts

Explorations for the pop-up

I've facilitated user studies together with UX researchers and got reactions from Dutch users on the early concepts above. This consolidated insights about their mental model and current pain points, while informing us on the direction.

Shortly, users hated having to set a time in advance. Skippable pop-ups were alright, but rarely perceived as bringing value. We did discover a few scenarios when setting a time becomes useful, e.g. doctors' appointment, office day, or long term parking.

Next research used complex prototypes that I made in Protopie, together with UX writers. These concepts matched users' mental model of simply starting, with an optional end time. These were perceived much better.

Field study photos of people testing the app on the street in Amsterdam, above a set of inline set-a-stop-time component variants

The field study focused mostly on the map (another team), and observing people's reaction o the more subtle set end time feature.

Detailed explorations of a smaller element to be integrated in existing steps, rather than using disruptive pop-ups. My favorite was the toggle enabling a default.

My tasks than shifted to facilitating internal alignment across our leadership, together with the product manager and tech lead, since we aimed at introducing a big variation specifically for the Dutch market. Insights from research were extremely valuable here.

Then, focus shifted on making sure that we are re-using as much of the global flow and design system components as possible, while matching insights about users' needs. Several design iterations and rounds lead to a version that was gradually released in the market.

The launch was successful, and while monitoring the release we received user feedback regarding missing functionality, in Android: foreground services. The team got together and did a great job enabling the feature within a couple of weeks.

Shipped flow: the default start-parking-now path on top, branching down to the optional wheel-based end-time flow

This first release focused on Dutch users' needs with the global parking solution as a secondary action.

Things I learned