Improvements for Gear section of Strava (Cycling)

I am at a crossroads with equipment list management. I am about to dump tracking all my components as I have seen no improvements in a very very long time. I switch around wheels and tires all the time and that tough to track the way it's currently setup here on Strava. But now I have recently cracked my frame and is being replaced under warranty. I will be moving all my component to this new frame, so this is where it will be a complete failure for me. How do I track going forward? Components are tracked by Frame and not individually.

 

Support Summary:

1. Allow components to exist independently from bikes/frames

Instead of limiting only one active version of each component per bike, components would exist as a "pool" and could be removed from a bike without being retired, could be "shelved" for any amount of time without accumulating mileage, and could be easily switched between bikes. Like different tiers - at the top level there is a group of frames, and under that is a group of components, any amount or type of components you wish to track. Then there is freedom to match the components to the frames in any desired way. 

2. Ability to add historical usage to a frame or component

As the system currently stands, bikes and components added to Strava are treated as new, with zero use. Of course, we know this is only the case a fraction of the time. For a functional gear tracking system there needs to be a way to add an item to the system with historical mileage/usage. 

3. Track Gear in hours as well as miles

4. Ability to set notifications for when a component reaches a certain amount of use (miles or hours)

5. Add maintenance records, or simply a notes field to any Gear item to keep track of when equipment was last serviced

Are there any additions, or major feedback trends that I missed? -Elle

280

Comments

