01
Entire rental in-app
Why: A cyclist needs to stow their bike quickly and safely. The app guides them to the locker, the locker opens on its own after payment, and there's nothing else to deal with.
Impactbike secured in a few steps
Smart, secure bike parking with an app for 75k+ users.
“The design was always ready for us to build right away. No follow-up questions, no rework.”
Martin Sýkora, Senior developer
ChallengeBike secured, no delays
What we designediOS and Android app
Our roleUX, UI and design system
Result337 dev-ready screens
/Starting point(01)
BikeLink runs a network of electronic bike lockers in the San Francisco area. If you don't want to leave your bike on the street by a lamppost, you pick a locker in the app, the app guides you to it, the locker opens on its own after payment, and your bike is safe. Over 75,000 people use the app. When a locker doesn't open on the first try, you're left standing with your bike in front of a locked box.
“Our designer left in the middle of the project, and development risked stalling. But the new designer took over the work-in-progress screens brilliantly, and development kept going without delay.”
Martin SýkoraSenior developer
/What we did and why(03)
3 principles behind our 337 screens.
02
Screens for when the connection fails
Why: Lockers open via Bluetooth. When the connection fails, the app doesn't leave people stuck at a locked box: it guides them to a backup QR code.
Impactusers know what to do next
03
1 component set for iOS & Android
Why: The app was built by iOS and Android developers, and the client was in the US. So we built all 337 screens from 150 components, so they could be built without extra explanation.
Impactno needless dev questions
/Process(05)
A weekly call to California. New screens ready by the next.
01
Rider journey
We mapped what people do from the moment they look for a place to leave their bike, all the way to paying and riding off.
02
Screens & states
Choosing a locker, navigation, payment and unlocking via Bluetooth. Plus the moments when something fails, including the backup QR code.
03
Weekly calls
Every week in the evening, at 9 p.m. our time, we showed the client in the US what was new and worked through their feedback.
04
Dev handoff
We fine-tuned components and screens directly with the iOS and Android developers so they could build them right away.
/Results(06)
337 screens the devs built straight from.
app users in the San Francisco area
screens ready for development
components that make up every screen
In practice
The iOS and Android developers built from the same components, so the app looks and behaves the same on both platforms.
The app has its own screens for when something fails. If a locker won't open via Bluetooth, it offers a QR code.
User count from the client. Screens and components counted from the Figma design.
I want a similar result/What the client says(07)
“The designed screens were always efficiently structured and technically well prepared. Whether it was components or individual screens, we developers found them great to work with.”
Martin SýkoraSenior developer
/More projects(08)
