There’s a double edged sword going on with modern smartphones. On the one hand they can do loads of stuff, but the flip side is that they might not do certain tasks as well as a dedicated device. For most tasks the compromise might be acceptable, but what are they like for tracking your bike rides? How do they measure up to dedicated GPS units?
In this post I’ll share the findings of a little experiment I did, which involved my friend’s iPhone 4S running the Strava app, my Android phone, a Samsung Galaxy S2, running the MyTracks app, and my Garmin Edge 800.
The experiment was initially devised to determine if Strava segments were being interpreted differently according to variation in the gpx tracks produced by different devices. The idea was for a group of riders to ascend a hill together, and see if strava interpreted the segment timings correctly.
This post is an off shoot of that experiment, mainly because I thought the issue was worth highlighting.
Here is the Garmin track, which we can use as a reference. It follows the road perfectly, and all segments are picked up by Strava, every time.
Here’s the iPhone 4S track. It’s all over the place. It barely follows the road any point, and Strava did not recognise this as the segment it actually covered.
If this is the quality of the GPS tracking on iPhones – don’t use one!
Just stick to Angry Birds or whatever….
Here’s the track recorded by the MyTracks app on my Samsung Galaxy S2 (Android).
It’s very accurate, and like the Garmin track, never deviates from the actual route taken. Strava recognised the segment and ranked it as an identical time to the Garmin.
(The garmin was mounted to my bar, and the phone in my jersey pocket)
I took a closer look at that iPhone track, and found this little delight (below).
I have no idea what’s going on here. We were travelling from the East, following the road by the side of the river. The iPhone starts daydreaming and wanders off the track, only to snap out of it and suddenly jump back to the road at a later point (the zig zag bit).
The garmin and android tracks had no such oddities, and were consistent for the entire 58 mile ride.
If you’re serious about tracking your cycling, there is no better option than a dedicated unit such as a Garmin. Smartphones can give you a taste of it, and on the basis of this limited evidence, it would appear that Android does it more effectively than Apple. But they would both suffer poor battery life anyway, so the Garmin still wins.
There are loads more reasons to ditch your phone and get a proper GPS for your bike.










Hi Alan
Interesting findings. Hope you don’t mind if I put a some what different slant on your comments.
Today I road the Liverpool-Chester-Liverpool 50 mile event and recorder the ride on my Garmin 800. I then downloaded the results to my PC using both Garmin Connect and Strava. I rather surprised to see different results from both.
Garmin Connect Strava
Distance 51.00 miles 51.00 miles
Time 3:15:11 2:59:45
Moving Time 3:14:51
Elapsed Time 3:40:44 3:40:48
Max Speed 27.9 m/h 27.7m/h
Elevation Gain1608 ft 1318 ft
Avg HR 128 129
Max HR 161 161
Sorry for that Alan, I do not know what I did wrong there but I seemed to have posted it without finishing my comment. Possibly when I tried to put the data into columns. The second figures are from Strava.
The Garmin Connect gave me an average speed of 15.7 m/h against Strava at 17.0 m/h. I like Strava’s figure better! There is considerable difference between some of the data yet some is more or less the same. Makes me wonder what is most accurate.
Like your Website.
Hi Ian, thanks for your kind words and for sharing your data. It does seem like several people are reporting differences between Garmin connect and Strava too. Perhaps until we get the next generation of GPS which civilians can access, we’ll always have these discrepancies. Until then, I’ll keep telling myself it’s reliable *enough* because it motivates me to train harder.