February 19, 2020
This is the first of a series I'll be writing where I share my invaluable, world-changing insights with companies small and large, who will then ignore me.
Summary: I've had this app since I started running at the end of 2010, so as to get in shape for the Bay to Breakers centennial. The "BtoB" is the longest, continuously held footrace on the planet earth (109 years and counting), from the bottom of the Bay Bridge here in San Francisco, to the Pacific Ocean's waves breaking 7.45 miles away.
I wouldn't be here running today without it, because I don't like running, and am not good at it (but do it because, per Jack LaLanne "I like the results"). Apps like this are critical for my unfortunate pattern of getting in shape, doing the run, then getting bored a few months later, then sedentary, then needing to start back up. Yes, I should schedule other races. I should also eat less sugar, save more money, and foster animals. I know I know I know.
Bit of History: I've emailed the creators a couple of times over the years. They've fixed most bugs, others they've ignored (or they dumped the offending feature), and oddly, they've completely ignored my suggestion to contact me regarding a variant of their existing program to make a lot of money (given the success of the iBeer, you'd think they'd be at least willing to come to the phone). Alas, not everybody is ready for #ThusSpokeKevinthrustra.
More info at http://felttip.com/support/run-faq.html
Again, they have fixed many bugs over the decade, and I think it's still a great little app.
Just Fix It: No doubt it's a small company, and no doubt they're in a tiny niche now full of competitors (they used to be one of just a few a decade ago). That being said, the following can't be that hard to fix. Most of these would have been caught if given to five beta-testers.
- Of the apps I own, this is the only one whose major functionality goes away with the flick of a switch. If you forget to put the switch back onto ringer (instead of buzzer), you won't hear the auditory cues. Is it really that hard to fix, after almost a decade of dysfunction?
- Pace. Don't care about my average walking pace: only care about the average pace during the running segments, AND my current pace: split the screen, showing both.
- Stretch Transitions: Don’t need so long of a pause between the ones done standing; do need longer amount of time to get to the ground, and between those stretches (saw the longer stretch duration possible in "settings, " but I mean this basic difference between stretches needs addressing).
- Stretch Tips: Be sure to have a few form reminders to clue users in: "flat back," "head turns opposite from legs," for each stretch.
- Run Distance Only: Users recognize that an API for other running apps is a bit much to ask, but how hard can it be to have your apps only total the running distance, and not include the walking distance as a separate stat?
- Bug: Used "pause" during a walk segment, and the app later told me I was running 4 minute miles. Don't think that happened.
- Music: Is there really that much demand for users wanting to skip sections? The fast forward and backward buttons do that, rather than control music. Having to leave the app to skip a lame song that's on an album or in a list is a far greater need.
Thanks for the runs folks, but could you JUST FIX IT.
