UX Case Study — Mobile App Design
Designed for someone moving at 40km/h.
Parker is a parking app built around one radical constraint: every interaction must work with a single thumb, in traffic, without pulling attention from the road.
Role
UX Designer (Solo)
Platform
iOS & Android
Duration
8 Weeks
Scope
End-to-End
Splash
Permission
Main Screen
List View
Find a Spot◆Book in Seconds◆Navigate There◆Mark Your Park◆Pay & Go◆40km/h Design◆Real-time Availability◆No Surprise Fees◆Driving-Safe UI◆Find a Spot◆Book in Seconds◆Navigate There◆Mark Your Park◆Pay & Go◆40km/h Design◆Real-time Availability◆No Surprise Fees◆Driving-Safe UI◆Find a Spot◆Book in Seconds◆Navigate There◆Mark Your Park◆Pay & Go◆40km/h Design◆Real-time Availability◆No Surprise Fees◆Driving-Safe UI◆
The Problem
Every existing parking app fails drivers at the exact moment they need it most.
As vehicle ownership grows, the gap between available parking and real demand widens. Drivers circle blocks, park illegally, or overpay opaque Pay & Park services without knowing what they'll owe until they leave. It's a daily tax on attention, time, and trust.
0 min
Avg. time lost searching for parking in Indian cities
0%
Drivers have parked illegally due to no available options
0 apps
Tested — none passed a basic driving-safe usability check
0
Apps offered real-time availability + upfront pricing together
🗺️
No real-time availability
Apps show static listings. Drivers arrive to find spots taken, wasting time with no fallback.
💸
Hidden fees revealed at exit
Pay & Park services show total cost only when leaving. No upfront rate, no live meter.
📍
No parking location memory
After parking in a large or unfamiliar lot, users have no way to retrace back to their vehicle.
📱
UX built for desks, not dashboards
Competitor apps require multiple taps and complex flows — unusable safely at low speed in traffic.
Research & Discovery
Tested 3 apps. Interviewed 4 drivers. Found 5 gaps no one had solved.
Competitor Analysis
User Interviews
Contextual Observation
Heuristic Evaluation
F1
JustPark, Parclick, Smart Parking all failed the driving test
All three required 4+ taps to confirm a booking, used sub-12px text, and had no single-hand layout. Not one was safely usable at a red light.
F2
Car drivers lose 20+ minutes per city trip to parking
Every car commuter interviewed cited parking search as their highest daily friction. Two-wheeler users had near-zero friction — a key split that shaped the design.
F3
Price opacity is the #1 reason drivers avoid Pay & Park
Users don't distrust parking — they distrust not knowing the price. Upfront pricing with a live meter was the most requested feature across all interviews.
F4
No app offered expandable search on failure
When searches returned no results, every app showed a dead end. Users had no escalation path — they simply closed the app and drove away.
F5
VPN and GPS delay creates false location on first load
Mock locations and GPS cold-start lag caused wrong-city results when search was auto-triggered on open. Several test users searched in the wrong area entirely.
User Personas
Two users. One moving fast. One moving freely.
Research surfaced a clear split: four-wheeler commuters carried the full weight of the problem. Two-wheeler riders had minor friction but distinct needs. The design had to serve both without compromising either.
🚗
Arjun, 31
IT Professional · Daily Car Commuter · Bengaluru
"I waste 20 minutes every morning looking for parking. I'd happily pay if I knew exactly what I'd pay before I left the house."
Goals
▸Book a confirmed spot before leaving home
▸See total cost upfront — no surprises at exit
▸Navigate directly to spot and mark where he parked
▸Pay digitally without hunting for cash
Pain Points
▸Can't safely use complex apps while driving
▸Pay & Park opacity makes him avoid paid spots entirely
▸Forgets exact bay location in large multi-storey lots
🛵
Meera, 26
Freelance Designer · Two-Wheeler Commuter · Kochi
"I usually find a spot fine, but in malls or new areas I get confused. I just want a quick check — not an app that needs an account and a tutorial."
Goals
▸Quickly confirm availability in unfamiliar areas
▸Mark parking location to find the bike later
▸Lightweight experience — no friction, no onboarding wall
Pain Points
▸Doesn't want to register just to find one spot
▸Dense UIs feel overwhelming when navigating somewhere new
Design Process
Five phases. One throughline: the driver is always moving.
01
Empathise
4 driver interviews, 3 app teardowns, contextual city observation
02
Define
HMW statements, insight clustering, constraint mapping
03
Ideate
Crazy 8s, low-fi sketches, driving-constraint feature review
04
Prototype
Wireframes → Figma prototype → driving simulation phone-mount test
05
Test & Refine
5 usability sessions, A/B map vs list, payment friction audit
UI Screens
From parking problem to pocket-sized solution.
The complete app flow across onboarding, discovery, booking, navigation, and payment — all designed with divided attention in mind.
Login
OTP
Map View
List View
Book a Spot
Navigate
Parked
Payment
Key Design Decisions
Every decision has a reason. Click to reveal the rationale.
These weren't aesthetic choices. Each one directly addresses a specific research finding or behaviour observed during testing.
01Map + List toggle on home — both always available+
02Search triggers only on user intent — never on app open+
03UPI pre-authorisation required before first QR scan+
04All primary actions in bottom 40% — thumb-safe by design+
05Radius expansion (2–10km) activates only after a failed search+
06Navigation hands off to Google Maps / Apple Maps+
Before & After
The gap between what existed and what we built.
❌ Before Parker
✕Auto-searches on open before GPS is confirmed
✕No upfront pricing — cost revealed at exit only
✕4+ taps to complete a booking
✕Zero driving-safe UI consideration
✕No parking location marker after parking
✕Dead end on no results — no escalation
✕Account required before any feature works
✓ Parker
✓Map-first visual confirmation before search fires
✓Live meter with transparent rate before booking
✓2-tap booking flow for phone-mount use
✓Bottom-zone UI — all actions thumb-reachable
✓One-tap location marker with navigate-back
✓Contextual radius expansion on failed search
✓UPI pre-auth removes all payment friction at spot
Outcome & Impact
A parking app that works the way drivers actually think.
Parker delivers a complete end-to-end experience — find, book, navigate, park, pay — within an interface that demands nothing more than a thumb and a moment's attention. Every core design bet was validated by prototype testing.
0%
Single-handed task completion in driving simulation
0%
Users found a spot on second attempt with radius expansion
0
Ghost bookings in UPI pre-auth prototype sessions
0 taps
To complete a full booking from map view
📍 Real-time spot finding
📅 Advance booking
🧭 Navigate to spot
📌 Location marker
⏱️ Live meter
💳 UPI + Card
🔍 Radius search
🗂️ History + PDF
Reflections
What I'd do differently. What I'd double down on.
↑ Would improve
Expand the research base significantly
4 interviews is honest but thin. The design works for the personas found, but a larger sample across Tier 2 cities — where infrastructure differs dramatically — could reveal entirely different failure modes. 20+ interviews before shipping anything at scale.
↑ Would improve
Test with actual motion, not simulation
The driving-simulation test used a phone mount in a parked car. A real test — low-speed urban driving with a co-pilot observing — would give harder data on attention tax, glance time, and error recovery. This is the critical next validation step.
✓ Would keep
The constraint-first approach was the right call
Starting with 'what must work at 40km/h?' forced every decision to be earned. Without that constraint anchoring every feature review, we would have shipped a generic, desktop-thinking UI on a phone. Constraints don't limit design — they focus it.
✓ Would keep
Progressive disclosure on radius search was the breakthrough
Hiding the radius control until needed felt risky during ideation. Testing validated the instinct: showing it only on failure turned a dead end into a useful next step. Trust the research, not the assumption.
VHK.
Vishnu Haridas Karinatt
Product Designer · UX Researcher · Kerala, India
vishnuharidaskarinatt@gmail.com
© 2024 Vishnu Haridas Karinatt. Crafted with intent.Parker — UX Case Study