Ferrule
Concept · A bike workshop app where customers book a time and follow their repair live.
Concept project. Ferrule isn’t a real business: we made it to show bookings and live repair status, both sides at once.
- Type
- Concept
- Sector
- Bike workshop
- Year
- 2026
- What we did
- bookings and live repair status, both sides at once
- Built with
- Astro, Preact, Postgres, Vercel
The idea
A bike workshop runs on phone calls: booking, “is it ready yet?”, “can we change the chain?”. We wanted one app that answers all three. The customer books a time that really fits the mechanics’ day, sees where the bike is without calling, and approves extra work with one tap. The workshop sees every bike on one board.
What we built
Both sides at once: the customer’s phone and the workshop board, working on the same data. A booking appears on the board; moving a bike updates the phone; approving a new chain updates the board and the price. Open it on your own phone with a QR code and watch the two screens talk. Every action shows how long it took. Try it without signing up: each visitor gets a sample shop that resets on its own.
How it runs
- tap response
- Not measured yet
- ready to use
- 3.2 s
- dropped
- Not measured yet
Lab measurement: Mid-range phone, emulated (Chrome, CPU ×4) · Nov 16, 2026
| Device | Tap response (INP p75) | Ready to use | Dropped (heaviest screen) | Measured on |
|---|---|---|---|---|
| Mid-range phone, emulated (Chrome, CPU ×4) | Not measured yet | 3.2 s | Not measured yet | Nov 16, 2026 |
Lab only, not yet a real phone: an emulated mid-range phone (Chrome, CPU 4× slower) on an emulated slow 4G connection, against the live demo from South America, so every request also crosses the Atlantic to Frankfurt. Ready to use: from opening the page until the app answers a tap, on a first visit (1.3 s on a returning visit). On the server, booking, moving a bike and approving took 59, 36 and 29 ms (p95).
