Reach out to start your project
See all Projects
  • Hardware state, on screen
  • Guests without accounts
  • Multiple devices per user
  • Readable in daylight

Parqly

A parking space that knows whose it is.

Jul 28, 2025
Client
Parqly
Services
UX/UI · App · Connected device
Year
2025
SECTOR
Smart parking & IoT
SURFACES
Mobile app · Parking lock · Guest links
Parqly
01 — The ChallengeWhat we were handed

A reserved space is only reserved if someone can enforce it — and nobody wants to stand guard.

Parqly pairs a physical parking lock with an app, which means the product spans a driveway and a phone. The design problem was making a piece of hardware legible on screen: whether it is locked, whether it has battery, whether a guest can open it, and what happened while you were away. Every state the device can be in had to be readable in a glance from the pavement.

02 — Groundwork

Structure before surface

Every flow was argued in grey first. Nothing went to visual design until the journey held up.

WIREFRAME · ACCESS & PAYMENT
WIREFRAME · ACCESS & PAYMENTGuest invite, map search, notification log and saved cards resolved in grey — the invite was cut to name, number and a time window, because anything more and nobody sends it.
WIREFRAME · DEVICE CONTROL
WIREFRAME · DEVICE CONTROLOne device per screen with lock, unlock and battery on the same row, and history underneath. The dial came out of this stage: a state you can read at a distance, not a toggle you hunt for.
03 — What shipped

One screen, one decision

01 / 03
The lock, drawn as itself
Map first, payment second
Every alert is an opt-in
DEVICE CONTROLThe lock, drawn as itselfOnboarding, home, control and sign-up. The device is rendered rather than iconified, so the thing on the screen and the thing in the driveway are obviously the same object.
In the hand

Built for the phone first

Finding a spot, one thumb, kerbside
Finding a spot, one thumb, kerbside
App and lock in the same frame
App and lock in the same frame
04 — How it runsTech & architecture

An app whose job is to make a physical object trustworthy.

AppMobile app pairing to the lock, with multi-device support per account
Device layerLock, unlock and battery state surfaced as one readable status
AccessGuest invites by SMS link, scoped to a date and time window
CommerceSubscription and per-use payment with saved cards and history
05 — Outcomes

Hardware that explains itself before anyone reads a manual.

1Status object carrying lock, battery and presence
SMSGuest access without an account or an app install
MultiDevices and locations under one profile
LogEvery open, close and jam recorded per device
I had a great experience with Roars Technologies. Their service is professional, flexible, and friendly. I am very happy with the service and the results. The entire process stood out to me as exceptional.
Elena ElraieDigital Consultant, Lametus
Where it goes nextVendor onboarding and shared-bay scheduling are the next release on the same device model.
Start a project like this