Showing posts with label RunKeeper. Show all posts
Showing posts with label RunKeeper. Show all posts

Tuesday, May 21, 2013

Pebble and RunKeeper Review

Check out the end for an update from my 2nd Pebble/RunKeeper Run...

I think part of the reason why I was able to get into running was because I was able to download a C25K program on my iPhone.  Almost every single run I've been on, I've had my trusty iPhone with me.  Yes, part of it is for personal safety, part of it is for having music and part of it is so I can collect as much data from my run as possible.  When I ordered the Pebble on Kickstarter, I was thrilled since they were already talking about RunKeeper working with the Pebble.  Last December, I switched to using RunKeeper, and found it's a slick app for tracking your runs, shoes (love this function!) and makes it easier to review all of your stats (the engineer in me loves that!).  The app and the website are both very stable (which I can't say for some other free running apps I've used in the past...)


Since I wanted the red Pebble, I had to wait until this month to get my watch.  The red was totally worth the wait!  The color has a depth due to the clear coat over the whole watch face, which really makes it looks a bit slicker than the black Pebble my husband has.  The black Pebble has that serious air to it, while red is a bit more fun and flashy.  We both got the right color! :)

I will say, I was little worried about the size of the Pebble's face.  I knew it was going to be on the large size, to accommodate the required screen real estate.  But I have "girly wrists", so I was worried it was going to look or feel cumbersome.  I have to say, they got the screen size perfect, it's big enough for long winded texts, but small enough that it doesn't stick out past my wrist.

It is surprisingly awkward to take a photo of your own wrist!

Sunday, April 28, 2013

Hills, times and perceptions

I ran two 5K's just two weeks apart and my times were 32:46 and 33:44.  I figured it made sense, they're both at the faster end of what I've been running lately, and the second race was hillier (Boston vs the "Worcester Foothills".  So, I did what any good engineer would do and pop on over to RunKeeper to see what the difference in Feet Climbed was.  I was a bit surprised.

First race: BAA 5K.  It runs along Comm Ave, and the "biggest" hill is going under Mass Ave. for an almost 30 ft hill.  And yet, the feet climbed totaled 280 ft.  Here's my RunKeeper File.

Then, two weeks later, I ran the AMSA Inaugural 5K. I swear to you, this race felt like it was uphill, both ways.  In actuality, there was a short up hill, a long downhill, then rolling hills then reverse of the first two hills.  That was a 120 ft climb in about 1/3 of a mile, including one stretch that I need to put my Prius into "super break" mode to not roll backwards down the hill.  But, the overall climb was only 228 ft! That would be LESS hilly than the BAA 5K. Here, check out RunKeeper.

A minutes slower, but 60 feet less of hills? Different day, so it's within my normal error of pace?  Technical glitch? (I've seen most running app's get confused about elevation near water. Every time I cross the Charles, my elevation goes to 0 ft, even though I'm not walking on water!).