Skip to main content

Health Tracker Stats Fun - Jawbone Up24 vs. Nike FuelBand

UP24 vs Nike FuelBand
UP24 vs Nike FuelBand
After being a Nike FuelBand user for several years I’ve got myself an Up24 and decided to compare the data I am getting with both of the devices.  While some of the data, like calorie burn, is subject to interpretation, the other data, such as steps, should have been more or less mechanically calculated.  Surprisingly the data between the two devices had as much as 70% difference with Up24 usually counting more steps and Nike FuelBand generally recording more burnt calories.

Here are a few data points I’ve got over the past week with both devices worn on the same wrist close to 24hours a day:


Nike Steps
Nike Calories
Up24 Steps
Up24 Calories
19-Dec
13,986
1096
16990
946
21-Dec
8,170
1003
11317
586
23-Dec
6,685
673
5553
272
25-Dec
1,929
319
2491
146
26-Dec
5,684
940
9675
540
27-Dec
2,334
271
3341
184


Here is the difference between the two sensors:


Step Difference
Calorie Difference
%Diff
%Cal
19-Dec
3,004
-150
121%
86%
21-Dec
3,147
-417
139%
58%
23-Dec
-1,132
-401
83%
40%
25-Dec
562
-173
129%
46%
26-Dec
3,991
-400
170%
57%
27-Dec
1,007
-87
143%
68%

As you can see there is still no consensus on what constitutes a step and how you calculate calorie expenditure.

Up24 is a newer device and also includes a sleep tracker to maybe has more advanced math, but there is no way for me to claim which one is more accurate.  Both devices accomplished one thing well – giving me instant feedback on when I am active and making me feel good about moving around during the day.

Post a Comment

Popular posts from this blog

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!


SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!

Why you should take the software job in San Francisco (or not).

Silicon Valley is an iconic place for technology.  Many people say this is the place for the “best and the brightest.”. Apple, Google, Facebook, Salesforce, Twitter and other top companies draw a lot of talent form all over the world and the largest chunk of VC capital goes to companies in the Bay Area, so it seems like moving here is a no brainer!

The real situation is actually not that simple, I believe there are three scenarios where it makes sense, but in many cases living in the Bay yields disappointing results.  The cost of living, housing situation, homeless catastrophe make places like San Francisco a lot less appealing to a lot of people.  So in what situations does it make sense to move to SF?

Startup founder raising millions There are many places to be a startup founder, but if you are looking to raise capital the largest pool of VC money is in the Bay Area.  There is an established network, events and conferences which give founders an opportunity to pitch more people th…

Pull Requests and Code Reviews

Software development involves a great deal of collaboration.  One of the most basic blocks of collaboration on a software development team is a code review.  There have been many different ways of doing code reviews over time, some of this has been dictated by the tools available.  Git and online source collaboration tools created a set of best practices that are worthwhile of adopting on any team.

About a month ago I have looked at various articles about how to best create a Pull Request (PR) and do a code review and the attached presentation is the result of this research.  The presentation can help you guide your team and develop a set of collaboration practices that works for your particular situation.

It’s good to start out with why to seek a code review.  Having clarity about your intentions helps you guide the person helping you with code reviews and also to manage your expectations about you can get out of the code review.  The reasons for seeking a code review are generally …