Showing posts with label fitness wearables. Show all posts
Showing posts with label fitness wearables. Show all posts

Sunday, August 24, 2014

I wish my insurer would offer this incentive

Bloomberg News discusses an oil company's offer to reduce an employee's health insurance co-pay by $100/month if he would wear a FitBit tracking device to track his steps toward 1 million in a year.

(Shhh, don't tell the employer that wearable fitness trackers sometimes lead users to gain weight.)

I don't think I'd mind wearing something like that to track steps in exchange for an annual $1200 savings on health insurance premiums. Of course, I would keep the device active when I go running, instead of (usually) turning off the pedometer app on my Galaxy S5 when I run.

Hey, how about giving graduated breaks on health insurance based on how good of an age/gender-graded 5K time you can achieve in a certified race? (I have heard of employers who offer to pay 5K/10K entry fees for employees . . . I wouldn't complain about that.)

Thursday, July 31, 2014

10,000 steps a day is hard!


The S Health app on my new Galaxy S5 includes a pedometer, and as seems to be typical for pedometers, it sets a default "goal" of 10,000 steps per day. Apparently, the 10,000 steps idea originated as a marketing pitch in Japan, though it does seem to correlate (not surprisingly) with some good health markers.

I've been using the pedometer for close to a week now, and it isn't easy racking up 10,000 steps if you don't count running.

Saturday (7/26), 7269 steps: Walked to lunch; went to an indoor sporting event and walked around the stadium at half time.

Sunday (7/27), 11942 steps: Ran 3.3 miles outdoors, which accounted for about 5000 of the steps. Without running, this would've been just under 7000 steps.

Monday (7/28): 29738 steps: This included a 13.7 mile run. Without that, it would've been another day around 7000 steps.

Tuesday (7/29), 4565 steps: Running was done on a treadmill without my phone, so this is the pure number of walking steps.

Wednesday (7/30), 9660 steps: Again, running was done on a treadmill without my phone. No particularly extensive walking trips other than taking the kids to summer daycare (about 0.6 miles round-trip), just a lot of chores around the house.

Thursday (7/31, as of early afternoon), just under 4000 steps: About 1000 of those "steps" came when I was on the exercise bike before I realized that the cycling motion was fooling the accelerometer on the phone.

I do live on the West Coast, and in a sprawling suburb at that, so I do less walking as a means of ordinary transportation than if I lived in one of the dense cities with little parking. It's certainly feasible for someone who relies on walking to get from place A to place B to rack up 10,000 or more steps a day easily. But if you have a white collar semi-sedentary lifestyle, it may be near impossible without incorporating running into your routine.

(One thing I am curious about is how much pacing will add to the step count. When I am teaching, I tend to pace back and forth at the front of the classroom. Classes start after Labor Day, so I will have to wait until then to find out.)

Oh, and while it has been interesting to see my number of steps taken, I haven't bothered logging the calories burned count. The effect on calorie burn of walking is pretty negligible, and anyway, I figure this is all part of NEAT.

Monday, July 28, 2014

More on the Samsung Galaxy S5

I reviewed the Samsung Galaxy S5 from a runner's perspective here. It was more like "first impressions," as I hadn't had a chance to go on a long run with it, just a short 3.3 mile jaunt.

Today I ran 13.7 miles with it, using RunKeeper and Audible while also running the S Health app as a pedometer in the background. Battery drain was quite acceptable, about a loss of 15% over 2 1/4 hours. Obviously that wouldn't last the entire day at that rate, but then again, I wouldn't be having the constant GPS hit for the rest of the day.

One slight downside is that the S5 is slightly larger than my old Galaxy Nexus, and somewhere around mile 11, my left shoulder started to get tired. I switched the phone to my right hand, and not long after, my right shoulder got tired. (I normally hold my phone in my left hand, so even though I'm right-handed, I guess I have more muscle endurance on my left side for this particular context.) It's not a heavier phone, but it's wide enough that it seems to be stretching my grip to its comfortable limit.

The other funny thing is that the S Health pedometer has absolutely no idea what to do with my high cadence/short stride when running. It knows when I'm running versus when I'm walking and helpfully displays the "steps taken" bar chart in different shades of green, but its mileage calculator was way off. By the end of my run, it proudly informed me that I had covered over 20 miles on foot today. Subtracting the 13.7 miles from the run, that would mean that I'd already walked well over 6 miles too. I think the accurate figure would have been about 3/4 of a mile at that point. So the pedometer roughly overstates my on foot mileage by about 50% when I'm running.

Sunday, July 27, 2014

The Samsung Galaxy S5


I've been using a Samsung Galaxy Nexus for the past two years, and I've liked it a lot. However, the first one I had became extremely unstable not quite a year into the contract, and I ended up getting a refurbished replacement. That one worked well until my July 4th 5K race, when the GPS decided to take a vacation, leaving me to run essentially without any timing guidance.

A few weeks ago, I lingered a bit too long in Target's mobile phone section, and when the sales manager approached me, I was unusually receptive to learning about the available phones. I was intrigued by the Galaxy S4, which had dropped to $50, and not so much by the Galaxy S5, which was going for $170. The S5 had two new features, a heartrate monitor and a waterproof case. I didn't see much use for the HR monitor, but the waterproofing was somewhat attractive, living as I do in a rainy climate. Still, I didn't think it was worth $120 more.


Friday, July 25, 2014

RW's gag running inventions


Runner's World has a slide show with a bunch of gag running inventions, but I wonder if performance-obsessed runners like me would actually go for this "PaceProd" watch, which "delivers an electrical shock if you start to slow too much. No more looking at your watch or listening for beeps, just a helpful 2 milliamps of current to keep you on track."

Even better is the PaceProdPlus, "which delivers twice the electricity if you try to remove it before you’ve reached your target distance for the day."

You have to wonder how long the battery lasts, though.

Tuesday, May 20, 2014

Kickstarter project: the Slick Bib - maybe it's a solution in search of a problem, but I'm backing it

The Slick Bib is a Kickstarter project that I just decided to back, even if it's possibly a solution in search of a problem. Here's a picture of it:



It's a tech shirt with a transparent pocket for holding racing bibs, thus avoiding the need to poke safety pins through whatever other racing shirt you'd wear. One downside is that you won't be wearing the shirt provided by the race organizers (if there is a race shirt) - but that's not really an issue for me because I don't like to wear race shirts at the race itself. It's not exactly a superstition, just more of a tradition.

Now, not having to mess with safety pins on cold mornings is a definite plus - and those late November to early March races can get chilly in the Pacific Northwest. Of course, this is a short sleeve tech shirt, but it can just over a baselayer longsleeve.

Anyway, this may be something of a luxury purchase (assuming it gets sufficient backing; it's only 1/3 of the way there) but it's also a pretty neat idea.

Thursday, April 24, 2014

Smartphones versus fitness wearables?

I have a running watch that's waterproof and can track up to 40 different intervals, but it doesn't have GPS. I've periodically thought about getting a Garmin, but inevitably, I ask myself, why? If I run on a treadmill, I know exactly how far and how long I went, and if I run on a track, I don't need GPS. On all other road runs, I carry my smartphone and use RunKeeper.

So I guess it's not surprising at all to read about the impending demise of Nike's Fuelband and the troubles ahead for other fitness wearables. I mean, I'm not exactly in the vanguard of tech gadget adoption, but I am one of those semi-obsessed runners who has about as much running clothing as non-running clothing. To the extent I'm somewhat representative of a swath of fairly dedicated runners, the fact that I'm not rushing to get any of these devices is not a good sign.

To be sure, I'm not saying that the smartphone/RunKeeper combination is a perfect substitute for a GPS watch or a fitness tracker. I have RunKeeper set up to give the most frequent audio cues about time/distance/average pace, which is every 1/4 mile and every 5 minutes. In a 5K race, that means I get 12 updates from the mileage and (at my pace) four more from the time. That's not bad, but if I want to check my average pace at some other point, I'd have to get pass my screen lock, which isn't trivial when you're running at near maxVO2. I could see how a watch or fitness tracker would offer some incremental advantage there.

But enough to be worth buying one . . . when that money could be used toward more race entry fees, or tech shirts, or shoes?