ParkFlux

Designing a flexible parking system that combines ANPR cameras, a management platform and a driver app.

[ ParkFlux dashboard + driver app device mockup ]
Role
UX/UI Designer
Team
5 people: product manager (also product designer), UX/UI designer (me), business analyst, software engineer, mechanical engineer
Timeline
Feb – July 2024
Skills
User flows, dashboard and app UI, design system (2026)
Tools
Figma

My Contribution

What I owned on this 5-person team:

1

Designed both parts of the product in Figma: the dashboard for parking companies and the app for drivers.

2

Mapped the end-to-end flow from arriving at the gate to leaving the spot, turning three disconnected pieces (hardware, platform, app) into one coherent journey.

3

In 2026 I came back on my own and built one design system for both apps (see below).

Result: the team presented it as the final pitch at DTU X-tech in spring 2024.

The dashboard and app screens below are the actual UI I designed in Figma.

[ Real-time Monitoring — dashboard on laptop + phone ]

Context

Rise in number of vehicles, loss of parking spaces and development of smart cities — parking management projected to grow 12.1% by 2030.

ParkZone already runs number-plate cameras (ANPR) and collects the parking data behind them, but the cameras and the data sit in separate systems.

Design challenge: how might we turn ParkZone's hardware and services into one coherent experience for drivers and parking operators?

[ Solution overview diagram: ANPR cameras, parking spot user, and app with payment ]

[ Management platform ecosystem diagram ]

Smart pillar

ANPR cameras, motion detection and LED feedback to track each parking spot

Owner dashboard → my focus

Web platform to see occupancy, set rules and export data

Driver app → my focus

Mobile app to guide drivers to a spot and handle access and payment

Research & insights

The team interviewed ParkZone's business lead to understand their current solution and where they see opportunities.

[ Parkzone – product/services map for private sector and businesses ]

Current User Flow

Current parking journey at ParkZone: what the driver does and what ParkZone does, from entering the car park to driving out

The team mapped the current end-to-end journey for a driver and the parking company.

Pain points:

Drivers struggle to find a free EV charging spot and remember where they parked

Guards manually check illegal parking and issue fines – this is slow and inconsistent

Data from ANPR cameras is not fully used to improve operations

These maps helped the team identify where a digital platform could improve the experience for both sides.

[ System map: ParkFlux App core functions diagram ]

Based on the journey and system map, the team defined the core functions for the ParkFlux app and platform:

1

Real-time monitoring & feedback

2

Booking and reservations

3

Space and EV-charging management

4

ANPR-based history, reporting, and user management

This became the backbone for the dashboard and mobile flows.

I started with low-fidelity dashboard layouts to explore how to:

Visualise space reservation and charger occupancy

Keep the side navigation simple for different modules (data, history, space management, user management)

Early low-fidelity dashboard layouts: a space reservation view with EV charging cards, and a vehicle entry and exit statistics view

[ Final dashboard designs — three views ]

[ Illegal parking alert — license plate detection ]

[ Reservation information tooltip ]

[ Parking space reservation management screen ]

Final dashboard highlights:

A map-like grid for a quick overview of free, occupied, and reserved spots

Separate cards for EV chargers, showing status and power use

A reporting view that aggregates ANPR data (entries, exits, fines) for business decisions

Mobile App Design

[ Mobile app design screens — part 1 ]

[ Mobile app design screens — part 2 ]

[ Driver app mobile screens — search, pick slot, book, confirm ]

The driver app I designed lets you:

Reserve a charger through the company or a private owner

Get guided back to your car after charging

One system for two apps

I designed both ParkFlux apps in 2024. In 2026 I came back on my own and built one design system for both. This was not part of the 2024 team project.

1. The problem

One dashboard screen used 30 different colours. The same purple had 6 versions.

Colour audit of the 2024 ParkFlux screens: six versions of the same purple and eight greys across the two apps

2. Colours with names

I gave every colour a name. Some names say the colour, like purple-500. Others say the job, like "main text" or "error". Now every screen uses the same colour for the same job.

Colour system: 12 base colours, and 23 colour tokens named by their job, such as main text, error and reserved slot

3. The parking slot: one part, two apps

Both apps show parking slots, so I built the slot once. It has four states: available, selected, reserved and unavailable. The dashboard shows it upright. The driver app shows it flat.

Parking slot component, upright and flat, in four states: available, selected, reserved and unavailable

4. Before and after

I rebuilt one screen from each app with these colours and parts. The dashboard screen went from 30 colours to 11. The driver app screen went from 21 to 8.

Dashboard booking screen: the 2024 version on top, rebuilt with the design system belowDriver app slot picker: the 2024 version on the left, rebuilt with the design system on the right

What I learned

How to connect business models, hardware constraints and UX in one concept

How to design for two user groups at the same time: drivers and parking operators

How to communicate a complex system clearly in a short pitch and a visual dashboard

How a shared system keeps two apps consistent (2026 revisit)

[ Other projects — Job Search Tracker and Designing for Less Stress ]