Phasora predicts the next period, the phase you are in and a fertile-window estimate by averaging the dates the user entered — on the device, in plain Dart, with no model involved. Run it twice and you get the same answer, which is why the bundled tests can assert on a prediction.

Demo Instructions — the sign-in screen is a mock and contacts no server, so any credentials are accepted. Use demo@phasora.app / demo1234, or simply tap Sign in with both fields left empty. There is no account to register, no API key to enter and no network required: Demo mode is on out of the box, so every screen — including both AI features — works on the device. Onboarding has a Skip in the corner.
No backend. No Firebase. No real account anywhere. The app ships with ten cycles of sample history, so the first screen you see has something on it, and demo mode pins “today” to that history’s own date — which is why the screenshots, the live preview and the tests all agree with each other.
flutter pub get flutter run
That is the whole setup. The project sits at the root of the archive; there is no wrapper folder to step into.
Two kinds of number, kept apart on purpose. The device works out the next period, the phase, the fertile-window estimate and every statistic. A provider is asked two things only: read a note into tags from a fixed list of twelve, or rewrite those figures as a paragraph. Never a date. Never a diagnosis.

The calendar never draws a guess like a record. A day logged as bleeding is filled; everything else on the month is projected from the user’s own past cycles and drawn differently for exactly that reason. The key sits under the calendar in the app, so a first-time reader never has to guess.

How much do they actually vary? Every row starts on its own day one, so the ragged right-hand edge is the answer — 26 days at the shortest, 32 at the longest, which the app calls somewhat variable. It is the one question a month grid cannot answer, because every month is a different shape.

You write it. It gets tagged. A model may only answer with names from the twelve stamps, the schema says so, and the reply is filtered against the list again when it arrives. Tags are added, never substituted; an empty answer is a correct answer; there is no severity scale and no slider; and it works offline in demo mode.

You can read exactly what gets sent. The top of the screen is what the device computed; the bottom is the same facts, rewritten. In that order on purpose — a screen that led with the prose would be asking you to trust the generated half. The instruction forbids adding a figure, predicting a date or naming a condition, and the disclosure that shows the outgoing text ships in the app rather than behind a debug flag.

Where the entries live: in the phone’s encrypted store — Keychain on iOS, EncryptedSharedPreferences on Android — behind one class you can replace. Take it with you (one button copies every entry out as CSV), destroy it (one button deletes all of it, memory and disk), start from your own dates (three questions replace the sample history), or read what is sent before you send it. No account to create, no health-platform sync, no analytics and no ads.

The rest of it: a day (flow, twelve stamps, a note), set up (three questions, no more), providers (keys, and an editable model name), and Pro (a mock paywall, wired to one flag).

A buildable app, not a mockup — 13 screens in light and dark, 12 symptom stamps on one closed list, 3 AI providers plus a demo mode, 4 dependencies and no vendor SDKs, 105 tests with flutter analyze clean, 18 chapters of offline documentation, and 0 lines of backend to deploy. Figma is not included; every screen is Flutter.

Printed in the app itself, on Settings → How the estimates are worked out, with the numbers read off the engine rather than typed into the copy:
SubscriptionService.purchase() is the one seam to replace, and only the request allowance is wired to the Pro flag — the rest of the feature gating is left to you.pubspec.yaml to configure. Reminders appear inside the app when it is opened.Phasora is for informational purposes only and is not a medical device or a substitute for professional medical advice. Predictions are estimates based on the dates the user enters; they are not a contraceptive method and must not be presented as one. The app scores nothing, assesses nobody and never names a medical condition.
The AI features are produced by a third-party provider the user supplies their own key for. Connecting this template to a live service such as Google Gemini, OpenAI or Anthropic will involve those third-party services, which will incur their own separate costs, not included in the price of this item. Free tiers and prices are set by each vendor and can change without notice. Demo mode makes no network calls.
Questions about setting the template up, connecting a provider or re-skinning it are answered through this item’s comments page. Item support covers this template; it does not cover a provider’s own account, quota or billing, and it is not medical or clinical advice.
v1.0 — first release.
0 average based on 0 ratings.
| Last Update | 2026-09-02 |
| Created | 2026-09-02 |
| Sales | 0 |
| Discussion | Comments |
| Software Version | Flutter 3.x |
| Files Included | Dart YAML JavaScript JSON .kotlin .swift |
| Video Preview Resolution |