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.

Labels:

Comments

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!
Post a Comment
Read more

Code versus Configuration

At Ethos we are building a distributed mortgage origination system and in mortgage there is a lot of different user types with processes that vary depending on geography.  One of our ongoing discussions is about how much of the logic resides in code vs. being in a workflow system or configuration.  After researching this topic for a bit, I have arrived at a conclusion that the logic should live outside of code very infrequently, which might come as a surprise to a lot of enterprise software engineers. Costs of configuration files and workflow engines First thing that I assume is true is that having any logic outside of the code has costs associated with it.  Debugging highly configurable system involves not only getting the appropriate branch from source control, you also need to make sure that the right configuration values or the database.  In most cases this is harder for programmers to deal with.  In many FinTech companies where the production data is not made readily acce
Post a Comment
Read more

Intuitive Programming - Comments

Comments are a topic of vibrant discussion.  Ever since programmers could leave some text in the program that was ignored by the machine the debate started: “what’s a good comment, what’s a bad comment, why comment?” There are endless instructions to programmers that say many of the following things: 1) Describe your function! 2) Don’t write in the comment what you wrote in the code. 3) Tell people why you are doing what you are doing. What I think has been missing from this discourse is the audience for comments and through those audiences there is intent.  The code is being read, skimmed or analyzed by people and tools.  So what are the audiences and reading modes? 1) Maintaining and enhancing the code 2) Skimming through the entire module or file to figure out what the overall structure is 3) Reviewing the test files to check out the test coverage and edge cases 4) Seeing the docstrings of functions while being in a separate file altogether 5) Reviewi
Post a Comment
Read more