Finally some wintery weather has descended in the Philly suburbs.
A light dusting of snow arrived Friday night and then the temperatures plummeted into the low teens Fahrenheit.
This led to some great playtime with the kids on Saturday and to a very cold run on Sunday morning.
The actual temp listed was 13F but the real feel was 3F; so getting the right kit was imperative.
Under armour underoos (an extra layer for butt)
Sugoi winter leggings
Under armour cold weather long sleeve shirt (x2)
Cycling wind breaker layer (has long back pockets that also cover your butt). Make sure this is a visibility colour against snow; do not wear white or grey.
10 miles later, all that froze was my butt. My face and hands were toasty. I wore my iPhone holder inside my outer layer to stop the phone from freezing up.
I wasn’t fast but then no one would be with all those layers on. 9:07 average pace reported by Nike+.
I’m writing this sitting on a heat pad to defrost my extremities 🙂
Tech-wise I ran with my Lumo Run device today and I got ‘in the green’ results for four of the five measured categories, with the only exception being my hip rotation.
I used Nike+ on my Apple Watch for tracking and started it from my watch. This meant that to hear the announcement for distance and speed I had to hold the watch up to my head as the sound wasn’t routed through my headphones that were connected to my iPhone. Nike really need to get their integration worked out.
Now to get showered before my sweat causes me to get a chill.
Two more runs on the books since we last spoke; Monday was a quick run with my friend Ed and today was a 45 minute run as prescribed by the Nike+ marathon training programme I’m testing out.
Which brings me to Nike+ Run Club: what is going on with this? It’s behaviour is very inconsistent.
I’ve used it four times now and get different behaviours most times:
First run Sunday: started from watch. Recorded heart rate but no elevation.
Second run Sunday: started from watch. Recorded heart rate but no elevation. Same so far.
Monday run: started from watch. No heart rate or elevation.
Wednesday run: started from phone. No heart rate but elevation recorded.
Also, it seems that there is no integration between the phone app and the watch app. If you start the run on your phone the data doesn’t show up on your watch as you run. I assume this is why it isn’t recording heart rate, too.
It’s all a bit odd to me and clearly there are som edges that need to be rounded off.
The app itself on both the watch and phone are very slick looking but have some internal integration issues too. If you start a run as part of the programme and compete it correctly, it still doesn’t mark the run as being done in the programme. You have to go into each run and assign them to the various programme activity. Weird.
I’m trying to be good and did a few stretches after the run. My son decided he would be my coach; very helpful, I’m sure.