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!

Chief Collaboration Officer

When you search for the word “collaboration” on the Internet, the top hits are mostly software packages you can buy.  Software can facilitate collaboration, but it doesn’t make people collaborate on its own.

One of the key functions of a technical leader is to bring a team together, help people share ideas, and facilitate team members helping each other.  When a software leader overlooks this key function, you end up with a group of individual contributing engineers instead of a cohesive team.
Before we get into tactics, we should ask “Why is collaboration important for an engineering team?” 
It’s critical to examine your assumptions, so here are my reasons for why a group of engineers working on their own are worse than a team working together: Smart people learn from each other.Getting your plans and designs reviewed by other people allows you to leverage their experience and check your assumptions.Collaboration produces artifacts that stay after collaboration has taken place (such…

Hire Fast, Fire Fast? Not so Fast.

Silicon Valley is full of advice and it frequently comes from people who have little experience on the subject matter.  A popular topic surrounds hiring and terminations with the king catch phrase being: “Hire Fast, Fire Fast.”  To me, what that usually means is lack of diligence, thought, communication and courage.

When hiring people love going with their gut feel, often with disastrous results.  There is an obvious subject of diversity of thought, appearance and background.  When thinking “fast” you are probably hiring people like yourself because humans quickly react to people who they believe are in their tribe.

A startup that lacks the resources of a big company often becomes so desperate to get technical staff that when a decent candidate comes along, excitement ensues and the employer doesn't slow down to put them through a more rigorous hiring process.

I highly encourage technical founders and engineering executives to write out their precise hiring process.  Of course, y…