Client work / paid engagement
Shredder.
Find a riding partner. Track a day on the mountain.
- My role
- Sole engineer
- Working with
- Solo on the original app; later returned to work with the team
- When
- 2025 — initial build, then a later stint
My contribution
- App Store launch, delivered soloBuilt and shipped the original ski/snowboard app, from rider matching to activity tracking. Also built the staff dashboard.
- Rider-matching algorithmReturned to develop Shreddy, which scores riders by interests and preferences, and fix bugs as the user base grew.
The problem
The original brief was an app for skiers and snowboarders to find compatible riding partners and track their activity. Matching needed to account for ability, interests and what each person wanted from a day on the mountain.
What I built
My part
in the product.
Sole developer on the initial build, through to App Store release.
- 01
The whole matching system: a swipe-to-match flow between riders, and the pairing logic behind it.
- 02
Built activity tracking and rider statistics for skiing and snowboarding.
- 03
Took the original app through development and App Store release as its sole engineer.
- 04
Built the web dashboard used by staff to operate the app.
- 05
On returning: bug fixes and Shreddy, a rider-matching feature that scores stated interests and what users want in a riding partner.
The current product has expanded beyond skiing and snowboarding. The artwork shows the current product; I built the original app solo and later returned for bug fixes and Shreddy, the rider-matching feature.
01 / a closer look
Find someone
to ride with.
I built the original swipe-to-match app and the pairing logic behind it. Ability and riding preferences were central to the original skiing and snowboarding brief.
02 / a closer look
Built solo.
Brought back to help.
I shipped the original app through to App Store release and also built the staff web dashboard. I later returned to fix bugs as the user base grew and developed Shreddy, a feature that matches riders by their stated interests and preferences.
Decisions worth explaining
Why it works
this way.
Shreddy uses deterministic scoring over stated interests and riding preferences. The matching logic compares riders against explicit criteria without needing a language model.
Ability first, not proximity first. Matching people who ride at the same level was the point of the product, so skill signals drive the pairing rather than simply who happens to be nearby.
Tools used on this project
React Native / TypeScript / Convex / Clerk
Next project
Zums ↗︎
Earn from surveys and tasks. Manage it all behind the scenes.
← Back to this project in selected workSummer 2027 co-op · flexible term length