New Strava app for Apple Watch to support Series 2+

We are excited to release an updated Strava app which supports standalone recording using the built-in GPS of the Apple Watch Series 2+. 

Please note: To support the GPS in the Apple Watch Series 2+, we redesigned the app to work separately from the phone. Even if your watch still connects to the GPS from your phone, the app functions independently on the watch.

If you're experiencing technical troubles installing, recording, or syncing Apple Watch activities, please contact us directly by submitting a ticket at the bottom of this post. 

Learn more in our Apple Watch article

21

Comentários

903 comentários
  • Hi Elle,

    Strava on AW2 seems to be released a bit pre-maturely. I don't really mind running with a "beta" app and I'm glad that I don't have to carry around my phone anymore. It's irritating though that I'm running PR's this whole week because of the inaccurate GPS data. Fix this issue first please! The collected data is the backbone of your entire system. It needs to be correct. I wouldn't mind the option of direct data transmission from the native apple app if this means more reliable data. 

     

    1
    Ações de comentário Permalink
  • Two questions:
    1. Does it works in treadmill or only outside?
    2. Why don't put a pop-up of mille or Km split Just Live Garmin?

    0
    Ações de comentário Permalink
  • This update has made the app totally unusable on my series 1 Apple Watch, stops recording after 3 miles of a 10 mile activity then doesn't sync. No solution from support so I've given up using it and will drop to the free version. Pointless paying for features you cannot use.

    3
    Ações de comentário Permalink
  • @Salvi Becca I don't think people understand that if they are commenting on this post, THEY are beta-testers. If anyone read Elle's post and are responding here you are a beta-tester. If you have your apps to update automatically, that's your fought. Turn them off. I never update automatically because it can break something working before it's been tested. If you update your apps or iOS as soon as a new one is released YOU ARE a beta-tester wether you like it or not. Wake up people that how developers test "real world" scenarios. Feedback is essential. However, I do think this should have been released on Test Flight first and a invite code sent out.

    -10
    Ações de comentário Permalink
  • @Stephen Thomas technically speaking Strava cannot import from Apple Activity or Health App, what they can import from is Health Kit which is the API interface used behind the scenes to record data metrics. That's what those permissions you setup when install app are for. The Health App is the UI that has the "white box with heart icon" and that includes all the graphs and stuff. When you drill down into the sources and individual data parameters, that's where the API data is store for each app. I'm not a developer but have some understanding (after research) of the convoluted process. Apple tracks EVERYTHING, every second of the day then allows what data it wants to allow back to the app. I used RK today and it showed my activities in the Apple Activity app quicker than the RK app did. It even showed my splits (which is usually doesn't). After RK synced my data, my split times in Apple Activity app disappeared and only show an AVG time. I hate this and RK devs say it's Apple that does this to probably "simplify" data. But given it shows up, this tells me that the data is there in Health Kit, but Apple limits it. Ticked they think they are in control of my metrics.

    Whether it's Apple being a bully or other apps being twerps for not wanting to bow to Apple's control, apps that work give in to a certain extent. Run Gap however can pull data from just about any app, but the UI and graphs need a major update and depending on how data is fed into Health Kit it can produce duplicates. Data imported from MapMyRun sucks as it doesn't title activities properly (Untitled). I wish someone could get it right and stop fighting over something so menial. It's the paying customers and users who suffer!

    -2
    Ações de comentário Permalink
  • @Cameron Olsen it could all be remedied with data point smoothing. Apple Workouts does this, but WAY too much! How hard is it to use curves instead of straight paths? NRC does't ping often enough (several seconds apart or more) There could be some kind of compromise you would think. It's like the GPS is trying to track the movement of the watch on the wrist with a light beam and can't lock on it's EXACT position. Is the signal not broad or good enough to track someone? Is the Hardware on the AW2 that lame? There is no way anyone runs that far out line and this looks like it was a track too.

    -1
    Ações de comentário Permalink
  • Using the AW2 native running app, my GPS has been super accurate. (Mapping looks dead on as well) Way more accurate than my Fitbit Surge while using both at the same time. So In my experience it doesn't seem to be an Apple GPS hardware issue.

    Data/splits (especially at the beginning of a run) seems to be where things get wacky when I started using the strava app, and other 3rd party apps.
    So data sync/conversion more so as the opportunity than any hardware issue. Again, that is just my observation. Thx

    0
    Ações de comentário Permalink
  • @ Matt Kornegay do then please explain how someone is supposed to AVOID being a beta tester for Strava? When an update is released to the app store, when do I then apply it to ensure I am not considered a beta tester and it is a "production" update? If there was a notification that the update was considered beta, I would not have applied it. And the "golden rule" of beta testing is that you should be able to go back to the mainline production code, which we cannot. Your statement is completely inaccurate.

    4
    Ações de comentário Permalink
  • I had a problem with the auto pause. Every time i lift my hand to check out the speed/time etc. during the run, Strava went into auto pause for 5 sec or something even If i was running pretty fast. So i had to stop the run, end the session and turn of the auto pause

    0
    Ações de comentário Permalink
  • @ Matt Kornegay
    Perfect, very well written and explained!
    Thanks!

    -4
    Ações de comentário Permalink
  • Asking people to turn off updates is a horrible idea, that's the only way to keep things as up-to-date from a security perspective as possible, and it's unrealistic to expect the average user to remember (or care) to update them manually on a regular basis.  That's why those updates are on by default.

    Apple does have an entire ecosystem for beta testing called TestFlight, that's how legit Apple developers beta test.  They don't push something experimental to their entire install base to see what happens.  The problem here is that Strava had an old app originally written for AW1 users, that AW1 people loved.  And instead of adding new AW2 features to it, they created a whole new app for AW2 users that threw away the features for AW1 we loved.  Instead of creating a new app "Strava for AW2", or renaming the old one "Strava Classic" or something, they just decided that all of their users got the new one, chasing the cool, shiny features of the AW2, and the AW1 folks are just out of luck, with no warning, unless we want to go spend $500 on a new watch.  Or switch back to NRC, MapMyRun, or most of the other (less nice) running apps that still support tethering.

    Disappointing for sure.

    7
    Ações de comentário Permalink
  • I agree with the other AW1 users. This was an update that broke the functionality that I was using. I liked the mirroring between watch and iPhone and this was working flawless.
    With the update I cannot use the watch anymore as the location being sent to the watch is not as accurate as the iPhone. I went for a run where I started the recording on both devices and the one on the watch was not accurate.
    I pay for a service where I expect high quality software. I think there are a lot of AW1 users at the moment that doesn't want to support your product anymore. Please find a solution quickly or revert to the old app that was working. You could maybe use previous release from your repository and send out as a Strava for AW1 app to the app store?

    Until I see a new update I will use RunKeeper and I'm considering cancelling my subscription when it's time for renewal.

    A UX error in the latest WatchOS app:
    Before I could stop the recording by tapping hard on the screen but now I'm changing record type. When it's raining it's hard to swipe on the screen but the hard touch did alway work.

    7
    Ações de comentário Permalink
  • I gotta say to the folks who are claiming we are all beta testers - that is baloney! I should not have to assume that ordinary app store updates of an app I've used for well over a year is suddenly a beta version. There are other mechanisms in place for beta testing where apps can be distributed to willing participants outside the app store process.  The app store update mechanism is supposed to be for finished, working software.

    I was perfectly happy with version 5.12.0 of Strava for iOS and Apple Watch which came out February 6th. When 5.13.0 appeared on February 21st, the version notes say NOTHING about beta, and only mention changes to Apple Watch Series 2 support. Since I don't have that device, why should that clue me in that I should NOT update?  And why should I have to jump through hoops to keep that one app from updating?

    I actually do NOT have auto-update on, I actually look at the updates. But you who are claiming this is a beta are being unreasonable - NOTHING marks it as a beta.

     

    8
    Ações de comentário Permalink
  • @Matt Kornegay...wow...this comment..."I don't think people understand that if they are commenting on this post, THEY are beta-testers...If you have your apps to update automatically, that's your fought...blah blah blah...Wake up people"

    For me, the update read "bug fixes". That's it. So I accepted the update as some bug fixes, and then suddenly my cycling experience was upside down. Maybe you should "wake up" and read/comprehend this thread before posting a condescending comment like this. There are ways to beta test an iOS App. It's not misleading everyone and hoping for the best.

    I absolutely would not have updated if it said:

    "-completely redesigned app that has only been conceived for standalone AW2 runners. -Cycling experiences not even remotely considered -AW0 or AW1 experiences not supported -tethered functionality broken - AW heart rate monitor for cyclists broke -external sensors (powermeter, cadence, etc) broken -premium features like beacon no longer work -Running distances not correct -audio cues broken -etc etc etc -P.S. everything is broken - P.S.S. this in beta state -P.S.S.S. download at your own risk"

    Yep should have been a Test Flight first because the current state is not acceptable for a public release. Period.

    7
    Ações de comentário Permalink
  • Any way to revert back to the original app? even if i could download two different ones to have on my watch.  or at least choose that I want to just use the watch to control my strava on my phone like if originally did, because I can't use my cadence sensor now with the apple watch. so now i have to hit start on my phone and my watch and record two simultaneously routes and one will have my cadence and one will have my heart rate, not very useful any more.  the main reason i bought an apple watch was so that i could control my strava on my phone without having to pull my phone out : ( and average mph is more useful than instant mph when your mountain biking, i already miss that feature now in this new update.

    8
    Ações de comentário Permalink
  • There is a simple $10 solution.  Use Runmeter or Cyclemeter and pay the $10 for Elite.  It does everything you want and even before the Strava update it was a much more feature rich app on phone and watch.  It will automatically send your workout to Strava upon completion.  So you have the best of both.

    0
    Ações de comentário Permalink
  • Ok people, lets stop this conversation about beta, non-beta. This doesn’t lead to anything and doesn’t help improve the app.

    My English is poor but Matt wrote it very well. What we both wanted to say is that a couple of years ago companies released their products when the products were compleately finished as they couldn’t change or improve them afterwards.

    Today it works differently: often companies release a product/software as soon as it is in a basic-status, often with plenty of bugs. Then they improve it with more or less regular software-updates. Some companies listen to their community feedback (that’s what we do here.. we are the live-users!), others don’t.
    Nowadays often you see a new product with a list of feature but half of them will be avaiable only months after the release with updates.
    That’s excactly what Strava does now. See Elle’s list on page 1.
    And tethering will – or better «has to» - get more importance in that list.

    -2
    Ações de comentário Permalink
  • If the update on the App Store would of said what the actual update was instead of "Bug Fixes", I know I wouldn't have updated and after reading through this thread I know I'm not the only one.

    Feel like Strava duped us into the updated by not giving us all the info about a major overhaul on the app. Instead we get "Bug Fixes".

    0
    Ações de comentário Permalink
  • @John Zurwarski, @Terry Shaw. I agree that Strava had screwed up and in no way and I sanctioning their development methods. Yes I would be ticked too if I had an app (especially paying for it) that worked and then one day it didn't. In my approach to call ppl "beta-testers" I was trying to communicate that we all are to some extent wether we like it or not. How many times has Apple pushed out a new realease and it change or break something that worked fine? I always wait to update my iOS until the bugs are worked out (multiple versions later) However, I believe Strava did this at the expense of its paying customers too. Which I believe to be an atrocity. I am a beta tester for RunKeeper and they have released v7.9 which I am testing through the TestFlight app. Their current version is 7.8.1. So I can agree with everyone's frustrations.

    Yet, Strava is using this forum and current release to document the problems. Being on the other side of the fence with the AW2 then I was excited to see the release...finally! The whole point of even having an overpriced AW2 was for its standalone GPS capabilities and onboard music. Otherwise I would have bought a Garmin. I think Strava got tired of ppl bugging them about the release and they pushed it on the users prematurely. I'm not even sure Strava has a real beta-testing program. If not, they need to get with it.

    No harm, no foul. My comments were not meant to inflame the situation as I agree with everyone's valid complaints. If I were affected the same way I would be up in arms too. I have tested a number of other apps and if you are using your phone to tether to your Watch, there are more capable apps a available. Runkeeper seems to be leading the pack on the Watch only app, but they have there bugs too. Some of which are keeping me back and forth b/t Strava and RK. I'm trying to decide which one has issues I can live with. I hope Strava does something soon.

    0
    Ações de comentário Permalink
  • I love the new native app, but why doesn't the display show hundredths of a mile?  Every other running app does this.

    0
    Ações de comentário Permalink
  • Thank you for enabling Strava to work w the native Apple GPS! Not having to run w my phone is awesome. Well done Strava and Thank you!

    -2
    Ações de comentário Permalink
  • @Andy N - you have summarised the issues so well. Initially I thought I was going nuts and spent most my run on the weekend checking my watch and my phone to try to get the audio cues to work. Why would Strava take that feature away? I agree also @Brent Rich - can we turn the clock back for us AW1 users and provide us with the old app again. And now!!

    1
    Ações de comentário Permalink
  • I coming at this from the other side - I didn't realise that the AW native GPS had been made available to cyclists (on the 21st Feb 'bug fixes' update) and tried it for the first time today. Like many others, I'm sure, I've been waiting for quite some time now for this functionality so was both surprised and pleased that it now is - albeit, in what one must assume, is not the final version.


    For me on the Series 2, it worked very well. The HR dropped out for a short time during my morning ride to work, but was fine on the way home. I can't verify the accuracy of the data as I had nothing to compare it with, but the GPS data compares well to my Garmin unit. Having the HR data available in the Strava app is particularly useful when combined with the Premium content. 


    What still needs fixing? It's been said before, but to ensure the app chooses the watch's GPS, I have to turn my phone's bluetooth off before the ride, then turn it on again before I save, so it automatically uploads it to Strava. This is an inconvenience in the short term but would become very tiresome in the long-run.

    There's currently no complication for the AW which is an inconvenience, but should be a standard for apps/companies of this calibre. 

    I'd love some heart zone feedback from the AW during the ride. Other similar apps offer it and so should Strava's.

    The native activity app on the AW ain't great, but it does do some things really well - like the countdown from 3 to go before a ride. The Strava app could do something similar I'm sure.

    Finally, I have to agree with others on this post - if Strava update their App, they should be upfront about the changes that have been made, to allow users to make the choice. Beta testers know they are beta testers because they have access to a unique version of the app that regular users don't have. I think I understand why Strava did what they did - the release of the Series 2 compatible app is kind of dragging - but it was probably a bit naive to do it under the radar.

    0
    Ações de comentário Permalink
  • 1. For cycling. I'd like the AW2 to still have the ability to function as a second screen. Reason being that my iPhone's weight and bulk is insignificant on a ride and has better recording equipment (barometer, altimeter, etc.) so I won't be switching.. but would still like to glance at the watch (as was previously possible).

    2. For running. I will be switching. Audio cues are really important to me, so I can get an update at every split (of my choosing) and know whether to up the pace, keep it steady or chill. These cues should be customisable so I can request as much or as little info as I want. For me: previous split, overall average pace and distance ran (or remaining if after 50% of set target distance). Section info would be great, too, since this is what differentiates Strava. Entering/finishing a segment + any post-info (beaten PR, KOM, etc.) - why not? :) Last but not least they should be aware of music playing and fade in/out appropriately. Most apps do this but one (I can't remember - maybe Waze?) doesn't, and it's really annoying.

    3. For swimming. Just that.

    0
    Ações de comentário Permalink
  • I love the Strava app but now my Apple Watch 1 is useless with the new Apple Watch update. Before my Apple Watch 1 just acted as a remote for my iPhone, but now the new Apple Watch app does not use the iPhone app. The battery in my Apple Watch 1 is not strong enough to last on my 3 hour rides, so the Apple Watch Strava app dies in the middle of my rides and does not record my full ride.

    Can you please make a setting for Apple Watch 1 that just makes it work like before, so that I can record my ride from iPhone but I can view the information on my Apple Watch 1.

    As a side note, the only thing I use my Apple Watch for is Strava.

    Thanks so much,

     

    Ray Kreisel

    2
    Ações de comentário Permalink
  • Can you look at adding an potion to set up intervals runs? my previous Nike GPS sports watch had this feature but there is no option to have this on the Nike Running Club app on the apple watch series 2. It was a huge part of my training and very very useful. If you added this function it would be a HUGE bonus and one up on Nike.

    0
    Ações de comentário Permalink
  • Hi Elle,

    thanks a lot, I am really happy, well done! One question though: I have quite a difference in the run length compared to the training app - more than 10%. Any idea what the reason could be?

    Looking forward to the new functionalities you announced, spot on, they are missing and will create an even better running experience!

    Cheers, René

    -1
    Ações de comentário Permalink
  • Had a strange one this morning - the AW2 seemed to get confused when it was separated from the iPhone - my wife handed me her jacket (with iPhone in the pocket) as she ran past. We thought this wouldn't be a problem due to the iPhone and AW2 not being linked anymore. This stopped logging for about 4 minutes, cutting a big corner off the run.

    Strangely enough the distance was more accurate than the same time that route was used 4,900m instead of 5,000m with 500m missing from the log. Last time she ran that course with the new software it logged as 4,500m despite to trace showing the full route.

    https://www.strava.com/activities/886877363

    0
    Ações de comentário Permalink
  • Ok so last weeks comparison of garmin watch with strava app on AW2 which showed how bad the gps is on strava app. 6.10 miles recorded for a 5.3 mile run!

    This week I compared the garmin Watch to the Runkeeper app on AW2. Garmin- 3.10 miles. Runkeeper- 3.08 miles. The HR data was also very very similar.

    My conclusion is simple. The Apple Watch is excellent at tracking runs and HR accurately but NOT WHEN USING THE UPDATED STRAVA STANDALONE APP.

    Strava this is very disappointing. Get it sorted soon or I won't continue to pay premium and I'll stick with using Runkeeper.

    0
    Ações de comentário Permalink
  • There are two absolute priorities for the next update.

    1. The delay in starting recording with GPS. I can understand that it takes a bit of time to get GPS signal, but it must be simple for the watch app to try getting a signal as soon as you open it and to alert you when it is ready

    2. Uploads to the phone. My last 3 rounds have had issues uploading. 1 has not uploaded at all because of the Strava server issue, the next two have not updated straight away. It has taken 2 days for one to appear on my feed and I am still waiting for the next. Totally unacceptable and not exactly complicated.

    I can understand things like becon not being available because they require cellular connection.

    -1
    Ações de comentário Permalink

Por favor, entrar para comentar.

Não encontrou o que estava à procura?

Nova publicação