Hey everyone!
I'm definitely an outsider here, for a couple of reasons. First, I ride an e-MTB, although I keep the motor off most of the time because my doctor told me I need to lose some weight. Second, I mostly stick to bike paths, doing 20–40 km rides.
So looking at the stuff you guys post here, I'm definitely not much of a mountain biker 😄 My idea of extreme riding is making it down a moderately steep hill without falling off.
Anyway, I'm a software engineer, and one day I wanted to measure my pedaling cadence. I figured, if a phone can count steps, surely someone has already made an app that can count pedal rotations, right?
Well, I couldn't find one that did what I wanted. So I thought, how hard could it be? I'll just build one myself.
Fast forward two months, and I'd built an Android app called Cadence Coach. It uses your phone's motion sensors to estimate cadence without needing a separate sensor on your bike.
About a month ago, I finally bought a proper crank-mounted cadence sensor because I realized that without something to compare against, I had no idea if my app was actually measuring anything correctly.
I've now gone through seven versions of the algorithm and logged around 20 hours of riding while comparing the phone's readings with the actual sensor. The results are surprisingly good during steady pedaling, though there are still some situations where the algorithm gets confused. To be fair, even the dedicated sensor occasionally spits out weird numbers.
If you're curious about the technical side, I wrote up the experiments, results, and failures here:
https://suncokretlabs.com/blog/cadence-accuracy/
And that got me wondering: what would happen if someone tried this on actual MTB trails?
Looking at my ride data, I can already spot noise from rough pavement or when I drop off a curb. But that's pretty mild stuff. I'd love to see what happens when the algorithm has to deal with some proper rough terrain and sudden movements.
Can it tell actual pedaling apart from bumps, vibrations, and the rider moving around? Or will it just start spitting out complete nonsense?
Honestly, I have no idea. And that's exactly why I want to find out.
I don't really expect this app to become a serious MTB training tool. Maybe it'd just be something fun to play around with, check your cadence, laugh at the numbers, or notice something interesting. Assuming the numbers make any sense in the first place!
Or maybe the whole thing falls apart the moment someone hits a proper trail.
Either way, I'd love to know. I enjoy solving engineering problems, and I've gotten a bit obsessed with figuring out just how far I can push this algorithm.
So that's why I'm here asking for your help.
Cadence Coach is currently in closed beta, and I'd really appreciate some ride data from actual MTB trails, especially ones with lots of bumps, rapid cadence changes, and all the other stuff I can't really reproduce on my usual rides.
All you need is an Android phone. No cadence sensor required. Even recordings where the app gets things completely wrong would be useful — they could help me understand what's breaking and why.
And if you happen to have a dedicated cadence sensor to compare against, that would be even better!
If anyone feels like giving it a shot and sharing some recorded data, or even just telling me where it screws up, I'd really appreciate it. I'm not trying to collect installs just for the sake of it. Actual feedback is what I'm after.
Full disclosure: the app has some paid features, but beta testers can try them for free using Google Play test purchases. Just make sure Google Play shows it's a test purchase before confirming. No need to spend any real money.
If you're interested, here's how to join:
https://suncokretlabs.com/cadence-coach/testing/
The algorithm works pretty well on my rides so far. But apparently that's not enough for my curiosity. Now I want to see what happens on trails I'm not even brave enough to ride myself 😄