How it works
Does MiniCycle work offline? Period tracking with no signal
You are on a flight with the Wi-Fi off, or somewhere with one bar of signal, and your period starts. Can you still log it? With MiniCycle, yes. The app records the date, redraws the calendar, works out your next period and fertile window, and fires its reminders without touching the internet. The reason is plain: there is no account to sign into and no MiniCycle server to reach. One part does use the network, and it is worth naming out loud rather than hiding.
The short answer
Everything you do day to day in MiniCycle runs on the phone itself. Logging a period, editing a date, reading the predictions, jotting a note, checking the widget, getting a reminder: none of it waits on a connection. Turn on airplane mode and the app behaves exactly the same.
The usual assumption is that a period app has to sync with a server, the way a chat or mail app does, so losing signal would freeze it. MiniCycle is built the other way around. Your records live on the device, and the math that turns them into predictions also runs on the device. The network is not in that loop.
What works with no connection
The core of the app is fully offline. You can log a period start and end, fix a wrong date, and watch the calendar update. The predictions recalculate on the spot: the next period from your saved start dates, ovulation counted back from it, and the fertile window around that.
Daily notes, the statistics tab, and the home-screen widget all read from the same on-device data, so they behave the same with no signal. Reminders do too, because they are local notifications scheduled on the phone rather than messages pushed from a server. A reminder set for next Tuesday arrives next Tuesday whether or not you have been online since.
Why it can run without a server
MiniCycle has no login and keeps no copy of your history on a MiniCycle server. That choice is what makes offline use possible, not a side effect of it. With nothing to fetch and nothing to upload before it can answer, the app already has everything it needs on the device.
The prediction engine is part of that. It estimates your cycle length from up to your last 12 period starts, using a median rather than a mean (once there are at least 10 intervals it first drops the single shortest and longest), and falls back to 29 days when there is little history. Ovulation is counted back from the next expected period with a luteal phase clamped to 9–14 days, and the fertile window runs from 5 days before estimated ovulation through the day after. All of that arithmetic happens locally, in the moment you open the calendar.
The one part that uses the network
Being honest means naming the exception. MiniCycle includes Firebase Analytics, Google's usage-measurement SDK, which logs events such as app opens and screen views to show how the app is used. Sending those events needs a connection.
It does not block anything. When you are offline the usage events wait on the device and upload later, once you are back online, and in the meantime every feature keeps working. The website you are reading this on separately uses Google Analytics, but that is the site, not the app. So the accurate line is not that MiniCycle never uses the network, but that nothing you actually do with your cycle depends on it.
When you do need a connection
There is one obvious moment: installing the app or updating it goes through the App Store, which needs the internet. That is a one-time download, not a daily requirement.
After that, ordinary use asks nothing of the network. If you travel abroad with data roaming off, or spend a week somewhere with no Wi-Fi, the app keeps logging and predicting as usual. The reminders you set before the trip still fire on schedule.
What offline use can and can't do
Working offline does not change what the predictions are. They are reference information drawn from your own dates, not contraception, a pregnancy test, or a medical opinion, and being computed on the device with no connection makes them no more and no less certain than they would be online.
It also is not the same as a backup. Records kept only on the device can be lost if the phone is lost, reset, or the app is deleted, and offline use does not protect against that on its own. If keeping a copy matters to you, that is a separate question from whether the app needs a signal day to day.
Airplane mode, travel, and a weak signal
Picture a long-haul flight. You put the phone in airplane mode at the gate, and three hours in your period starts. Open MiniCycle, tap the date, log the start: it saves, the calendar redraws, and the next-period estimate shifts, all at 35,000 feet. Land, turn the radios back on, and there is nothing to catch up.
Or picture a week in a cabin with no Wi-Fi and roaming switched off. You log each day as usual, your notes save, and the period reminder you set last month still pops up on time. The only thing waiting for a connection is the handful of anonymous usage events, which upload quietly the next time you are online.
Frequently asked questions
Do I need to create an account or sign in? No. MiniCycle has no account, so there is no login step and nothing to authenticate against a server. You open the app and it works.
Will reminders still arrive in airplane mode? Yes. Reminders are local notifications scheduled on the phone, so they fire on their dates regardless of connection.
Does turning off Wi-Fi delete or hide my data? No. Your records sit on the device, so connection state does not touch them. They look the same online and off.
Does the widget update offline? Yes. The widget reads the same on-device data the app uses, so it reflects your latest records and predictions without a network.
Is anything sent while I am offline? Only the app's usage analytics, and only later. Those events wait on the device and upload once you reconnect. They are not your cycle data.
The one-line version
MiniCycle runs its core entirely on the phone, so it works with no internet: logging periods, fixing dates, the calendar, predictions, daily notes, statistics, the widget, and reminders all work offline because there is no account and no MiniCycle server, and the prediction engine (median cycle length from up to 12 records, a 9–14 day luteal phase, fertile window 5 days before ovulation through 1 day after, 29-day default) runs locally.
The one networked piece is Firebase Analytics, which logs anonymous usage events and uploads them later when you are back online; it never blocks a feature and does not carry your cycle data. A connection is only needed to install or update the app from the App Store. Offline use does not change how certain the predictions are, and it is not a substitute for a backup.
MiniCycle is built for a clean iPhone period calendar, local records, simple statistics, and a home screen widget.
View on the App Store