And I wonder if the article is correct in that they are pivoting away from segments. That seems strange since segments seem like the most compelling feature.
And I wonder if the article is correct in that they are pivoting away from segments. That seems strange since segments seem like the most compelling feature.
Route building and personal heatmaps are some of my favorite features, but there's so much that could be added (like a simple search). To some degree their customers are spread out over so many market segments beyond the original biking and running that they started with. Each segment has their own needs and wants. Then there's all the hardware (watches, power meters, trainers, etc..) that needs to be integrated and supported.
I posted it on HN but got flagged[1]. I still find it eye opening, a reminder that the code we write are products impacting the finite life of other people. Maybe we should have more modular, more open software as a standard so that other people can work on and deliver experiences that the original creators fail to deliver.
[0] https://web.archive.org/web/20200601152323/https://support.s...
I used it snowboarding and there's some way to track runs and push out the whole day of skiing as one post, but I couldn't figure it out, so I just polluted my own feed with these single run posts. Then for some of them I forget to start recording halfway down the run because once again thanks to the broken auto pause feature, so now I need to remember to start it up at the top of the hill in addition to already having to put on a snowboard binding. Then thanks to the auto pause and me forgetting about pausing the run, it records me shuffling about in the lift line and then riding 25mph on the nose on the gondola.
Or, if you happen to have an Ikon pass, the official Ikon Pass app (May work at ikon pass resorts without the pass — not sure?)
Both know the difference between a run and a lift. Slopes doesn’t quite get pauses. Not sure about how ikon handles it. (I don’t get too obsessive about it). Nice thing about ikon app is that it tells you which runs you took. (Slopes is seemingly adding this but it’s not prime time yet)
Most apps/startups begin as an exploration of product/market fit. They'll try a lot of different things and use analytics (even simple server-side stats) to determine what people actually use in the app. Very frequently, you discover that the things you thought your users would want are actually only used by 0.05% of your customers. Eventually you have to start shedding rarely used features and limiting free plans, even if it makes the non-paying users angry.
Truth is, it doesn't really matter if you're losing someone who spend 5 years on the free plan but refused to sign up for the paid plan. They're not converting to paid unless they're forced to, and you're not gaining any money by letting them stay on the free plan for another 5 years.
> but where are all the new and cool features that should have come out over the last few years?
Cutting rarely-used features like this one could be a sign that they're trying to free up engineering resources to ship new features.
This is true, but it ignores the importance of network effects in products based on social media/interaction. I'd guess that a huge part of the attraction and user retention ability of Strava is the social aspect, which they'd be crippling if free users migrated somewhere else. As a secondary issue, Strava also benefits from the data generated by free users, though I have no idea what the value of that data might be.
They paired back things that weren't working, moved to focus on revenue (as they weren't going to be able to grow into the social network for all activities like they tried).
I think it's the right strategy, but this move makes no sense. It's very easy for them to manage duplicate data, and I'm surprised to see them suggest users set-up their garmin device to connect directly to Apple. This essentially makes it easier for strava to be cut out of the loop in the future if the social aspect isn't working for you.
My normal morning jog goes under a large bridge. This often confuses my phone's GPS, leading it to return a spurious point or two a kilometer away. Strava is completely incapable of detecting these spikes (accelerating to 200 km/h when running is normal right?) and offers no way to edit them out afterwards, meaning all my speed and distance records, progression charts etc are ruined by junk data.
That's not what DCR wrote, that part was clearly about user perception: Strava has grown into something bigger than just that app that declares you KOM when you go really fast.
And it apparently isn't valuable enough to charge more for ($5/month)
What are you referring to? That Strava has to store&compute more and more data from a user the longer they are using the platform?