Running with only your phone, and what it covers

A phone is already a complete run recorder. It carries a satellite receiver, a step counter, a clock and a speaker, and between them those cover distance, pace, splits, cadence and route. What it does not carry is a wrist heart rate sensor or a screen you can read at a glance.

What a phone records on its own

Distance, pace, splits, cadence and route. Nothing plugged in, nothing paired. Distance and the shape of your route come from satellite fixes, and pace is distance over elapsed time, so it inherits whatever the distance did. Splits are arithmetic across the same track. Cadence comes from the step counter phones already run for their own health features.

Elevation is the weakest row in that table.

Whatever an app derives it from, the figure is an estimate. It is not a measurement, so do not build training decisions on small differences in it.

Two questions that share one phrase

Running without a watch means two opposite things.

Searching the phrase returns both mixed together. Work out which one you are asking before you take any advice.

• Phone, no watch. You carry the phone, it does the recording, and the thing you need is an app that keeps running with the screen off and tells you your numbers out loud.
• Watch, no phone. You leave the phone at home and the watch does the recording, and the thing you need is a watch with its own satellite receiver and onboard storage, plus somewhere to put a key.

They fail in different places. A phone only runner loses a run to a permission, a battery setting or a crash. A phone free runner loses a run to a watch that never synced. Advice written for one is close to useless for the other: battery and permission steps mean nothing to someone whose phone is at home, and watch sync steps mean nothing to someone who owns no watch.

What a phone cannot measure

The gaps are real and structural. None of them is fixed by a better app, so the useful thing is knowing which ones you are accepting.

• Heart rate. No phone reads your pulse from a pocket, so every heart rate number on a phone screen arrived from a watch, a strap or a health store.
• A glanceable display. Reading your pace means taking the phone out, and a manual lap means handling the phone.
• A lap button under your thumb.
• Running dynamics such as ground contact time and vertical oscillation, which need a device fixed to your wrist or torso.
• Anything measured while you are not running, such as overnight recovery figures.

Two of those are about reading numbers, not recording them, and that is the gap spoken cues close. The rest are sensors, and no software recovers a sensor that is not there.

The setup that has to be right before your first run

Three settings decide whether an hour of running survives.

A fourth step is the short test that tells you whether they took. Do all four once, before you rely on the setup for anything long.

1. Grant location at the while using level, and start the run with the app openApple defines that status as "The user authorized the app to start location services while it is in use", and adds that "To continue using location services in the background, enable Continuous Background Location Updates and start the services while the app is in use" (Apple developer documentation on CLAuthorizationStatus.authorizedWhenInUse, checked 2 August 2026). A run tracker you started yourself is exactly that case, so Always is not the setting it needs.
2. Grant precise rather than approximate locationAndroid's permissions guide describes an approximate location from the platform providers as "accurate to within about 3 square kilometers (about 1.2 square miles)", against a precise one that "is usually within about 50 meters (160 feet) and is sometimes as accurate as within a few meters (10 feet) or better" (Android developer documentation on location permissions, checked 2 August 2026). The coarse level cannot draw a route.
3. Let the app keep working while the screen is offOn Android a foreground service is what buys this: "Your app retains access when it's placed in the background, such as when the user presses the Home button on their device or turns their device's display off" (Android developer documentation on location permissions, checked 2 August 2026). In practice, leave the app's persistent notification alone, exempt it from battery optimisation, and do not run the phone in a power saving mode.
4. Test it with the screen locked before you trust itStart a recording, lock the phone, put it in the pocket you actually use, walk for five minutes, then look at the track. A straight line, a stalled timer or a missing middle tells you more than a settings screen will.

Carrying the phone so the fix stays usable

Carry it where your own body is not between the phone and the sky. The United States government commits to broadcasting the signal in space with "a daily global average user range error (URE) of ≤2.0 m (6.6 ft.), with 95% probability", and then says plainly that "To be clear, URE is not user accuracy", because user accuracy "depends on a combination of satellite geometry, URE, and local factors such as signal blockage, atmospheric conditions, and receiver design features/quality" (GPS.gov accuracy page, on the government archive host, checked 2 August 2026). Signal blockage is the term that matters to you, and where you put the phone is one of the few parts of that list you control.

