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

Lessons from my 9 Year Journey with DocuSign

After over 9 years at DocuSign I am taking on a new challenge.  It’s been phenomenal seeing the
company grow from from 25 to 2000 employees.  DocuSign has changed the way the people do business and I am proud of it.  The next chapter is going to be heading up software development at Tempo Automation - a 25 person startup that is changing the way people produce electronics.  While I am extremely excited about the future, this is a good time to reflect on my journey and share the things that contributed to the success and things that I will do differently next time around.
1: Focus on the Customer One of the key things that contributed to the success of DocuSign and my personal career is relentless focus on the customer success.  From the very beginning our CTO has taken meetings, listened and prioritized requests and feedback coming from customers.  People who could not be bothered by customer requests didn’t last long.  As a result over time our engineering team retained and reward…

Highly Effective Software Teams

A few weeks ago our Board of Directors asked me to present my assessment of the state of software.
 I was hired to organize and grow the software team and the directors wanted to know what kind of a team we needed to build.  I was hoping that I can just reference an article somewhere that would give me the answer, unfortunately I didn’t find anything suitable. During my research I did find some great material that will be helpful if your job is to put together a highly effective software team.
A highly effective software team has the following key characteristics: dependable, committed to shared goals, passionate about technology, respectful and compassionate.  These are not limited to technology industry, it can easily apply to finance, medicine, or sports as well.  Below is the summary and references that I found. Dependable If you are creating a software product, you need to deliver your software to your users.  Your users need to know that you are able to solve their problems on …

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!