Have something to say?
Combined service intervals
Be able to create one service intervals that combines several intervals. for example, a rholoff hub should have it’s oil changed every 5000 km or after one year, whichever comes first. It would be great if you could create one service interval that “triggers” on whichever of those happens first, and that you can record the service and thus reset both intervals in one action.
Note to a specific tour
Sometimes, I want to document a noise or something my bike make during a specific tour. Would make sense to be able to have a note or comment field for a Tour.
Mechanic service reports: your shop's work straight into your customers' logbook
Hello, I am a mechanic and would like to encourage my customers to use your app by uploading maintenance information to their accounts myself. Would it be possible to allow customers who wish to do so to grant access to their mechanic? Thank you in advance for your response.
Add/remove components and/or rider gear per activity
The ability to add/remove manually an “In Storage” or an “Installed” component, rider gear or other stuff to a specific activity. Not install permanently, exemple, I’ve many shoes for specific rides on the same bicycle, instead of installing a shoe to a bicycle the counts for every activity I only chose that shoe for that activity only ou others in the future, that can be applied for specific components or other stuff. The same can be applied to “Installed” components or gear, exemple, on an activity I’ve had to change the wheelset, only for that activity. Then I just go to the activity, that has the list of components and gear I used and remove the wheelset and add other manually, but the defaults installed components and gear remains the same for the next activity. Kind of complex, don’t know it’s possible but useful when you are an athlete that constantly changes gear and components 😆. The alternative is to use Strava tags that can remove or add that gear, but that’s another topic…
Component ride history
Along side with the component install history it could be also the component ride history, listing all rides where it has been used on.
Only count the activities a component was actually used on
Right now every component installed to a bike picks up every ride on that bike (depending on the install date). If you keep one wheelset for the trainer and another for outdoors, or swap between mountain bike and gravel tyres on the same frame, both sets wear out on paper while only one of them is being ridden. Same story if you rotate several pairs of shoes. You can off course uninstall and later re-install but that is cumbersome. I'm planning to fix this in two steps. First, by the kind of ride. On a component you'll be able to say it only counts for indoor rides, or only outdoor, or only for a particular sort of ride — road, gravel, mountain bike, e-bike. Strava already records which kind each activity was, so this works with what you've uploaded already, including rides from months ago. It stays off unless you switch it on for a specific part, so nothing changes for anyone who doesn't want it. Second, and I'm less sure about this one: tags. For things the kind of ride can't separate — four pairs of shoes, two identical wheelsets — you'd give a part a tag, add it to your Strava ride title like #raceshoes, and only that part picks up the ride. It depends on you remembering to type it, which makes it the weaker of the two, and the first step may well cover most cases on its own.
Bike fit — save a rider's fit sheet per bike (new Utilities tool)
Let me record my bike fit per bike and find it again later: the numbers a fitter wrote on a sheet (or that I measured at home), attached to the bike they belong to, shown on the bike detail page, and reusable when I set up a new bike. A new Utilities → Bike fit tool, following the tyre-pressure and suspension tools exactly.
Bike transfer with components — server-side deep copy to another user
Let me transfer a bike and its components to another user. Primary use: selling a bike. Secondary: forking a build someone likes. Server-side deep copy into the recipient's account; the transferred bike carries its accumulated distance as manual base distance and can then be linked to the recipient's own Strava account.