• An armband, a waistband belt or a vest chest pocket keeps the phone on the outside of you.
• A front trouser pocket works, since the phone sits at the front of you, not behind.
• The bottom of a rucksack worn on your back puts your torso and the pack in the way.
• Your hand works, though the arm swing adds movement the track has to absorb.

Give the phone a moment outdoors before you press start, and start in the open, not under an awning or a bridge if you have the choice. Neither habit turns a phone into a survey instrument. Both spend a few seconds on the part of the track people most often mistrust afterwards.

Getting your numbers by ear instead of by looking

Spoken splits are the replacement for a glance at your wrist, and they decide whether phone only running feels workable.

If the app talks, the phone stays in your pocket for the whole run. If it does not, you stop to read a screen, and the setup becomes worse than a watch, not merely different.

• Does it still speak with the phone locked and in a pocket, not just in your hand?
• Is the announcement interval fixed or adjustable, and does the settings screen say which?
• Does it lower your music while it speaks, and can you turn that off?
• Does it say anything when you pause, resume or finish?

Runflake's own answers to the first two are on the record. In metric its distance announcement fires on every completed kilometre, and the 1,000 m lap length is a fixed constant in the signal config rather than a user setting. It keeps speaking with the screen off and in your pocket, and its announcements are heard even with the iPhone silent switch on, which is deliberate. On the recording side, every GPS point is written to the phone's database the moment it arrives, before the app does anything else with it, so there is no save timer and no save at the end step for the raw track.

That second half matters more when the phone is your only recorder, because no watch is holding a second copy. Why running apps lose runs covers where a run is actually lost, and what running apps actually say out loud covers how to check any app's wording before you install it.

Where a watch is still the better tool

A watch wins on reading.

It wins on wearing too, and on anything that needs a sensor against your skin. If a session depends on holding a target pace minute by minute, on intervals you have to see, or on heart rate at all, the wrist is the right place for the device.

There is a second reason to know where you stand, which is that some coaching features are tied to one watch, and the requirement is usually stated only on the vendor's own support page. Samsung's states that "Galaxy Watch8 and Watch8 Classic feature the personalised Running coach", and that the programme "is available on Android phones (Android 10 or above) and requires Samsung Health app (v6.30.2 or above)" (Samsung support page on the personalised Running coach, checked 2 August 2026). Garmin's Forerunner manual puts the plan in the account and the watch in the reading: "Your Garmin Connect™ account has an adaptive training plan and Garmin® coach to fit your training goals", and "When you start a plan, the Garmin coach glance is added to the glance loop on your Forerunner® watch" (Garmin Forerunner 265 owner's manual, Adaptive Training Plans, checked 2 August 2026).

Read the requirement line before the feature list, and note that the two cases are not the same. Where a watch is named in the requirement, installing the phone app alone does not get you the feature. Where the plan lives in the account, the manual establishes only that the watch is where it surfaces while you run, which tells you what a phone will not give you, and not whether the plan is usable at all. If you are planning a block of training around a phone, half marathon training with a phone only works through what that means week to week.

What phone only means for leaderboards

A leaderboard ranks whatever it scores. If it scores something a phone cannot produce, it is ranking equipment as much as running. Heart rate is the clearest case: a board built on effort measured at the wrist is closed to everyone whose only device is in their pocket, whether or not anyone intended that.

This is a design choice a product can state rather than a fact about running. In Runflake a watch is not required for distance, pace, splits, cadence or elevation, and heart rate never enters any ranking. It is barred by written rule from every judgement axis, including goals, XP and course completion, on the reasoning that including it would make the metric favour whoever owns a watch. The phone has no heart rate sensor, so a run with zero heart rate samples is the normal case, and heart rate can only arrive from a paired watch, a BLE strap, or the platform health store.

Before you join any board, read what it ranks and ask whether you can produce that number with what you own. Distance and pace you can. Anything derived from a wrist sensor you cannot, and no amount of running changes that.