RunKeeper and Target Pace

[AndyD]

Is anyone using the target pace function on the free version of RunKeeper on Android?? I've just discovered this function and may be useful. I presume it tells you to speed up or slow down... if anyone is using it I would be interested in any feedback and good they think it is.

Thanks for any help

[IannodaTruffe Mentor]

I haven't dared to use it! Annabel Runkeeper-Smythe is mainly reliable, but frankly just takes the p**s with her reports of my current pace, so I wouldn't trust her with the target function. But, nothing ventured, nothing gained, so I'll wait to hear how you get on!!

[AndyD Graduate in reply to IannodaTruffe]

Thanks for your reply. I really like RunKeeper and don't like to go out without it but I totally agree on the "current pace" alerts. I hope that it works as I could really do with something to report on my pace as I tend to go off too quick!

I'll have a go at the target function and see how it goes. I actually switched it on during my slow craw home in the car tonight and it appears to report at the time or distance set for the other audio cues... so i wonder whether the target pace is over that reporting period or the run so far...something to test and play with.

[Bazza1234 Graduate]

I find that "current pace" announcements by Runkeeper - either through the target pace function or just through the audio alerts that you can set up in it - are not reliable or accurate. You can see this on the pace chart at the Runkeeper site, where pace changes seem to occur every few seconds. . "Average pace" however is another matter - and i find this to be quite reliable and plausible. I generally aim for an average pace for most runs that I do - even run/walk intervals. I believe that any system that uses GPS points to work out pace between any two points is subject to wide fluctuations in result - the average over a longer period and distance is another matter.