TimesFlow 0.1.66
A cleanup release.
Why the change
The app used to actively hit api.timesflow.app with a health probe at startup to decide "are we online right now?". That caused two problems:
- Slow first paint. Every cold start added an extra HTTP request; on bad networks you'd wait several seconds before reaching the main UI.
- Broken in offline scenarios. On a plane, on the subway, in a cafe with no signal — if the probe failed, the app assumed "the network is broken." But TimesFlow is offline-first by design: tracking and local data don't need the network at all.
What it is now
We now just use the browser's navigator.onLine as the network status signal:
- No backend request is made at startup
- The OS tells us the network state (airplane mode toggled, ethernet unplugged, Wi-Fi dropped)
- Sync logic is unchanged — it's just no longer a precondition for "did startup succeed?"
The payoff
Cold start is 2–4 seconds faster on slow networks. Offline startup is now a fully supported path — tracking, history, view switching all work normally; only the sync button will say "waiting for network."
No new features in this release, pure fixes. The next release (0.1.67) brings a bigger change to focus mode.