PregnancyPal

PregnancyPal keeps a record, week by week. That is the plain description of it, and it is first on this page on purpose.

Software in this area slides very easily into sounding like a clinician.

This does not, and the line is drawn in what the application actually does rather than in a disclaimer at the bottom of a screen. It records, and it shows back what it recorded.

Day to day, that is vitals, symptoms and mood.

Around those sit week-by-week pregnancy tracking, appointment management, nutrition and prenatal exercise sections, a community module and a blog. Period and fertility tracking is there as well, covering ovulation, the fertile window and basal body temperature.

Appointments are the part people underestimate. A pregnancy generates a run of them, each with its own date and place and its own reason for being booked. A diary sitting in the same application as the entries is easier to keep straight than one spread across a phone calendar and a paper card.

None of it interprets anything.

The application does not decide whether a reading is expected. It does not identify a symptom, and it does not tell you what any of the numbers mean.

That reading belongs to the person looking after you.

Which is what the export is for. A health report comes out as a PDF, so a record can arrive at an appointment as a document rather than as something recalled in the room, and the charts behind it are drawn with D3.

The architecture is strictly zero-cost.

Logic runs client-side. Firebase's free tier holds the data and uploads go through FilesHub, with no Cloud Functions and no Cloud Storage anywhere in the design.

That constraint has a second effect worth naming.

A product with no server code of its own has fewer places for anybody's records to sit, and on an application holding entries about a pregnancy that is worth more than the money it saves.

Later work hardened the interface rather than lengthening the feature list.

A theme customiser with a full dark mode is available signed in and signed out, and a boot loader removes the flash of the wrong theme before the first paint. Both are small changes, and both matter most on a screen somebody is reading in a dark room.

Build-time prerendering arrived in the same pass.

14 routes and 10 blog posts emit crawler-facing static HTML with per-page JSON-LD, so a search engine or an answer engine reads real content without executing any JavaScript at all.

A page a crawler reads as empty is a page nobody finds.

What it cost is the ability to tell you anything.

An application that interprets is a different product carrying a different set of obligations, and building one would mean making claims this work is not in a position to make. So it stays on the side of the line where it records, and the clinic stays on the other side of it.

That is a limit. It is the correct one here.

It is at pregnancypal.aoneahsan.com, with an Android build on Google Play and documentation at pregnancypal-docs.aoneahsan.com.

There is no iOS build because there is no Apple Developer account behind any of this work, and this page is not going to be the thing that quietly implies otherwise.