Back to selected work

ParkZen

Find perfect parking
en route.

My role
Research & UX design
Tools
Figma
Desk research
User interviews & synthesis
Context
Independent feature concept
Behind the workExplore the design processInterview themes, familiar interface patterns, and prototype testing.
01

Research

The problem.

One unexpected afternoon, my husband stumbled upon a hidden parking lot we’d never noticed. An El Dorado in the desert. The signage was misleading, the space was free, and the walk to Main Street took 30 seconds.

That serendipitous experience had us asking: how many parking gems are hiding in plain sight?

From that question, ParkZen was born: a concept feature for Apple Maps that makes parking discovery and planning feel clear, intuitive, and accessible.

Beyond my own experience

Understand what makes parking the worst.

I reviewed local coverage, surveyed residents, and interviewed people about parking in Nashville. Three themes shaped the concept: availability, confusing information, and cost.

Research synthesis titled “how to make parking more peaceful”: three interview themes (finding a space, cost, and a disjointed journey), six participant notes, and a design response for each.
Interview notes → design responses.
02

Strategy

Build on a familiar experience.

I explored how parking could fit into the navigation habits people already had. Sketching helped me work through the full sequence: find a destination, choose parking, drive there, then walk the remaining distance.

This is where I decided to build on Apple Maps instead of a whole new app, because of what I learned: people hate parking. The best way to make it better is to help it fade into the trip they’re already taking.

Pencil sketches of three phone screens: searching for a destination, a destination card with a new parking button, and a list of nearby parking with walking times, titled Find parking near destination and get directions to both.
Early sketches / Find parking near a destination, then get directions to both. Green dots mark screens Apple Maps doesn’t have.

Extend the interface people already know.

I studied Apple’s Human Interface Guidelines and Apple Maps’ typography, colors, bottom sheets, and navigation patterns, then used those conventions in my concept. The challenge was to make the new parking feature discoverable while keeping the surrounding experience familiar.

Early destination card with a Find a Spot action beside existing destination information.
Initial approach / Parking on the destination card.

I also explored nearby search and payment flows. This case study focuses on selecting parking and completing the journey.

03

Test & refine

Three decisions shaped by testing.

I moderated five think-aloud usability sessions: two in person and three remotely via Zoom, lasting approximately 20–30 minutes each.

Participants compared parking near a restaurant and followed the journey from driving to parking through walking to their destination.

My participants were so helpful: their feedback changed the design in three ways.

01 / Make parking discoverable

Put parking where people plan a route.

“I didn’t notice Find a Spot.”

Usability participant

The separate action competed with the familiar blue directions button. I moved parking into route planning so it could become part of that existing decision.

Earlier destination card with a separate gray Find a Spot action, circled.
Before The gray Find a Spot action (circled) was easy to miss.
Revised directions screen with an Add Parking Spot field.
After Parking is now a stop inside route planning.

02 / Keep the map useful

Compare options without losing their location.

A participant could not connect the parking choices to their locations on the map. I replaced the vertical results overlay with horizontal cards to leave more of the map visible during comparison, and tapping a card highlights its spot on the map.

Earlier vertical parking results overlay listing parking options.
Before A vertical list covered the map.
Horizontal parking cards with the surrounding map and route visible.
After Horizontal cards keep the map in view.

03 / Clarify the handoff

Parking is one stop before the destination.

Another participant initially expected one set of directions. I made the parking stop explicit in the route and provided walking directions after arrival, carrying the journey through to the final destination.

Arrival at parking with a walking directions action.
Step 1 Arrive at parking.
Walking navigation to the final destination.
Step 2 Continue on foot to the destination.
04

Detail & reflection

Familiarity still needs scrutiny.

Matching an established interface did not guarantee that people would notice a new action or understand a new sequence. I also reviewed contrast and refined the arrival screen’s text treatment.

“Designing ParkZen taught me how powerful small UX choices can be. Something as mundane as parking holds emotional weight: missed plans, unexpected costs, daily stress. I learned that clarity, timing, and flow matter as much as the visuals.”

Accessibility refinement

Make the arrival message easier to read.

The earlier arrival screen placed white text on a bright green background. I changed the message to black text on white, retaining green as a success accent.

Before / White on bright green
You’ve arrived!
Revision / Black on white

Contrast check · WCAG 2.2

Before: white on bright green 2.65 : 1Fails AA
After: black on white 21 : 1Passes AAA

AA requires 4.5 : 1 for body text and 3 : 1 for large text.

Visual refinement / Portfolio update

Keep the map visible and the next action clear.

After growing as a designer, I revisited spacing, hierarchy, and labels. The camera action is now explicitly labeled “Scan parking QR” for parking-garage codes.

Horizontal parking comparison.
Horizontal parking comparison.
Arrival at parking, with walking and QR actions.
Arrival at parking, with walking and QR actions.

Next test

Can people complete the revised flow without guidance?

Next, I’d implement the design and test whether people find the parking step, connect each card to its location, and move smoothly from driving to walking.

Implementation question

How reliable is the information behind the interface?

Availability and pricing would need dependable data sources. Recommendations from other drivers could help fill the gaps. An implemented experience would also require platform feasibility work beyond this prototype.

An independent concept; not affiliated with Apple.