What a menstrual app is actually for
When someone looks for a menstrual app, they are usually looking for a period app. Not a printed grid with a red pen. Not a lecture on the pill. They want a place on the phone that answers a short question: is bleeding likely soon, given the cycles I have actually had?
Cycle apps accumulate features because contraception, fertility, and pregnancy sit next to menstruation in real life. The home screen still has to do the original work. If it cannot say, from your own dates, when the next bleed is likely, the rest of the product is decoration.
Lua is an iOS cycle and contraception app built around that first job. It estimates. It does not know the exact day. It is not a contraceptive and has no contraceptive effect.
What the app is actually computing
A menstrual app is not a clock. It is a running summary of bleeds you logged, turned into a guess about the next one.
You mark the days you bled. The app measures the gaps between those starts and places a window on the calendar: bleeding is more likely here than there. Close cycle lengths should tighten the window. Scattered lengths should widen it. An honest app shows that uncertainty instead of pretending it has a secret sensor.
The loop does not need a clinic or a cloud model. It needs dates you trust, and enough of them that a pattern can appear. One cycle is a data point. Several cycles are a distribution. The app is useful when it treats that distribution as the thing you came for.
People still want a day. Plans prefer a date. The trade-off is that a date is a point estimate of a noisy process. Average cycle length is not a law. Stress, illness, travel, a new method, and the years around menarche or perimenopause all move the interval. An app that “knows exactly” is selling a feeling. An app that estimates from your history is doing the work.
Lua follows the second path. You log. It updates the picture. If your last few cycles were longer, the next estimate should move with them.
Menstrual calendar
A static menstrual calendar is a different object: months, weeks, empty squares. You mark the days you bled, and you may count forward twenty-eight squares because that is the number everyone remembers. The calendar does not change its mind when your last three cycles were thirty-two days. It has no memory unless you give it one with a pen.
Paper is enough if all you need is a record. The gap is prediction. A printed calendar cannot recompute. It cannot show a range that grows when your intervals scatter, or sit next to a patch reminder and a pregnancy week view without becoming a pile of systems.
An app earns its keep only if it is a living calendar: the same squares, but the likely window comes from your starts, not a textbook 28. If the digital version still draws a red dot on a fixed day regardless of what you logged, it is a prettier paper calendar. Lua’s calendar is meant to be the living one. It is still a calendar, not a diagnosis. The highlight for “likely” should move when the history moves.
One home screen, several lives
Contraception, trying to conceive, and pregnancy are not the same job as “is it coming.” Putting them in one app helps when you do not want three copies of the same dates. A bleed logged on the pill is still a bleed if you later stop. A pregnancy week count still needs the last period start. Shared history is why a combined app is not automatically a mess.
It becomes a mess when the home screen forgets the first question. If you have to tap through fertility scores and a feed before you see the next likely bleed, the product has optimized for everything except the search that got people there. Method reminders, fertile-window estimates, and pregnancy tracking can live in the same app. They should stay secondary until you ask for them.
Lua puts cycle, contraception, trying to conceive, and pregnancy in one iOS app for that reason: one set of dates, several ways of looking at them. The test is still the home screen. If it cannot answer whether bleeding is likely, the combination failed. Reminders for a pill, patch, ring, or shot do not make the app a contraceptive. They are clocks. The method does the preventing. Lua does not.
What an estimate is allowed to say
A menstrual app should be allowed to say “around then,” and required not to say “on that morning.” Given the starts you logged, bleeding has usually begun in this span of days. Hide the span behind a single confident day, or drown it in content, and the original job is gone.
Cycles change when life does. Starting or stopping a method, lactation, and illness are ordinary reasons the next interval will not match the last average. New logs should matter; old averages should fade. Irregular, here, often means the model has less to go on, not that you failed at menstruation.
Lua will be wrong about the exact day. So will every other estimator built from past bleeds. The useful product stays close enough, and lets you see why the window sits where it sits: these logged starts, not a promise of precision.
Period dates are easy to type and expensive to regret. Lua keeps health logs on the device. There is no account, and there are no Lua servers holding those logs. That is a design choice, not the thesis of this post. The longer version of no-account design is here. How that compares with other trackers is a separate page.
Lua is not a contraceptive. It has no contraceptive effect. It is not medical advice, and it does not replace a clinician. If bleeding is suddenly very different, or missing when you expected it, that is a body question, not an app question.
If you want a period app that estimates from your own cycles, keeps the calendar honest, and still has room for contraception and pregnancy without making those the first sentence, Lua: Period & Birth Control is on the App Store.
More from the blog
One app for your cycle, contraception, fertility and pregnancy.
Private, flexible and designed to adapt with you.