Case study

Carnot

Designing reliable app-to-vehicle control for shared mobility

Bounce ↗

Choose your depth

The problem, my contribution, outcomes, and strongest screens.

My role

Product design · Connected mobility · Service-state design

Product focus

A recoverable app-to-vehicle journey across booking, Bluetooth, riding, parking, and completion.

Overview

I redesigned Bounce’s connected-scooter journey across booking, proximity, Bluetooth pairing, in-trip control, and trip completion. The work turned unpredictable hardware and network transitions into explicit, recoverable product states.

The problem

A scooter could be reserved, nearby, paired, connected, paused, offline, or physically incomplete. The app had to coordinate the rider’s phone, Bluetooth, vehicle hardware, location, helmet and trunk sensors, and parking evidence without leaving the rider stranded when one signal failed.

What I drove

Mapped the service across the rider, mobile app, phone Bluetooth, scooter hardware, sensors, and network conditions.
Defined the state model from reservation and proximity through pairing, active ride, pause, recovery, and trip completion.
Designed contextual guidance for distance, connectivity, and physical actions, with an OTP fallback when pairing failed.

What changed

Mapped digital, physical, hardware, sensor, and network states as one rider experience.
Kept the journey recoverable when proximity, Bluetooth, or vehicle state became uncertain.

Impact