RunVue 사용 가이드

What RunVue does

RunVue turns a run you have already recorded into a short 3D replay video. It is not a live tracker you start before heading out. Instead, you finish your run with your watch or favorite running app, and RunVue reads the workout from the health store on your phone (Apple Health on iPhone, Health Connect on Android) and renders a video. Rather than a bird's-eye map, the video follows your route at runner height. The default camera chases from behind in third person, switches to first person during highlight sections, and finally rises to a sky view that shows the whole course.

It suits people who want to share a run in a more memorable form than a screenshot of a watch screen, and people who like keeping a visual log of a favorite route. It is not a coaching tool: if you want live voice cues or structured training, use a coach app or your watch's workout app, and let RunVue present the result afterwards.

Screens at a glance

The five images below are iPhone screens: two video scenes, then settings, library and import.

What you need

• A run with a location route. The workout must have been recorded outdoors with GPS. Treadmill and indoor workouts have no route to follow.
• Health data read access. Allow the app to read workouts and heart rate from Apple Health or Health Connect. On Android, the route permission is handled on a separate screen; if a run appears in the list but is reported as having no route, check the route permission in Health Connect settings.
• A network connection. Map tiles are downloaded to draw buildings and roads, so rendering may need internet access. Your personal route is not uploaded in the process.
• A reasonably capable device. Rendering and video encoding happen on the device itself, so older phones take longer. Plugging in while you export is a good habit.

The app is listed on both the App Store and Google Play. Supported OS versions and regional availability are shown on each store page, so check there before installing.

Making a video, step by step

1. Grant permission. On first launch you are asked for read access to health data. The app limits itself to what the video needs: workouts, routes, and heart rate. It does not collect your birth date or weight. Maximum heart rate uses a fixed value, and calories come from the recorded value when available or an estimate shown with a tilde (~).
2. Pick a run. Choose a workout from the list. If you have no runs yet, you can try a sample to see what the result looks like.
3. Preview. The chase camera follows the route while the HUD shows pace and heart rate, with a mini map in the top right and section information. Videos are vertical (9:16) and run 22, 27 or 32 seconds depending on the distance you covered.
4. Adjust view and speed. For free you get the default navigation camera and a 1x summary video. Playback speeds from 2x to 60x, the cinematic and calm camera presets, and camera height and zoom controls are part of the subscription (Pro). If Reduce Motion is enabled in your system settings, the calm preset is available at no charge.
5. Save and share. Saving to your Photos library is the primary route, and you can also send the file to other apps through the system share sheet. Every video carries the app watermark, and map data attribution (OpenStreetMap) appears at the start and in the ending.

Reading the screen

The HUD

The pace badge at the top shows speed as minutes per kilometer, and heart rate appears in beats per minute. A waveform of speed and heart rate along the bottom summarizes the effort of the whole run, and it is free. Playback uses variable speed: straight stretches pass quickly while notable sections slow down, so time in the video is not proportional to real time.

The ending

The last scene sweeps the full course from above, lists place names the route passed, and shows a short run summary. Place names try to follow your device language, but fall back to the default name when the map data has no translation.

Tips for better results

• Wait a few seconds for a GPS lock before you start a run. A jumpy start shows up as a shaky camera at the beginning of the video.
• Courses between tall buildings or through tunnels may look slightly off. Map matching snaps the track to roads, but it is not perfect.
• If you want heart rate in the HUD, pick runs recorded with a sensor or a smartwatch. Runs without heart rate simply show no value.
• Render the same route every few weeks and compare; seasons and pace changes make a nice record.
• Keep the app in the foreground while exporting. Background rendering can slow down or pause.

Troubleshooting

• The run list is empty. Confirm the run is really stored in the health app and that RunVue has read access. Syncing from a watch can take a while.
• It says there is no route. The workout was indoors or recorded without location permission. Choose a different run.
• The map looks plain. Maps come from OpenStreetMap, and building height data is thin in some regions. Average heights are used where data is missing.
• Export is slow. Check device temperature and free storage, and close other heavy apps.

Privacy and data

RunVue needs no account, and it is designed so that your routes and health data stay on your device. The server only provides static map files, and the policy is not to keep individual request logs. See the privacy policy for details. Subscription payments are handled by the respective store.

Limits and known issues

• It only turns already-recorded runs into videos. It is not a live tracker or a coach. The run must be an outdoor run with a GPS route; treadmill and indoor workouts have no path to follow.
• The watermark and map credit cannot be turned off. Both free and subscription videos carry the app watermark, and the map data (OpenStreetMap) credit is included for licensing reasons.
• The whole route is visible. A run that starts and ends at home can reveal where home is, and the app has no feature to mask a segment. Manage who you share with yourself.
• Map quality varies by region. Where building height data is missing, an average height is drawn instead. Courses among tall buildings or with many tunnels can show the route passing through buildings.
• Video length is one of 22, 27 or 32 seconds depending on distance. Time in the video uses variable speed, so it is not proportional to real time.
• It is sensitive to device performance and heat. 3D rendering and encoding happen on the device, so older devices take longer. Keep the app in front and charge while it renders.
• The free range is limited. The 1x summary, Navi camera and waveform are free; changing speed, the cinematic camera, height and zoom need the subscription (Pro). The GPX import in the screenshot is from the iPhone app; check the store description for what the Android app supports.

How it compares

Sharing strategy and safety tips are in the running replay video guide.

FAQ

If you need more help, visit the support page.