Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
[Free] YouRace: the new Apple Watch app for runners!
- Thread starter rbart
- Start date
- Sort by reaction score
I recently mentioned GPS signal strength before I start run and it's great! Now I can wait until I have good signal and then start run 👍.
I also start running with my iPhone and searching for shortcut that play apple music playlist for me from phone after I open YouRace on Watch or I start running
.
I also start running with my iPhone and searching for shortcut that play apple music playlist for me from phone after I open YouRace on Watch or I start running
.Sounds great with the new features 👍
An idea could also be to have 2 run “profiles”, one with auto lap enabled, and one where it’s disabled.
And another idea is to be able to make customizable “auto lap”, let’s say with a 5k interval, so I know when to take my gel on a marathon.
I've scanned this thread but may have missed it – is there any way to display a heart rate lock (as Garmin does) similar to how you have the GPS strength before starting the run? I often find that the AW doesn't have a lock on my heart rate right away, and I would prefer to delay starting until it does.
It's probably possible, but in some cases, you have to wait for a very long time.
The way Apple measures heart rate is mysterious, sometimes, for some reason, you get no data ...
There is another glitch, the sensors behavior is not the same in "idle" mode and in "workout" mode.
But, I can only put the workout mode when you start the workout.
I have to investigate, but with Apple APIs, we are not completely free ...
The way Apple measures heart rate is mysterious, sometimes, for some reason, you get no data ...
There is another glitch, the sensors behavior is not the same in "idle" mode and in "workout" mode.
But, I can only put the workout mode when you start the workout.
I have to investigate, but with Apple APIs, we are not completely free ...
Thanks for the response.
I guess the best workaround for me for now is to use my external HR strap. I can confirm it's paired in the bluetooth settings prior to starting my run, and it seems to lock more quickly (and is more accurate, especially during intervals) than the built-in sensor.
Hi, I recently started using Yourace (+IAP for export)... worked well for a recent 26.2 mile event - whereas my old Polar watch failed / crashed somewhere around 18 miles :-(
Would it possible to add bluetooth footpod support, I find the Apple Watch current pace rather slow to react (and rather random sometimes) based on it's pedometer/GPS.
Would also be great to have a 3rd screen, so we can have intervals and race screens. My last event was ~5 mile laps, so I triggered a new interval each lap, but would also have liked to see the race page with estimated finish time.
Thanks.
Would it possible to add bluetooth footpod support, I find the Apple Watch current pace rather slow to react (and rather random sometimes) based on it's pedometer/GPS.
Would also be great to have a 3rd screen, so we can have intervals and race screens. My last event was ~5 mile laps, so I triggered a new interval each lap, but would also have liked to see the race page with estimated finish time.
Thanks.
Thanks for using YouRace !
I have no plans to bring footpad support for the moment, for different reasons:
- it's not very common for AW users
- I don't have one
- I am the only developer and I need to have priorities ... I have a lot of things in pipeline and not enough time
I think you can achieve what you need without needing a 3rd screen.
You can use auto lap to have one lap per mile and display the current mile speed or time in the race screen (or another screen). Check the available data fields, I am pretty sure you can have your perfect setup with 2 screens
For the moment, I have no plan to have a 3rd screen, it's not hard to develop but I don't want a too complex app.
If many people request that I will think again about that 3rd screen ...
I have no plans to bring footpad support for the moment, for different reasons:
- it's not very common for AW users
- I don't have one
- I am the only developer and I need to have priorities ... I have a lot of things in pipeline and not enough time
I think you can achieve what you need without needing a 3rd screen.
You can use auto lap to have one lap per mile and display the current mile speed or time in the race screen (or another screen). Check the available data fields, I am pretty sure you can have your perfect setup with 2 screens
For the moment, I have no plan to have a 3rd screen, it's not hard to develop but I don't want a too complex app.
If many people request that I will think again about that 3rd screen ...
this race was laps of around 5 miles each (not exact) and the lead in to the first lap made that one a little longer, requiring the ability to manually trigger the laps to compare average pace over each, but the total was marathon distance, so would have been nice to have a screen with an estimated finish time over the 26.2 miles - the option to set the number of screens would be ideal.
OK, I understand ...
I have one concern ...
The app has basically 2 modes:
- interval mode : to mark segments with buttons (or double tap)
- race mode : to mark real km with buttons (or double tap) for distance fix
So it's a different logic to implement to mix intervals and race modes.
I have no easy solution for such use case at the moment. I have to investigate.
I have to enhance things, some users are lost with my screen/mode management, and you question is another issue that shows it's not clear and/or flexible enough.
There is room for improvement, but I am always constrained by the only physical interaction allowed by apple : the 2 buttons pressed ...
I have one concern ...
The app has basically 2 modes:
- interval mode : to mark segments with buttons (or double tap)
- race mode : to mark real km with buttons (or double tap) for distance fix
So it's a different logic to implement to mix intervals and race modes.
I have no easy solution for such use case at the moment. I have to investigate.
I have to enhance things, some users are lost with my screen/mode management, and you question is another issue that shows it's not clear and/or flexible enough.
There is room for improvement, but I am always constrained by the only physical interaction allowed by apple : the 2 buttons pressed ...
I was interested in the distance fix concept, but couldn't find a detailed description - is the idea to double tap every km / mile to calibrate ? Does it need to be the first km / mile from the start, or can you tap for every km / mile you pass ?
I suppose a double tap on the intervals page starts an interval, and double tap on the race page to calibrate distance, and the option to show/hide each additional mode page.
Additional - I liked the double tap, versus using the two hardware buttons simultaneously (I always seemed to hit one before the other and move away from the app) - and certainly better than ismoothrun where you have to swipe across and hit the correct icon whilst running... ;-)
I suppose a double tap on the intervals page starts an interval, and double tap on the race page to calibrate distance, and the option to show/hide each additional mode page.
Additional - I liked the double tap, versus using the two hardware buttons simultaneously (I always seemed to hit one before the other and move away from the app) - and certainly better than ismoothrun where you have to swipe across and hit the correct icon whilst running... ;-)
Last edited:
For calibration fix, you have to tap when you meet an "official" km/mile. You can tap when you want, it will probably be more accurate after few km.
It's recalibrated very time you tap.
If I link the action to a specific page, it's problematic as you have to look at the screen when you double tap or push the buttons. It's more intrusive.
UX is a complex problem on a watch with few buttons.
It's recalibrated very time you tap.
If I link the action to a specific page, it's problematic as you have to look at the screen when you double tap or push the buttons. It's more intrusive.
UX is a complex problem on a watch with few buttons.
I ran half maraton last saturday and I forgot about this race function. At first half I was slightly ahead, but at the finish I was almost precise - https://www.strava.com/activities/7026667381/overview
I was rather wondering what purpose the 'calibration' served - unless you run an even pace & stride on a running track and only use the pedometer ? So perhaps it's not a necessary option in the app ... what use cases did you have for needing to include it ?
In my last event the laps were around 5 miles each (exact distance not known) with a lead in to the first lap to make up the marathon distance - so not really anything to calibrate from - hence I used the interval/lap double tap to compare pace on each lap - but knowing the total was 26.2 it would have been nice to see an estimated finish time too.
I have added this distance calibration because I have ran a lot of races where my watch over (or under) estimate the distance and it was difficult to have an accurate distance estimation for a specific target.
I find it useful and it was one of my first "exclusive" feature.
Maybe newer apple watches are more accurate, but I have started the development with my old series 2 and the error margin was quite high.
I know many users love this feature to be sure to reach their target (when running an half or marathon for example). You know your target pace and you just have to check if you are slower or faster.
I find it useful and it was one of my first "exclusive" feature.
Maybe newer apple watches are more accurate, but I have started the development with my old series 2 and the error margin was quite high.
I know many users love this feature to be sure to reach their target (when running an half or marathon for example). You know your target pace and you just have to check if you are slower or faster.
I understand... I think the newer watches/phones are more accurate - but I always find it hit & miss as to whether my tracking devices (whatever brand) matches the certified event distance at the finish. I normally expect to come up short, due to GPS smoothing, but last time showed 26.32 on a 26.2 course - which is preferable ;-)
I assume your calibration influences the displayed pace, but cannot influence the recorded track, nor overall timing, so Strava etc will still calculate the split / final pace from the track data / timing ?
Distance calibration is the best feature and I wouldn’t run a race without it. It’s nearly impossible to run the tangents on a course perfectly, so pretty much every race you run will be “long.“
Have you considered adding a field that calculates the projected finish time for the race, rather than just elapsed time? One of the Garmin apps I use has that and I find it useful.
If you use the "race mode" and set a target distance, you get the ETA instead of the elapsed time.
The "fix" feature is only for display during the race. It's not used when storing/exporting the workout.
Thanks for all your replies... another quick one: in race mode - does the workout automatically end once the chosen distance is reached, or does it continue to record until you manually end ?
After a while without any change, an new version is coming (waiting for Apple approval):
For every one:
For every one:
- Settings user interface improved
- Adjust distance target with 0.1mi step for imperial metrics
- Stability improvements
- possibility to completely disable kilometer or mile notifications
- setting for auto ending a workout at target distance