Choose a GPS running app by the decision it improves

Make the next training decision

A GPS running app should record enough distance, pace and route context to support training without pretending every point is exact. Trees, buildings, turns, device placement and sampling can all affect the trace.

Choose it when: Choose reliable recording, understandable exports, privacy controls and battery life that covers the longest expected session.

Avoid this mistake: Avoid changing a plan from one noisy pace trace or publishing sensitive home and routine locations by default.

Apply it in five steps

1. Define the metrics you will actually use.
2. Test on a known route.
3. Check battery on the longest session.
4. Review privacy defaults.
5. Compare trends across repeated conditions.

General training information cannot guarantee performance, diagnose a condition or provide medical clearance. Stop for acute illness, severe symptoms or pain that changes normal movement and seek appropriate care.

GPS is a tool — not a judge

GPS data is noisy. Use it to support training decisions, not to “win” every easy run.

The 5 checks that matter

1. Split stability on straight segments (workout usable)
2. Battery life for long runs
3. Auto-pause behavior (often messes up workouts)
4. Exportability (you own your data)
5. A simple workflow you’ll repeat

How to use GPS well in marathon training

• Use effort + breathing to pace easy days.
• Use GPS splits for workouts (but don’t chase perfect numbers in wind/hills).
• Practice fueling and keep long runs repeatable.

Use these with GPS:

• Running pace calculator
• Marathon fueling planner