RideSetup
I ride, and I could never find one app that set up mountain-bike suspension and tyres together, so I built it. Your weight and how you ride go in; pressures, click counts and a tyre psi come out, across 73 fork and shock models from eight brands.
At a glance
Section 1 of 5
The idea
I ride, and that is why I built it.
RockShox, Fox, Öhlins, DVO and Manitou each publish their own pressure chart, in their own format. Tyre advice is mostly forum threads. I couldn't find one app that did suspension and tyres together, so I built it.
How it works
You enter
- Your weight
- Ride style
- Fork and shock
- Wheel size and inserts
RideSetup
73 models from 8 brands, every figure sourced.
You get
- Fork and shock psi
- Sag in % and mm
- Rebound and compression clicks
- Tyre psi
Section 2 of 5
The problem it solves
The maths is a lookup. These were the hard parts.
Data in 8 shapes
No two brands agree on units, format, or even what to call the damper.
Two problems, one moment
Suspension and tyres get set up in the same five minutes, off the same two facts.
Set up in a car park
Full sun, one hand on the pump, gloves on.
What the chart gives you
- 'Between 65 and 90 psi'
- Your fork, but not your damper generation
- Nothing about tyres
What RideSetup gives you
- 95 psi, with the band underneath
- Sag you can measure to check it
- Tyres from the same inputs
Section 3 of 5
The process
Research
Every published pressure chart I could find, pulled apart into one schema, with tyres on top.
73 models, sourced
User interviews
Riders who'd never solved it. The usual answer to 'how did you set that?': whatever the shop did.
The trailhead constraint
Wireframes
One screen to the answer. Four principles, and three things it wasn't allowed to look like.
Constraints doc
Testing
Outside, in full sun, one-handed, with gloves. That set the target size and the dark screen.
44×44px targets
Design
Dark for the sun, amber because it holds up on dark, and the result is the largest thing on screen.
One screen
Development
One index.html, no build step. Supabase for accounts, Vercel for hosting, pull requests throughout.
68 commits
Section 4 of 5
What I built
One rule: you came for a number, so every decision shortens the way to it. I wrote down what it must not look like: gear shop, SaaS dashboard, fitness app.
Built for the car park
Dark by default
A mostly dark screen reflects less in direct sun, and amber stays readable on it.
Nothing under 44×44px
Whoever uses this has gloves on.
Every figure sourced
184KB of JSON, each number traced to a manufacturer article or a checked community source.
Tyres are half of it
Every fork calculator I found stopped at the fork. Tyres run off the same inputs, plus wheel size and inserts, and getting them wrong costs more grip than two clicks of compression. One set of answers gives the whole setup, suspension and tyres.
Section 5 of 5
Where it stands
Live at ridesetup.vercel.app. Sixty-eight commits from mid-June to mid-July 2026, all through pull requests. Renamed twice on the way: RideReady, Ride Setup, then RideSetup.
Availability
Taking on freelance projects
Replies within 1–2 days
Location
Remote · Bulgaria
Local time
The first call
Free, and commits you to nothing
Elsewhere