The social half is why the GPS traces need to be on a server, why there is a profile, and why the privacy settings are a screen with a dozen switches. Take it away and most of the reason for the cloud goes with it, because a training log is a private document.
cronoWiz records the same session — GPS, distance, pace, splits, heart-rate zones, cadence, elevation — and keeps it on the phone. Repeat a loop and it recognises the route and groups the runs into one circuit, so a Tuesday-evening 5K becomes one thing you have run twenty times instead of twenty unrelated entries.
Competition is still there; the audience is not. You can chase a ghost of your own previous run, or a friend’s, packed into a file they send you. There is no feed, no kudos, no followers, and no segment leaderboard, because none of those work without putting everyone’s traces in one place.
-
The training log without the feed
splits, zones, cadence and elevation, kept privately.
-
Routes recognised
the same loop is grouped into one circuit instead of fragmenting.
-
Racing without an audience
your own ghost, or a friend’s run sent as a file.
-
GPX in and out
plan a route, export it for a watch, or import one from someone else.
What you keep, and what you give up
Kept: GPS recording, distance, pace, splits, elevation, cadence, heart-rate zones from a Bluetooth strap, the full route on a map, and a history that groups repeats of the same loop into one circuit. A Tuesday-evening 5K becomes one route you have run twenty times, with the twenty runs beside each other, instead of twenty unrelated entries you scroll past.
Given up: segments, leaderboards, kudos, followers, clubs, and the feed. These are not missing features waiting to be built — every one of them needs everybody’s GPS traces sitting on one server, which is the thing being removed. A segment leaderboard is not technically hard; it is architecturally the opposite of a training log that stays on your phone.
What replaces the competitive part is racing a ghost: your own recorded pace over the same route, or a friend’s run packed into a file they send you. It is competition with a specific person you chose, rather than with an audience you did not.
Bringing your existing history across
There is no direct connection to Strava, and there is not going to be one — it would mean an account on both ends. What works instead is Strava’s own bulk export: in the web settings, under “My Account”, request an archive of your data. It arrives as an email with a zip containing every activity as a .fit or .gpx file.
Those files go into cw·dashboard, which reads them in the browser — the parsing happens on your machine, and nothing is uploaded — and adds them to the same history the app writes to. Routes you have run before get recognised and grouped with the new ones, so an imported year of running does not sit in a separate silo from what you record from now on.
It goes the other way too. Plan a route and export it as GPX for a watch, or import a GPX someone sends you and follow it. The point of a file format is that it works without either side having an account with the other.
Free. Private. Yours.
No account. No server. No cookies. Just you, your phone, and an app that minds its own business. cronoWiz is a free PWA that runs entirely on your device — your data never leaves. Ever.
The questions people actually ask
Can I import my Strava history?
Not directly from Strava. Sessions exported as .fit files can be brought in through cw·dashboard, which reads them in the browser and adds them to the same history.
What about segments and leaderboards?
There are none, and it is a deliberate omission: a leaderboard needs everyone’s GPS traces on one server. The nearest equivalent is racing your own recorded pace over the same route.
Can I share a run at all?
Yes — as a file or a short link, sent to whoever you choose. It is a message, not a post.