The first time we sketched TeenCycle, the design doc had a section called "Sync." Of course it did — every modern app syncs. You log in on your phone, your data follows you to the web, your settings appear on a new device. That's the modern contract: convenience for an account.
Then we sat with the kind of person we were actually building for — a 14-year-old who'd downloaded three other trackers and deleted them all because "they kept asking me for stuff." Email. Birthday. Whether she'd like personalised insights. Whether her mom should get notified. The apps were trying to be helpful. They felt like surveillance.
So we crossed out the "Sync" section and started over. What if the app never asked for anything? What if it didn't even have a way to know who you were?
What "offline-first" actually means.
The phrase gets stretched a lot. For us, it means three concrete things:
- No account, ever. There's no sign-up screen, no "continue with Google," no email required. The first time you open the app, you're already in.
- No data leaves the device. Not for analytics, not for crash reports, not for "anonymous usage statistics." We don't run a server you could send data to even if we wanted to.
- Works without a connection. Airplane mode, no signal, Wi-Fi off forever — the app behaves identically. It has nothing to ask the internet for.
This isn't a marketing posture we can flip on later. It's baked into the architecture. There is no backend codebase. There is no database with your name on it. There is nothing for us to lose, leak, or hand over.
What it cost us.
Being honest: the decision to skip sync made things harder, not easier. Here's what we gave up.
1. Multi-device convenience.
If you move to a new phone, you have to export your data and import it on the other side. We can't do that for you, because we don't have a copy. We wrote about how the export works in support, but it's a real extra step that competitors don't have.
2. Recovery from a lost phone.
If you drop your phone in a lake and didn't export recently, your cycle history goes with it. There's no "log back in to recover." That's a real trade-off, and we tell people about it before they buy.
3. Server-side anything.
We can't add a parent dashboard. We can't ship a web app. We can't run server-side prediction models trained on aggregate data. Every feature has to live on the phone, in code we can audit and you can verify.
"Offline-first isn't a feature. It's a constraint that shapes every product decision after it."
— our internal design principles, line 1
What it gave back.
The constraints turned out to be the point. A few things became possible that wouldn't have been otherwise:
- A one-time price. Without servers to run, there are no ongoing costs to recoup. $9.99 once, forever. No subscription, no renewal, no second charge.
- A genuinely calm product. No social feed pulls you back. No push notifications nudge you. No streaks to break. The app is a tool you reach for when you need it.
- A promise we can keep. "We don't sell your data" is something every company says. "We don't have your data" is something only a handful can.
For the audience we care about most — teenagers, who didn't ask to have their cycles treated as marketing signal — that last one is the whole reason we built the app.
If you've read this far, thank you. We don't write often, and we don't write a lot. If you want the occasional piece like this in your inbox, you can subscribe to the journal — one email a month, no tracking pixels, unsubscribe in a click.
And if you've been using TeenCycle: thank you for trusting us with the privilege of not knowing anything about you. It's our favourite thing about what we do.
