From my ride records to our shared riding platform.
Orider did not start from a grand business plan.
It grew from one long-time cyclist and developer fixing the things that felt missing during real rides: records, sensors, routes, and group riding.
It is too early to call it finished. Still, I hope Orider can grow into Our Rider and Open Rider: a small gift that the cycling community can use, question, and improve together.
Focused while riding, thoughtful after the ride
When you are riding, the screen should not get in the way.
After the ride, the record should open up enough to understand the route, the body, the group, and what could be better next time.
Web
Activity details, fitness trends, routes, segments, groups, and events for a larger screen.
App
Speed, distance, maps, sensors, route guidance, and group location sharing while riding.
Direction
Public repositories, a community hub, developer participation, and governance for a rider-owned platform.
Service
Open the Orider home to see the dashboard, records, and community flow. Some screens require sign-in and ride data.
If you are new, start with these paths
It is closer to a draft we improve together than a finished product
The screens and features already work, but there is still a lot to improve.
There are bugs, some screens need better explanations, and the app and web experience is not yet as smooth as it should be.
So I want to introduce Orider honestly: why it was made, what it tries to solve, and where it needs help.
It is not enough yet. I would like to improve it together.
From a tool built by one person to a platform improved together
Orider should not become large by looking like one person's closed service.
It should become better because riders bring their own experiences into it. The board, creator hub, and public repository are the first doors into that process. You do not need to write code to point out confusing screens or missing workflows.
Public repository
Starting with the intro docs and web code, the project is being prepared for issues, pull requests, reviews, and CI-based contributions.
Community hub
A place where developer ideas and real rider workflows can be discovered, discussed, and improved.
Developer participation
Personal data APIs and recipes can let riders build dashboards, alerts, reports, and automation from their own records.
I hope the records respect a rider's time
Solo days
Speed, heart rate, power, elevation, and routes become useful material for the next ride.
Group days
Location sharing, member activity, courses, and event flow can help riders move together more safely.
Review days
A ride should not end as numbers alone. It should connect to how the body felt and what comes next.