Skip to content
Kinni Support

reference

Virtual apps and FitCast overview

Use this overview when choosing whether Kinni should broadcast live run data through FitCast or use a separate app workflow.

Virtual running apps can make indoor treadmill sessions more visual, social, or structured. Kinni fits into that workflow by controlling or recording the run in Kinni, then using FitCast when another app needs a live Bluetooth signal.

This topic covers apps such as Zwift, Rouvy, Peloton, BitGym, Kinomap, and similar services. Those apps stay external to Kinni; Kinni does not manage their accounts, subscriptions, routes, classes, or workout libraries.

Most virtual-app workflows use two devices:

  1. Kinni device — runs Kinni, connects to the treadmill or sensors, and records the session.
  2. Virtual-app device — runs Zwift, Rouvy, Peloton, BitGym, Kinomap, or another app and scans for the Bluetooth signal that Kinni broadcasts through FitCast.

Use Kinni as the source for the run you are actively controlling or recording. Use the virtual app for its world, video, class, route, or social experience.

FitCast lets the second device discover Kinni as a Bluetooth fitness signal. Depending on the live run data available in Kinni, FitCast can expose treadmill-style data, running speed and cadence, and heart-rate data.

This is different from account linking. Strava and TrainingPeaks are connected-app workflows for post-run uploads; FitCast is a live Bluetooth bridge for another app during the run.

  • Zwift commonly pairs to FitCast from its pairing screen. Use the Zwift connection article when you want a step-by-step setup.
  • Rouvy, BitGym, and Kinomap may be able to read a compatible Bluetooth treadmill or running sensor signal, depending on the device and app version.
  • Peloton is usually a separate class or content experience. Treat Kinni as the run recorder/controller unless Peloton explicitly asks for a Bluetooth source it can pair with.

Because each external app controls its own pairing screens and compatibility rules, the stable Kinni guidance is: start with Kinni and FitCast working, then scan for Kinni FitCast from the other app.

Do not let two apps fight over the same treadmill. If Kinni is connected to and controlling the treadmill, use the virtual app as the display or recording companion unless you intentionally choose a different setup.

If the treadmill moves unexpectedly, use the treadmill’s physical stop or safety key first. Then stop the Kinni run, turn FitCast off, and check whether the treadmill is paired directly to another app as well as Kinni.

Still need help?

If an article does not answer your question, open Kinni and use in-app support, or join the Kinni Discord community for help from the team and other runners.

Join Kinni Discord