Skip to main content

For a while now, the route builder has been really slow. Especially extensions VeloViewer and Wandrer are taking sometimes 10 to 60 seconds to make a new waypoint. It seems the builder is constantly recalculating the route. With VV and Wandrer, there are more waypoints than in a regular route. 

Why is it Strava’s fault if third party extensions are slow? 

Not saying there's a fault. Saying it's slow. Maybe there's something that can be done. Not sure which side can do something.

Why is it Strava’s fault if third party extensions are slow? 

In one of the discussion threads that aren't visible anymore, some users pointed out that the slowness start correlated with the Strava API change. 

​@Jana_S The API didn’t change, “only” the terms for using it. Of course if Strava changes the route builder that affects browser extensions but it’s the responsibility of the extension programmers to adapt. Unlike the Strava API where everybody can expect that their programming keeps working whatever is changed a browser extension doesn’t have this claim and can only hope that the underlying website doesn’t change fundamentally.

Reply


Terms & ConditionsCookie settings