In this post
The Fitbit Surge, announced along with the Charge and Charge HRis the Silicon Valley company's first GPS watch. Typically related to activity monitors, it represents its first approach to more specific sports watches. Although not 1TP10We can not consider it as "a watch for running", since even Fitbit does not - in its advertising the slogan used is "super fitness watch" - the poder show rhythms and distances more accurately can make us think that it is. But perhaps what stands out most about Surge is its optical pulse sensor, which allows you to get heart rate data not only during activities and workouts, but also throughout your day-to-day life.
As always, I like you to know the origin of the test units. This review is to be thanked to Fitbit because, as in the case of Charge HRhave loaned a Surge for testing and analysis. And now I can already confirm that both units will be back with them as soon as I hit the "publish" button. As you can see, full transparency.
If you like the work I do, and thanks to this test you are encouraged to buy a Fitbit Surge, do it through the links I provideThis way you can help the site without it costing you a single penny. What's more, the offers I put up usually allow you to save good money, which is good for everyone!
And after all these details have been cleared up, let's get on with the analysis of the Fitbit Surge.
The presentation of the Fitbit Surge is very careful, with an impressive looking case. On the front you can find a photo of the watch as well as an indication of the three functions that Fitbit wants to give more presence to: GPS reception, pulse sensor and notification reception.
On the side of the case you can see how it refers to the type of product we are dealing with. It's not a watch intended for runners, it's a "super fitness watch". So that's the way we should treat it.
The box neither slides nor pulls out, it opens. As you can see the presentation is very neat and I'm sure the box is worth "a lot of money". And this is a decaffeinated version, since it is a press unit, it seems that the box is not complete. In this internal part the definitive products have a motivational text that does not have the unit received.
But let's stop admiring the packaging and let's get the contents out because in the end that's what matters, and the box will go in a drawer at best.
I have not yet been able to remove the watch from the case, which is still attached to another plastic holder, but this is what you will find inside the case. In addition to the Fitbit Surge you will find the charging cable with USB connection (only for charging, not for synchronization), a USB dongle and a small instruction manual.
After releasing the watch from its last support, I can now turn it on, and so start getting to know each other. The Surge strap is made of an elastomer material, a type of flexible plastic. Once on the wrist it is comfortable and light. The touch screen is black and white and has a size of 20.88×24.36mm, it also has automatic lighting.
You can find three buttons to control it. The left button will be used to enter the main menu (and if pressed twice, to activate Bluetooth music control) or to return to the previous menu, if you have entered any sub-menu. The lower right button will advance through the menus and the upper right button is limited to certain options such as ending the activity, working only when there is a prompt next to it.
On the back is the charging port and "the jewel in the crown", the optical pulse sensor, exactly the same as the one found on the bracelet. Fitbit Charge HRDespite the fact that the charging port has no protection, the watch is submersible up to 50m, although Fitbit recommends not to use it in the pool or shower. But I have the impression that the reason for the warning is more to avoid possible skin irritation problems that some users complained about in the Fitbit Force. That is, despite the recommendation, it will stand up perfectly to your shower or swimming with it, although in contact with water the screen will stop working properly.
This is the sensor that Surge uses, surrounded by two green LEDs that will flash insistently and throughout the day (although if you are bothered, you can deactivate it from the menu). And next to it, the connected charging cable.
Finally, the wireless Bluetooth adapter. It is a Bluetooth Smart adapter, but it is only used for synchronizing the watch with the computer, you will not be able to use it to connect to other devices (mouse, keyboard, phone, etc.). And since the vast majority of you will be synchronizing with your mobile phone, the best thing you can do is put it back in place with the instruction manual, because after reading this test you will not need it either.
We load the watch, put away everything that doesn't serve us, and go to training.
The activity monitor in the Fitbit Surge is exactly the same as the one in the rest of the Fitbit range, with the advantage of having a larger screen where data can be consulted more easily.
The activity and the calories consumed are calculated by taking three values: Steps walked, floors climbed and heart rate (which determines the intensity of the exercise). And these data are obtained by the accelerometer, the barometric altimeter and the optical pulse sensor respectively, all of them integrated in the watch itself. It is the algorithms used by Fitbit which, starting from all these data together with those introduced in the initial configuration (mainly weight and height), finally estimate the calories consumed and the distance travelled.
All this data appears directly on the Fitbit Surge screen without having to access any menu. And you can move between the different screens simply by sliding your finger over the display. The screens you can access are steps, heart rate, distance, calories and number of floors climbed.
The activity recorded during the day will be continuously synchronized with the phone, and you can access the application to check the updated data at any time, as well as from your computer on the Fitbit website (www.fitbit.comThis application is available for Android, iOS and Windows Phone.
This is where you will find all the data on your activity, both daily and from your training for running and other sports.
By clicking on each of the different lines that appear in that image, you can enter the complete graph of those metrics. By default, the development of the last week appears, but you can change the view to months or years, depending on how you want to see the data.
On the website you will find the same information, but represented somewhat differently.
By clicking on any of the sections you will access the complete information, for that day or for a specific period.
What you must take into account, not only in the case of the Fitbit Surge activity monitor, but in all activity monitors, is that the number of steps indicated is not an exact value. In the end, everything depends on the calibration of the accelerometer, and it is not always possible to distinguish a step from a hand gesture, or to interpret that you are walking despite not moving your arms, such as pushing a baby carriage.
This value should therefore be used as a reference, and if the daily goal you have set is 12,000 steps, you know that if it marks 12,500 you may have taken those steps or stayed at 11,950, but your activity has been high. And if on the other hand it is marking 4,000 steps, it is because this day you have been especially lazy and you still have time to go for a walk and meet your goal.
When validating the data provided, I can compare them with data collected by other activity monitors on different days, taking as an example the comparison between the Fitbit Surge on a doll and a Garmin Fenix 3 in the other.
You can see in the three comparisons that the number of steps differs from one to the other, however the distance data is similar, as well as the activity graphs. These are the values that you must analyze, beyond an exact figure, you must confirm that your activity has been elevated throughout the day.
When you've finished your day and you've been fully active and met your goal, don't take off your Fitbit Surge, because that's when it's time to monitor your sleep. The mode switch between activity and sleep monitoring is fully automatic and works at the server level. That is, all the data is synchronized and when the information is in Fitbit's computers, its algorithms are the ones that divide your activity to determine when you have stopped being "in this world" and you are snoring peacefully in your bed.
When you wake up the next day, you can check how you slept that night. And of course, thanks to the pulse sensor, you can also check your pulse during the night.
The most detailed is the quality of your sleep, as well as indicating the time you fell asleep and the time you woke up.
The automatic recording it makes is really good. The truth is that, compared to other manufacturers, Fitbit has one more variable to calculate, which is the pulse. When your body enters the state of deep sleep the pulse drops dramatically, which allows you to identify perfectly when you are really asleep, and not only from the movements of the wrist.
Although generally speaking I have found data that can be confirmed as true with other activity monitors, sometimes they have not interpreted well the fact of simply lying in bed watching TV or working with a computer. Fitbit solves it in a much easier way in the case of the Surge (and also in the case of Charge HR) precisely because of its pulse sensor.
Not only is it important to be precise when establishing what your effective sleep hours have been, but also the amount of data you can provide about how effective that rest time has been, a point where Fitbit stands out positively, both in the data you can find on the web panel and in the mobile application. And at least it helps me to know that I don't really get enough sleep.
The data you can find in the mobile application and on the web are essentially the same. But it is in the "app" where you will find the best podrás analysis and where you will find everything more organized.
24 hour heart rate monitoring
Just like the bracelet Fitbit Charge HRthe Fitbit Surge offers all-day heart rate tracking, thanks to its optical pulse sensor that uses "photoplethysmography". This is what this type of technology is called, easier to explain than to memorize the name. The pulse sensor is flanked by two green LEDs. These illuminate the skin, allowing the sensor to measure changes in light absorption. And they are green because red absorbs green.
Therefore, in each cardiac cycle (each pulse), blood will pass through veins and capillaries that as you know are red (now I wonder... will this technology work with the aristocracy?) and what the sensor measures is the variation between reflected and absorbed light. That way it is able to give you the pulse data.
Well, after this kind of anatomy we can now talk about the Fitbit Surge and its constant heart rate monitoring. On the clock you can see your current pulse at all times. It's as simple as scrolling through the screens left or right to the one that corresponds to your pulse.
This data is stored and synchronised with the application on your phone (or when synchronising with your computer, if you don't have the app installed on your phone), and you can access it for later analysis.
In the list of days, 1TP10You can access each of them to enter more detailed information for that particular day, being able to identify patterns and times of the day of increased activity (or inactivity). You will also have your resting heart rate information, as well as the heart rate zones your body has "visited" and for how long.
The resting heart rate is not the lowest rate. You can see in the picture above how my resting rate for that day has been 50 beats per minute, but while I have been sleeping it was much lower, around 40 beats. So the resting pulse is not the lowest pulse your heart can reach, but the average resulting from the data taken while you are not active, i.e. sitting, sleeping or just not moving.
What about accuracy? On all trial days of both Fitbit Surge and Fitbit Charge HR I haven't seen anything strange in the graphs. There are no sudden spikes that can't be caused by intense activity, and at the time of some activity the pulses go accordingly.
Running with Fitbit Surge (using GPS)
The essence of Fitbit Charge HR and Fitbit Surge are the same. They're both good activity monitors, plus they offer constant monitoring of your heart rate. But when we go for a run, that's where the second one comes in.
Starting the activity simply requires using the left button on the clock to access the main menu. Here, we can select the race option.
You can make your selection by clicking on the confirmation button (the bottom right button, where it is marked on the screen) or by pressing on the center of the screen. Then you will have two options for running using the GPS. The first one is Free Run.
But we also have another way, interval running
I will start with the first one, as it will be the most common use for the vast majority. After selecting the type of race we are going to make, the search for satellites begins.
After finding satellites, the main screen is presented. There are no data screens as such, but a screen with two fixed fields (the upper and the central one) that indicate total distance and travel time. The lower field is the one that allows you to rotate between the different information options offered, which are the following
- Average pace
- Heart rate
So there are eight fields available in total (the 2 fixed ones plus the 6 you will rotate through). You can access these metrics by simply moving your finger or tapping on the screen.
This is the basic training function, but if you go back a few lines you will remember that I have talked about interval racing. The basic operation is the same, but in this mode the upper right button is enabled so you can mark laps manually (instead of laps per kilometer).
In this mode what you see on the screen will change a little. Distance and elapsed time will no longer appear on the screen as in free run mode, but will be replaced by lap number and lap time respectively.
The last line is still available to show different metrics, which this time will be the following:
- Back rhythm
- Distance returned
- Heart rate
- Elapsed time
As you can see, the interval race is configured for those days when you have to do series. However, it is not possible to schedule training sessions of any kind that will mark different phases or go through them in succession.
In the case of the interval race, when you mark a lap you will be shown a screen with the specific data for that lap.
This information is not displayed when you complete a kilometer in free run mode, as is usual with watches of any other brand, but then that kilometer separation will appear in the application when all the data is synchronized.
You can pause the activity at any time by pressing the same button you started with (the lower left button). And you have two options, to resume the training by pressing the same button, or to end it with the upper right button.
When you finish the activity you will have the summary of your training with the main data of your training. If you have done an interval training, first you can check the times in each of the laps you have marked.
After this screen (and in case the training is free running, it goes directly without the lap details), the data displayed are the typical ones like time, distance or average pace.
In addition to these, there are others that we do not usually see, such as the steps (which are added to your daily activity to reach your goal) or the meters of accumulated unevenness.
And when you get close to your phone again, if you don't have it with you, your activity will be synchronized and you can check data such as rhythm, heart rate or calories on the Fitbit website.
And of course, of course, in the mobile application as well.
A very practical feature is that if you are doing interval training you can select whether you want to see the manually set times or the automatically set lap times per kilometre.
The application makes good use of the phone's screen, as it offers the information in differentiated tabs and at a fairly generous size.
The cycling option is something that was not integrated into the Fitbit Surge from the beginning. It is a separate application from the running one for two reasons. The first and most obvious is because in cycling we don't show the pace, but normally we will prefer the speed. Secondly and more importantly because the Surge, in its running profile, needs to have a running cadence for the correct calculation of the pace (if there is no cadence the pace it sets is 0). This was solved by adding the cycling exercise profile.
The Fitbit Surge has no support for any kind of external sensor, so you can't pair it with a specific speed and/or cadence sensor, let alone a power meter.
You should also note that if you want to have heart rate data, you will not be able to put the watch on the handlebars, for obvious reasons.
As for the data fields, they vary from the race profile, not only because now the rhythm is not shown, but also because what is most missing is the instantaneous speed information. That's right, this data is not available, and what is shown is the average speed. In a sense it makes a little bit of sense, since you are not going to wear the watch on the handlebars but on your wrist, so you are not going to use it as a cycling computer.
The fixed data on the screen are the same, distance and activity time, and the ones you can select in the lower band are the following:
- Average speed
- Heart rate
As you can see, the cycling profile is quite basic. It is valid if you want to count your cycling trips, but it will not be useful if you like cycling a little more seriously.
With the Fitbit Surge we are not going to limit ourselves to simply record running or cycling workouts thanks to the GPS, we can also use it for more generic activities, such as weight training, yoga or pilates. All of these are included in the "Exercise" menu.
These activities can be the ones that are configured by default (image on the left) or choose one of the ones that you can select additionally (image on the right).
These modes do not offer very special settings, it is simply a way to allow when syncing an activity to appear with the appropriate name, for poder to track it correctly. So, instead of syncing two activities with the name "exercise" that you won't know what each one is, it allows you to clearly identify them and know when it was a pilates or spinning class that you created.
When it comes to viewing the activities, there is nothing specific about them, and a gym session will show the same information as a spinning session (including steps, something a bit absurd...).
Additionally, in the running menu you can find another activity, called "Treadmill running". It allows you to more or less accurately track paces and distances when running indoors, taking data from the internal accelerometer.
Unlike other models on the market, the Fitbit Surge does not have automatic calibration when we run outdoors, but sets a default step length depending on your height, but we can calibrate it manually. For this purpose Fitbit has a guide on how to do itAlthough instead of doing the procedure indicated by Fitbit (not everyone has an athletic track handy), simply take some of your past running activities using GPS, as you'll have an approximate distance measured by GPS and the total number of steps.
After making the division, simply enter the resulting data in the user configuration, and you can go on the tape.
The accuracy of the results, therefore, depends on the data you enter for the stride measurement. Although this will depend on each individual user and their usual rhythms, as well as the rhythm used on the treadmill, because normally the stride size for warm-up rhythms of 5:30min/km differs from the stride when you are running at 4:00min/km. Therefore you always have to count on a percentage of error, whatever value you enter, it will never be totally accurate.
Optical heart rate sensor
Fitbit has equipped the Surge with an optical pulse sensor, but it is not the typical Mio/Philips sensor (like the one that equips Mio Link or TomTom CardioThere is no information on who is in charge of the manufacturing, nor of the tests behind it.
There is no doubt that one of the most important selling points of the Surge is the pulse sensor integrated into the watch itself. But what we have to demand from this sensor is that it has the correct precision for high intensity exercise, that is, that it goes beyond the correct detection of the pulse at rest or moderate activity, which is what we can ask from the Fitbit Charge HR.
Fitbit Surge is a watch that has a running mode and an interval running mode, so the precision it offers in both modes must be more than correct, its performance must be flawless.
As far as resting pulse monitoring is concerned, we have seen before that we cannot put any constraints on it. It works correctly, recording all the data continuously and without showing readings that we could ever think were not correct. But we still have to see how it behaves during our sporting activities.
To do this I have selected different workouts that I have done during these weeks, and I have compared them with a pectoral pulse sensor, technology that we already know that, although uncomfortable, does not present major problems beyond not having sufficiently moistened the "pads" of the chest strap.
First of all, this training lasts about 1 hour, at a stable pace, and the only thing to note is the peak in which the pulse decays rapidly due to stopping to drink water. This point serves perfectly to establish a point where we can fix ourselves.
Comparing the two graphs, you can see how, except for the first section where it seems that the Fitbit graph makes a strange (surely it can be explained by a bad placement, and an adjustment of the strap, it usually happens to me when I go out to run), both graphs overlap perfectly, at least at the beginning of the training. But as the training passes, the graphs are separated, although the readings are very similar. Therefore you can see how the Fitbit is recording the data with some delay.
The second example is a 10 km workout, also at a constant pace. This time there are no stops of any kind.
But let's compare both graphs, which is where we can best check the results. This time there are hardly any problems. They do not overlap at 100%, but it is enough to have started recording one clock 1 second earlier than the other for the slight difference, but in this case the reading is totally correct.
But where the problems come is when it comes to making series or intervals. Here we find the Achilles tendon of the Surge optical sensor. If in the continuous readings more or less behaves reasonably, in the rapid changes of rhythm is where it gets lost. In the first comparison, in the first and third interval you can see how a stranger does, lowering the pulse reading when I'm just starting to make the interval. From there, instead of being at the same point as the chest sensor, we see again how the graph has some delay.
Two more intervals of that same workout, where again we see how the Fitbit Surge reading is always lagging behind the reading taken with the Garmin Fenix 3 and the chest pulse sensor. And, again, a complicated start in the second interval, lagging far behind the time when the interval starts.
However, when the time comes to cool down, there are no more problems here and the two graphs overlap perfectly.
As you can see, the Fitbit sensor is not up to what can be demanded of it when we train in a demanding way. This data can be valid for an activity monitor, where our workouts are mostly going to be more relaxed or without so much demand in terms of data accuracy. But as soon as we ask for more, we find the limitations.
Therefore, if you are interested in having a reliable monitoring of your heart activity during your exercise, it is difficult to recommend the Fitbit Surge for this task. If this detail is not that important to you or you are not going to do interval training, then the Fitbit Surge may be sufficient for your use.
As to whether Fitbit can solve this by means of an update, although I think it's complicated, it's feasible. In short, the sensor is working correctly and is able to read the pulse achieved. It's already a simple matter of adjusting the algorithm used and the data acquisition speed.
When we start an activity, the first thing we have to do is wait for the Fitbit Surge to search for satellites. And at this point it does not stand out especially, as it does not have satellite searches. Therefore, every time we start an activity, especially if we start at a different point than where we finished the previous one, we will have to wait a little longer than usual than with any other watch launched on the market in the last year or year and a half.
It's not that it's too long or excessive, it's just that being used to finding a satellite signal in a matter of 15 seconds, the Surge can take a little longer, but there's nothing better than showing you a video where you can check it out first hand.
This search is conducted two days after the last training, and 40 kilometers away, with a full view of the sky without buildings or trees that could be a problem.
But the most important thing is the stability of the pace shown, and how fast it is reflecting our speed changes. The latter is crucial, especially on days when we have a series training planned, especially if they are intense and short fartleks. And just like in the search for satellites, I have also recorded a video for you to check.
The Surge is quick to vary the rhythms, however, as Suunto does, the rhythm is filtered along with the cadence. This Suunto calls it FusedSpeed, present for example in the Suunto Ambit3.
As you have seen in the video, the instantaneous pace is shown in multiples of 5. So you will see your running times go from 4:10 to 4:15 for example, but not in between. However, you can select an average lap time (in interval racing) and those times will go to the second. Obviously when you finish your training the average pace will include those seconds in between (4:12 for example). In this aspect it behaves like the vast majority of new watches of other brands, only Polar keeps an instantaneous pace to the second.
As for the distances, I have been compiling them in a table for later comparison. These days of tests I am beginning to recover from an injury, so there have not been days of long runs, which is where the greatest differences may exist. However, at all times the distances are very close to those recorded by the other watch I always wore to training, a Garmin Fenix 3.
|Fitbit Surge||Garmin Fenix 3|
|Tuesday night training||6.79 km||6.81 km|
|Bicycle return from swimming pool||3.1 km||3.07 km|
|Cycling to pool||6.35 km||6.28 km|
|Water Race||5.45 km||5.2 km|
|Tests and photos Fitbit Charge HR||6.45 km||6.64 km|
|Wednesday night training||7.93 km||8.07 km|
|Recovery start training||6.22 km||6.17 km|
|Post Injury Test||4.01 km||4.04 km|
|Cloudy Thursday night||9.17 km||9.32 km|
Especially curious is the day of the Carrera de las Aguas, which officially had a distance of 6.1 km. Neither of the two is close to that figure, which is normal because of the difficulty of the test (most of the test takes place in the streets of a village, very narrow and with houses of 2 or 3 floors, very bad areas to have visibility of the sky), but both mark quite similar distances.
The figures are within the normal, in addition neither of the two is clearly marking greater or lesser distance than the other, but alternating in the possible failure. It is normal, because we must also take into account that they were carried in different wrist and this affects more than it seems, not only in terms of signal reception possibilities, but in terms of radius in curves and turns.
Recording tracks I have seen a curious case, and that is that, as with the heart rate data, there is a slight delay in making the recording, for example, the data from this cycling activity.
According to the Garmin graph, I took the traffic circle at 25.3 km/h. And I take this traffic circle as a clear example of how fast I was going. Most of all, because I entered the traffic circle quite a bit too fast, since it is a downhill traffic circle whose exit closes, and I had to brake quite hard to avoid going "over the top". Those 25 km/h seem to me to be quite consistent with the speed that pod would have been going at that moment inside the traffic circle.
The problem is that, according to the graph obtained with the Fitbit Surge, at that precise moment it says it was running at 39km/h. It can be seen at the point marked on the roundabout and on the line on the graph.
Furthermore, you can see how this point on the graph would correspond almost to the fastest point for this section, and after this point it decreases considerably. Being the exit of the roundabout, it is clear that the braking takes place before entering, and not when exiting.
That is, the speed data does not match the GPS position data, there is a time lag of seconds. For the vast majority this will not be a major detail, but if you like to analyze cycling trips or passing speeds at certain points, it can be quite uncomfortable.
If you check the specifications that Fitbit gives for the Surge in terms of battery life, the only thing you will find is the following message:
Battery life: up to 7 days
But there is no further indication of whether it is with or without GPS use, or with or without a pulse check, so there is not much data to hold on to in order to quickly assess the Surge's range.
As far as using activity monitor and recording some activities with GPS, along with constant synchronization with the phone (i.e. regular use), Fitbit makes it easy for me, since it regularly sends you emails (and warns you with messages in the application) of different events such as distances, activity summaries, medals for completing goals, etc. And among them it also sends another one when the battery is about to run out, so that will be the reference I use.
Here's an image of the time between two warnings. I simply let the battery level be too low before I put the Fitbit Surge back on, to let its battery run almost empty again.
In the end, it also depends a lot on how many activities with GPS use you do, because it is what consumes more, but just over 7 days is a very good result for a device that, I remind you, is reading heart rate data during all this time, in addition to recording activities with GPS use (in that period of time, about 3 hours in total).
And what about the autonomy with the use of GPS? Because nowhere in the specifications do we find information about this. The only detail I could find is what Fitbit sends in the same battery warning email, which states the following:
Under normal use, the battery should last up to 7 days. A fully charged Surge device can monitor up to 5 hours of activities that require the use of GPS. Happy trails!
Well, someone should check the contents of that email, because with the battery fully charged I started a cycling activity, which uses GPS and pulse sensor, and the duration has exceeded 11 hours. For this I just left the clock in the window on the roof, and I picked it up the next day.
Actually, I think it's excessive, especially considering the specifications that Fitbit gives, so I propose to do another test where I can constantly check the clock to see if it's recording the activity with the screen off or if there's something that doesn't match the normal use of the Surge.
For that I wait for a suitable opportunity, like the one last SaturdayI left the house at 8 a.m. and started an activity marked as cycling. After finding a GPS signal the day went on normally. I was going to be outdoors all morning, so it was a perfect opportunity to do the test.
At lunchtime he was still recording the activity, at which point I lost sight of him and when I got home he was obviously off. So after loading the clock and synchronizing it, I look at the result again on the web. And again it's more than 11 hours that he's been recording the activity.
But something doesn't add up, because if I started recording around 8 in the morning and arrived well before 7 in the evening, something doesn't add up here. And indeed, after reviewing the heart rate graph and going from a distance graph to a time graph, I seem to have died at some point in the afternoon, because the heart rate changes to a completely straight line.
In fact, the clock is not reaching 11 hours that it seemed to be reaching, but it is well over the 5 hours indicated by Fitbit. From the position of the graph I calculate that it will go through the 9 effective hours of autonomy, which without being the 11 hours I had been surprised with, is also a very good result.
What I suppose happens is that the clock marks in the file the end of the recording when the clock is put in charge and is turned on again. In both occasions it has coincided to have done it around 11 hours after starting the activity, which has helped the possible confusion. But thanks to the pulse graph and to the fact that I am not dead, it has been easy to find out how far the battery has gone.
The lighting options of the Fitbit Surge differ from what we are used to seeing in other watches. What is most missing is that there is no option to keep the screen always on, something that those of us who run around at night on a regular basis consider almost mandatory. Within the menu we find three different settings for the screen lighting.
- Auto (default option): The Fitbit Surge has an ambient light sensor (which can be seen in the frame of the screen) thanks to which the screen will light up automatically, if the ambient light is low, when the screen is used or a button is pressed
- On: The screen lights up whenever a button is pressed or the screen is touched
- Off: The display is not illuminated at any time
The addition of the illumination sensor is a good thing, but we still need an option that allows us to keep the screen on. When we run at night and we need to see some data on the screen, we must press it or press a button. We can use the left menu button, because within the activity it has no use of any kind and will allow us to illuminate the screen, because if you touch it you will most likely change the lower metric.
The lighting offered is not excessively intense, but it is more than enough to consult the data while we are running.
Use as a diary clock
First and foremost, the Fitbit Surge is designed to be the watch you wear every day, both for performance as an activity monitor and for heart rate monitoring. So Fitbit has made a special effort to make the wearing experience as a watch as complete as possible.
To begin with, there are several clock displays to choose from, all of which are quite aesthetically pleasing.
Among all of them, the one that stands out the most is "Flare" because the lines on the dial surrounding the time is the indicator of what has been your activity minute by minute. As you can see in the image, there has been no activity until around 5 pm, and this is how it is shown on the screen and how you can quickly identify it.
As with the Flare clock screen, there is a lower line on the keystroke screen that represents the intensity of activity over the most recent period of time, and if your keystrokes are currently in any of the areas defined through the application (automatically or manually), it will also be represented accordingly.
But it's not the only "smart" screen. The step widget also has a line that will fill in as you reach your goal for the day.
Fitbit Surge allows you to create multiple silent alarms, in which the warning will be through the vibration of the clock (there is no other way, since Surge does not have audible warnings). These alarms are not configured from the clock, but must be established from the application to synchronize later. However, it allows you to create a multitude of alarms, in addition to establishing a repeat on the days you want (for example, to wake you up on weekdays).
As I said, it is not possible to create the alarms from the clock, but it is possible to activate or deactivate them from the clock. Fortunately, once synchronized, we do not need the phone to disconnect them.
So if your phone runs out of battery on a Friday night and you've forgotten to turn off the alarm for tomorrow, don't worry, turn it off directly on the clock.
Fitbit announces that the Surge is capable of showing on-screen notifications, but I find the implementation very poor. Unlike other clocks, the Surge doesn't show notification of everything that appears in the mobile panel, but will only notify you of incoming calls and received SMS messages (and with a somewhat strange behavior, at least in Android). No notifications for applications like Twitter, Facebook or WhatsApp.
I don't know about you, but I haven't received any non-advertising SMS messages in a long time, and the number of calls per day is also quite small. Besides, when the call appears on the screen (at least in Android), it can take up to 2 seconds to show the notification, that is, in that time until the clock warns you who is calling you, you have usually already picked up the phone and seen it directly on its screen.
What the Surge does offer is music control, but to do this you have to pair your watch with your phone a second time, via standard Bluetooth, which will affect the battery.
Once this new synchronization is done, you can control the music both within an activity and in the clock mode. Pressing the menu button twice will start the music control mode.
From here you can not select any folder or song, the controls are basic. It will allow you to pause or resume playback or go to the next song, as well as display the name of the song and the artist on the screen.
Remember that all music playback will be done by the phone, you cannot load songs into the watch or use it as a music player independently.
I have mixed feelings about the Fitbit Surge. There are aspects of it that I really liked, but there are other details that make me hold my hands to my head and ask myself "but what the f...? (insert whatever interjection you feel like here).
Starting with what I least liked, without a doubt, are the mobile notifications. I think this is an important factor in this type of devices designed to be carried around with you at all times, and it is one of the main factors that Fitbit announces for the Surge. Well, these notifications are limited exclusively to showing you who is calling you (with a certain delay in notification) and to showing you SMS messages (who is still using SMS messages today?). In short, no Twitter, Facebook, email, messaging programs... And being a company based in Silicon Valley, the cradle of technological advances in terms of mobility, I think it's pretty creaky.
Another thing that I have missed a lot is the ability to configure the data displayed during an activity. I think that the arrangement of three fields with two of them fixed is quite clever and very appropriate for a device of this type, but I would love to be the one to say which fields I want as fixed, and not have them come predefined automatically.
As for the pulse sensor, it depends a lot on the use you want to make of it. If you want to have full control of your workouts and want to follow up after the activity is over, it's easy to find its limitations. But on the other hand, for normal use (which, in the end, I think is the use that 95% will make of Fitbit Surge buyers) it's more than enough, and well above what has been offered so far in products such as Samsung or Motorola watches, aimed at the same type of audience.
I think the mobile application is fantastic. In both iOS and Android it is simple, very graphic and fast to use. However, the web portal is a bit more chaotic and slow, although most of the time it will be on the mobile where we consult all the information.
In short, I think that the Fitbit Surge has a complicated situation in the market. Not because it is a bad product, but because it is halfway between different types of users. Whoever is looking for a watch to run and it is imperative that it has the pulse sensor integrated into the watch itself has better options with more specific products, such as the TomTom Cardio and in a short time the Garmin Forerunner 225And whoever wants a device to control different sports activities but without the desire to compete, for about 100 euros less can get a Fitbit Charge HRIt's not that I don't recommend the Surge, but I think that among running watches there are much better options, and as an activity monitor there are cheaper options.
As Fitbit's first device with GPS, I think it's enough, but I'm looking forward to seeing how far they can go. They offer a very fresh view of the sector, and I think they can bring a lot of new ideas to the table. But some effort with the Surge would be welcome, especially in the area of mobile notifications, where I think they need to improve further to match the competition. And that same development will be useful when they launch a replacement.
Did you like the test?
I hope that this test has cleared up some doubts about Fitbit Surge. The truth is that doing each test you see on this page requires many hours. Taking data, photos, videos, writing your own test... It's a long and demanding process, because I only like to offer you the best.
If you liked it and want to show your gratitude, you can leave your impressions in the comments below. It will help me to know your opinion, or to ask me questions if something is not clear to you. Share the post on social networks, I'm sure your friends will like it too.
If you want to buy the device, you can do it in the links below, so you save by getting good offers, and I get a small commission that supports this website and its tests.
Buy Fitbit Surge
You can buy Fitbit Surge in three different colors, the black one you have seen in this test and also in blue or orange. For both models there are two sizes available, S or L. Here are the links where you can buy it.