Cicles JK
Designing the bicycle-rental ecosystem — the platform staff use to run the fleet, and a proposed booking flow for customers.
- UX/UI designer
- 2025
- Client project · 100x100net
- Admin platform · Public booking (proposal, not built)
- Staff · customers
A bike-rental shop on the Costa Brava.
Cicles JK rents electric, road, gravel, mountain, touring, junior and kids’ bikes from Palafrugell — by the day, the week or longer, to individuals, hotels and campsites, with accessories, delivery and pick-up. Bookings, fleet, customers, prices and holidays were all handled by hand. The project brought the whole operation into one platform, and proposed how customers could book directly.
Behind every booking, an operation.
Renting a bike isn’t just a booking screen. The bike has to be available, in the right place, maintained; staff need the rental details; it has to come back, be checked and become available again. So I designed the service, not a single interface.
The internal product exposes complexity because staff need to manage it. The customer experience hides it, so people can simply rent a bike.
The backstage.
The dashboard answers the morning questions first — active bookings, bikes out, returns this week, payments pending — then shows the fleet by category and state, and the rentals that end soon. Every bike has a state that decides whether it can be rented, so availability is never just “does the bike exist?”.
Closing the loop.
A rental only ends when the bike is back and checked. The return flow goes bike by bike: good condition, to the workshop (with what’s wrong and a photo), or not returned — and checks every accessory, so a missing GPS is charged before the booking closes.
That single screen is what turns a bike from “Rented” back into “Free” — or into “Workshop” — keeping availability honest for the next booking.
The frontstage — a proposal.
For customers, I proposed a public booking flow that hides all of that: choose dates and a type of bike (with size on the card), add accessories, enter your details, choose shop pick-up or delivery to your accommodation, pay, and get a confirmation that tells you exactly what happens next.
- 1
- 2
- 3
- 4
- ✓
Why types, not models.
If a customer books one specific Atala Cult 8.1 and that bike goes to the workshop, the booking breaks. If they book “an electric bike, size M”, staff can hand over any free one. Booking by type protects availability — the backstage stays flexible while the frontstage stays simple. It also matches how people choose a rental: by type, size and price.
I explored three early versions. The proposal builds on the third, and refines it: size is picked on the card, availability shows on each type (“Available”, “Last 3”), and anyone unsure gets a WhatsApp shortcut to the shop.
- + Flexible for the shop
- – Delivery, addresses and payment crammed into one last step
- + Familiar e-commerce pattern
- – A bike in the workshop breaks the booking
- + Protects availability
- + Size and availability on each card
- + Delivery gets its own step
Built for the street, not the desk.
People rent bikes on holiday — walking around town, at the hotel, a few minutes before riding. So the booking proposal works one decision per screen, with a sticky total and “Continue” always within thumb reach, and delivery times as big tappable slots.
One booking, both sides.
Following a single booking through the system shows why the two products have to be designed together.
- Books 2 electric bikes (M, L) and a junior bike for 14–21 October, delivered to the hotel
- The booking appears on the dashboard and in Bookings
- A free bike of each type and size is assigned → Rented
- Prepares bikes and accessories, delivers to the hotel at 11:00
- Rides the Costa Brava
- Registers the return bike by bike: good → Free, damaged → Workshop, missing GPS → charged
The details that make it run.
Bookings with filters by customer type, a calendar where holidays and seasons drive the price table, customer and bike records with their full history, and accessories managed like stock.
Designing connected experiences.
Cicles JK taught me to design frontstage and backstage together: every choice a customer makes becomes work for someone in the shop. Designing for staff and customers at once — B2B and B2C — meant one consistent model of bikes, states and bookings across every touchpoint, with business rules like holidays, prices, delivery windows and returns shaping the UX.
- 2
- 17
- 10
- 3