All posts
Guides ·4 June 2026 · 10 min read

Browser vs installed app: why riding indoors shouldn't need a 12 GB download

The Moveee team

Free coaching · a real route for every ride

Riding a stationary bike in your spare room should not require the same disk space as a modern video game. Yet that's roughly where the category landed: pick almost any well-known indoor platform and step one is a multi-gigabyte download, step two is an update, and step three — eventually — is the ride. On the evening you actually carved out an hour, that ordering stings.

It doesn't have to be that way any more, and this piece is about deciding when it should and shouldn't. Browser-native indoor apps now exist; installed apps aren't going anywhere. Both are legitimate. So here's a straight, feature-by-feature comparison — including the handful of rows where the installed app genuinely wins — to help you pick the right one for how you actually train.

The ledger, row by row

No thumb on the scale. Each row names a winner, and the browser doesn't take all of them.

Browser-native Installed app Edge
Getting started Open a URL, pair, ride — about a minute Download, install, update, then ride Browser
Install size Zero — there's nothing to install Typically 5–15 GB, per platform Browser
Updates Always current; nothing to download Manual or background downloads, sometimes mid-session Browser
Disk footprint None left behind Gigabytes, and it tends to grow Browser
Cross-device Any Chromium machine — nothing to reinstall Reinstall and re-log-in on each device Browser
Trainer pairing Bluetooth — FTMS, CPS, HR via Web Bluetooth Bluetooth and ANT+ (with a dongle) App
Works offline Needs a live connection Rides offline once it's installed App
Background / screen-off Tab must stay awake and in front Can hold a ride in the background App
iPhone & iPad Not yet — iOS has no Web Bluetooth Full native iOS / iPadOS app App

Install sizes are indicative and vary by platform; the ANT+, offline and iOS rows are the ones worth weighing hardest, because they're the browser's real, structural limits — not rough edges that'll be polished away next month.

Open countryside rendered in Moveee Indoor, a real road switchbacking up a hill — all running in a browser.
A full 3D world with real roads and terrain, running in a tab. The rendering was never the hard part of going browser-native — the pairing was.

Where the browser genuinely wins

The browser's advantages cluster around one idea: there's no software to own. That sounds minor until you've spent a February evening watching a progress bar instead of warming up.

Nothing between you and the ride

No install, no update queue, no gigabytes. The gap between 'I have an hour' and 'I'm pedalling' is about a minute.

It follows you anywhere

Work laptop, family PC, a friend's machine — sign in, pair, ride. There's nothing to carry and nothing to reinstall.

No maintenance debt

You're always on the current version, and you never lose an evening to a download that had to finish first.

Where the installed app still wins

And now the other side of the ledger, because pretending it doesn't exist would be dishonest. These aren't teething problems a browser app will fix next quarter — they're structural, and for some riders they're decisive.

Truly offline

Once installed, a native app rides with no connection at all — a real advantage in a garage with patchy Wi-Fi.

ANT+ hardware

Older trainers and some power meters only speak ANT+. A native app plus a USB dongle reaches them; a browser can't.

iPhone & iPad

If your pain-cave screen is an iPad, a native app is currently your only route — iOS doesn't expose Bluetooth to the browser.

The browser's honest catches

A browser tab has quirks a dedicated window doesn't. If your machine sleeps or the tab drops to the background, rendering can stutter, so it pays to keep the tab awake and in front — plug the laptop in and turn off sleep before a long session. A good browser-native app should also back your recording up as it goes, so a closed tab or a dropped connection can't wipe the ride. That last part is a fair question to ask of any browser tool before you trust an hour of intervals to it.

A cyclist training hard on an indoor smart trainer
Whichever side you land on, the trainer's the same — it's the software around it that decides how much friction stands between you and the effort.

So which should you pick?

Here's the honest landing point, without overclaiming: for most people, most of the time, browser-native is enough. If you ride a Bluetooth smart trainer on a laptop, in a room with Wi-Fi, the browser's wins — instant start, nothing to install, no updates, follows you to any machine — are real and daily, while its losses barely touch you. If you're on an iPad, depend on ANT+, or train somewhere genuinely offline, a native app is still the right tool, and there's no shame in that. If you're still choosing the hardware underneath all this, our smart trainer buying guide covers what to look for — Bluetooth versus ANT+ very much included.

The browser-native option we build is Moveee Indoor — our own product, and we'll say so plainly. The whole ride runs in Chrome or Edge: pair your trainer over Bluetooth, ride your own real routes rebuilt in 3D from map data, hold watts in ERG mode, and the finished session backs itself up as you go, then counts toward your Moveee training plan and heads to Strava in a tap. It's free while in alpha, with the honest caveats above. If you want to see the browser side in action first, our walkthrough on how to train indoors in your browser takes it step by step.

Twelve gigabytes was never the price of a good indoor ride. It was just the price of the era that's ending.

Ready to ride with a plan?

Connect Strava and get your first three-week block today — free.

Continue with Strava