253 comments
  • 3. Track Gear in hours as well as miles

    +1. I log every bike trip with Strava. Problem is, I ride MTB/All Mountain on very tech/extreme trails. Tracking kilometres is pointless, but having hours would be perfect to monitor lifing of components.

    0
    Comment actions Permalink
  • +1 For tracking components independent of the frame.  Ideally, we would have at least 2 options when adding used components to a frame: 1) Pick a start date from a previous frame/bike so everything since then gets picked up or 2) enter a starting mileage.

     

    0
    Comment actions Permalink
  • Recently had some free time, wrote my own app for this. It's very beta but works.

    https://fitbike.herokuapp.com/

     

    0
    Comment actions Permalink
  • Need to be able to track shoes used for hikes and backpacking just as we can for runs.. Should be a simple task for Strava programmers.

    0
    Comment actions Permalink
  • +1 on the shelf option. It would also be good to be able to share some components with a friend. So that if my wife borrows my wheels her usage of them would be added to the total usage of the wheels.

    0
    Comment actions Permalink
  • Winter is coming, CX season is here, studded tire season is on the way...

    Once again I ask that we get the ability to assign bike tires to rides. Please make this happen.

    0
    Comment actions Permalink
  • Any news about expanding the possibilities to track individual parts is the Gear section.

    I really want to be able to reinstate retired (or paused) parts.

     

    0
    Comment actions Permalink
  • Now virtual rides are a thing on Strava it would be a good idea to be able to add turbo trainers to the list, so you can track 'milage' on those too.

    0
    Comment actions Permalink
  • As mentioned elsewhere, I'd love to be able to re-activate retired gear. What do I do for switching between wheelsets (aero vs climbers, e.g.)? I definitely would love to see this happen as I rely (maybe wrongfully so) on the gear index to track usage on things like chains, cassettes, tires, and so forth.

    0
    Comment actions Permalink
  • Updated with kilometers for those folks on the other side of the pond.

    https://fitbike.herokuapp.com/

    0
    Comment actions Permalink
  • Merely transferring my similar request on time tracking for components:

     

    Would love a feature where it logs how many hours the components have been used instead of just the distance.

    I think time used would be also relevant for maintenance purposes because some manuals uses time instead of distance as an indication for maintenance.

    0
    Comment actions Permalink
  • New to Strava user here... this request is 3.5 yrs old. Is there any progress on this? Any chance of it happening? Or should I just stick to something else for tracking equipment?  Seems like you've got a real good opportunity here... too bad it's not going anywhere.

    2
    Comment actions Permalink
  • lots of valid input being ignored here. Nike+ used to be big as well :)
    1
    Comment actions Permalink
  • Could Strava expose time within their API?

    I don't see it here- 

    https://strava.github.io/api/v3/gear/

    0
    Comment actions Permalink
  • I would love to see a more advanced Gear section. As Strava is used to track rides, it provides input how long and when your equipment has been used. Based on this, I track the mileage of specifc parts eg. chans, sprockets, for replacement.

    Strava should move towards an equipment management system.

    1
    Comment actions Permalink
  • I made an application where you can track different components using Strava data.  You can take the parts off of one bike and put it on another and the usage is persistent.  It's at http://cycle-fyi.parseapp.com/

    For time, I usually just figure how many miles I would ride in that amount of time.  

    0
    Comment actions Permalink
  • Ok, J Scott, Sounds cool, so I'll bite - I set up two bikes and two wheels to test, one bike is named test, the other is named exactly like it is named in Strava - I assigned the two wheels (front & back) to the bike in your app, added a new activity in strava, then I come back to your app to assign that activity to a bike, and the associated components have the mileage added - nice job! 

    If the bike is named the same as in Strava, can you automatically associate the activity to the bike and components in your app?

    0
    Comment actions Permalink
  • Johan, I avoided associating the gear data in strava with the gear data in my application.  The only thing that is automatic between the two is retrieving rides from Strava so that they can be assigned to the components on whatever bike. 

    0
    Comment actions Permalink
  • J Scott, I also bit and like the features you have put in. But if I understand it correctly I would need to go to your site after every ride to log the miles. This is a show stopper for me. It's too bad this isn't  directly integrated into Strava where you have the option to select the bike used for any ride. 

    0
    Comment actions Permalink
  • David Fisch, the reason I did it this way was so there is a shelf integrated for people that like to switch out parts.  If it were truly integrated with Strava the way you describe it, then that would not be possible.  

    On another note,  there's no need to go to the site after every ride.  You can assign usage whenever you want.  Once a month or once a year.  

    0
    Comment actions Permalink
  • This is just another way of expressing many ideas previously suggested but here goes anyway:

    I think it would be really useful to allow the 'pausing' of a component. Currently you can 'retire' or 'delete' which does not cover the possibility of changing a component for example, seasonally. I propose the addition of 'pause' and 'resume'.  The idea being for example to have  a winter tyre which was taken off, and  'paused' for summer without clocking up distance. It could then be 'resumed' at a future date and begin clocking up its distance again.I think it would be really useful to allow the 'pausing' of a component. Currently you can 'retire' or 'delete' which does not cover the possibility of changing a component for example, seasonally. I propose the addition of 'pause' and 'resume'.  The idea being for example to have  a winter tyre which was taken off, and  'paused' for summer without clocking up distance. It could then be 'resumed' at a future date and begin clocking up its distance again.

    0
    Comment actions Permalink
  • I think the absolutely flexible way of solving this would be to make components exist independent of a bike, i.e.

    1. there are bikes a user owns (the way it is today)
    2. there are components the user owns (can be defined independent of a bike)
    3. any component can be marked as "installed" on a bike with start date and end date - the component will accumulate mileage/time when strava rides are logged for the bike the component is installed on
    4. (sort'a extension of #3) there could be components which are not "installed" on any bike for some periods of time - and that's fine, the components just don't accumulate any mileage/time during that period.

    I think this could be a good idea for a separate app which stores the component list and their installed/shelved periods and integrates with Strava to pull data about bikes and activities. Doesn't sound crazy hard, the trickiest part is the time interval logic :)

    0
    Comment actions Permalink
  • I totally agree with you Mikalai, this would be the perfect solution. Now the question is, how can we get Strava to implement this? It has been two and a half year since this idea was brought forward by Steve Saeedi and I think it is about time for Strava to make this very useful thing a reality.

    0
    Comment actions Permalink
  • I made an app like that.  You sign in through strava, create a bike, add components, and then assign the activities to the bike.  You can take the components off of the bike and put it on a shelf.  It will still retain the mileage information and will start accumulating again once you put it on another bike.
    Here's the app:  http://cycle-fyi.parseapp.com/

    Also, here's a short screencast showing how it works.  https://youtu.be/VA9ndV3FtfU

    0
    Comment actions Permalink
  • J Scott Chapman,

    Your app is a great start!

    Two features which are missing for me personally:

    1. Being able to specify date ranges of component usage in the past. You know, I often switch component and only remember to mark them as switched weeks or months later. Your app only allows to move component to the shelve right now (but doesn't allow to mark the component as shelved 1 week ago etc)
    2. If you can have a separate field "Strava Name" in your bike configuration, so no matter how I call the bike in your app - it knows that it is called xyz in strava and thus all rides on xyz bike should be automatically counted for the bike (and all components).

    Probably this forum is not very appropriate to discuss your app though - do you have a better place, e.g. github project?

    0
    Comment actions Permalink
  • Hi all,

    since J Scott's app didn't work for me (I didn't see any activities and the developer console told me that I was getting some HTTP errors from the app) and I didn't like the idea of assigning components manually, I decided to make my own app. It does everything except notifications, in particular:

    • loads bikes and activities from Strava, therefore no need to assign bikes to activites
    • components exist independently of bikes
    • components may be assigned to occupy a role (frame, chain, tire, etc. — can be customized) at a bike for some time
      (and since only one component can occupy a given role, it's only necessary to specify when the component was added)
    • components may be temporarily switched for a single activity using a hashtag (e.g. #cx in an activity title will use a cyclocross tires instead of road tires)

    As an example, my config is in the first picture and the output is in the other.

    Unfortunately it's just a console tool now, I haven't managed to create a web interface yet, but I'll work on that next week. If anyone wants to have a look anyway, here's a github repository: https://github.com/liskin/strava-gear. There's even a gitter chatroom if you want to talk about it.

    Hope this will be useful to someone :-)

    0
    Comment actions Permalink
  • Hi Strava

    Any chance of an update as to when this idea will be taken up. All we are asking for is a starting mileage :)

    Thanks

    0
    Comment actions Permalink
  • Yes, we need this. I run winter tyres and wheels. I will retire my winter wheels and tyres and put them in the shed until next winter when they will be brought out of retirement. I guess I am not alone....

    0
    Comment actions Permalink
  • I put this through to Strava & they suggested I post it here

     

    In the components section under My gear for Bikes it would be great to include functionality to temporarily suspend a component. I as many other riders will swap things around depending on ride location, weather, etc. I regularly swap wheels, cassettes, tyres, etc and with the only option to retire I have no ability to accurately track usage (apart from manually).

    The way I would see it working is if I change a cassette I click on a suspend button. I would go to the suspended cassette and click on unsuspend.

    2
    Comment actions Permalink
  • I think the ability to add historical mileage data to the gear section would be enormously helpful.  I have been cycling since before Strava started and even before GPS computers so it would be great to be able to add the actual total mileage on my bikes so I would have more accurate totals on Strava. Right now the only way to add mileage is to manually add some really, really long rides (and I would have to add many of those since there is a limit of 999 miles) but then that effects my biggest rides etc.  Some way to adjust starting mileage from zero would be great.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post