Why use Strava or Endomondo with Surge?

[StacyuDempsey]

I just upgraded from a Flex to a Surge. I use to integrate flex with endomondo because I used endomondo to track and map my runs. I was going to delete endomondo from my phone, but I see so many people that still use endomondo (or strava) with the fitbit app and Surge. I am not great about manual logging food and such, but am still curious why you would need an additional tracking app if you are using the Surge and tracking with their GPS. Am I missing something?

[Dominique]

For me, it’s Runtastic Pro, but the idea is the same: it’s another app that I use to log my walks/runs and resistance training. I started using it back in September 2013, when no Fitbit had HR monitoring, or GPS. Now I’m using a Surge, which indeed has both, but I continue to log my activities in Runtastic anyway, partly out of habit, partly because it still does things Fitbit doesn’t. For instance, Runtastic provides audio feedback every 1 km and every 15 minutes (I’ve set it up that way). This is convenient for me especially in winter time (I live in a cold country), when I can’t watch my Surge nor my phone. Runtastic also offers better support for HIIT-style workouts (haven’t even bothered to check whether I could do it in Fitbit). There’s no integration between Fitbit and Runtastic, but I don’t really care. I use them for different purposes and I don’t mind having similar data stored in both places.

[JohnRi]

The only reason I can think of is habit.  I used to use mapmywalk on my phone.  And when I got my Surge, I was not happy that the Surge always under reported miles walked, and pace times...  Then I started doing benchmarks on tracks that had milage markers.  And I found that the Surge was almost always dead on accurate.  99% to 101%.  Where mapmywalk was always over.

So I would guess that people how were walking 18 minute miles on mapmywalk, see the surge at 18:30 minute miles, and don't like it.

It's the same problem I'm having going from a Surge to a Blaze.  My blaze is about 3% short compared to the Surge.  I only went from the Surge to the Blaze because I LOST so much weight my Surge no longer fits!  But the Blaze has multiple band replacements, so I went with it this time.

I love everything about the Blaze over the Surge, except for GPS accuracy.  But the way I figure it, if I want the same numbers as the Surge, now I have walk 3% farther and faster.  So I guess that's not a bad thing...

But I dropped mapmywalk after I got the Surge.

[SebringDon]

I don't have a Surge, I have a Charge HR, but I've always used either MobileRun or Endomondo on my phone to provide GPS mapping.

Most of the time, I use MobileRun, because I like frequent feedback, and I can set MobileRun for two-minute voice prompts for time, distance, and pace. Every two minutes I get feedback.

Endomondo, on the other hand, only has one-mile feeback. So on my usual 5k (3.1 mile) course, I only get three voice prompts instead of 20 or so.

BUT... Endomondo tracks personal bests, and shows you where on the map you achieved that particular personal best, whether it's 1k, 1 mile, best in 12 minutes, or whatever. So every once in a while, I fire up Endomondo instead of MobileRun, declare it a testing day, and push to see if I can set some new personal bests.

So even if I had a Surge, I think I'd still be using Endomondo for personal best tracking. I also like the route feature of Endomondo, which isn't yet available in the Fitbit universe.