Key takeaways
- 18 August 2026: a clinical safety review package with stable rule IDs, versioned config metadata, environment-aware beta diagnostics, and v1.6 launch-readiness test coverage.
- 19 August 2026: privacy-safe lifecycle metrics, an offline-safe beta feedback queue, an internal founder dashboard, then a migration to a paid Apple Developer account and bundle ID, and Live Activities enabled for production.
- The same day, mommyrefuel.com was reworked end to end: a Trust & Privacy section, copy that honestly describes a built app heading to TestFlight (not a pre-launch waitlist), a complete Ukrainian version of the site, and a real features grid.
- None of this is a claim that the app reached the App Store or public TestFlight at this point — it's the readiness work that had to happen first, documented as it happened.
- This is the last post in the 13–19 August founding week; from here, later posts pick up wherever the next real milestone lands.
Where and when
18 August 2026:
- 08:49 — Clinical safety review package: a stable rule-ID catalog (MR-CRISIS-001 and others) mapped to the safety engine, with a test that forbids drift; an honest 'draft' review status (a test forbids ever claiming clinical review that hasn't happened); the AI safety gate extracted so the crisis-never-reaches-AI contract is directly testable; a docs/clinical-review/ folder reviewable without opening Xcode (8f71c6e)
- 08:49 — Crisis and escalation headlines marked as VoiceOver headers, reachable first via rotor navigation (94f07b5)
- 08:49 — v1.6 launch-readiness test coverage: safety fixtures, AI-gate, metadata, feedback (285a6b7)
- 08:49 — TestFlight launch-readiness docs and a GA release-gate matrix (caa820c)
- 08:49 — An environment model (development/beta/production) so internal diagnostics show correctly in a TestFlight beta without scattered debug flags, plus beta-safe diagnostics and richer feedback categories including a dedicated 'Safety concern' option (2a19e20)
19 August 2026:
- 08:41 — Privacy-safe lifecycle metrics (first use, active days, activation date) that never leave the device, and a closed, value-free set of analytics event names — a structural firewall so the analytics provider can only ever receive a known event case, never arbitrary data (fd22531)
- 08:41 — A beta feedback submission boundary: remote when a feedback endpoint is configured, otherwise a local queue that dedupes and never silently drops feedback; plus a calm, rate-limited weekly-usefulness check-in (995af6d)
- 08:41 — An internal, beta/debug-only founder dashboard (lifecycle, engagement, feedback, platform) and five coherent demo scenarios for testing (6d01522)
- 08:41 — Expanded regression coverage for the above (53430bb), and documentation: beta product metrics, an interview guide, a decision framework, a readiness report (8e62068)
- 11:34 — mommyrefuel.com reworked: a Trust & Privacy section, and copy reframed from a pre-product waitlist to a built app heading to TestFlight (b0274a3)
- 11:47 — A complete Ukrainian version of the site at /uk/, an EN/UK language switcher, and ecosystem messaging updated to reflect what's actually built (Watch, widgets, Health, Siri, Care Circle) (2cd6747)
- 11:56 — Migration to a paid Apple Developer account and a new bundle identifier, com.mommyrefuel.ios (e7202c8)
- 12:22 — Live Activities enabled for production (e1e7920)
- 14:53 — Exempt-encryption declared, so future TestFlight uploads skip the manual export-compliance question (2f6adf9)
- 16:03 — A 'what Mommy Refuel does' features section added to the site, in English and Ukrainian (aaac8fd)
Taking the safety review seriously, in writing
The most important piece of these two days, to me, wasn't a feature at all. It was making Mommy Refuel's safety logic reviewable by someone who isn't a Swift developer. Every crisis-related rule now has a stable ID, mapped one-to-one to what the app's safety engine actually does, with a test that fails if the two ever drift apart. The review status is stored honestly as 'draft' — there's a test that will fail the build if any code ever claims a clinical review took place before it actually has. That's a deliberate choice: I'd rather the code be embarrassingly honest about what hasn't happened yet than quietly imply more confidence than is warranted.
Readiness work, not a launch
I want to be precise here, because this whole changelog is built on being precise: nothing in these two days sent a build to TestFlight or the App Store. What shipped was the infrastructure that makes a responsible launch possible — an environment model so beta testers can see the right diagnostics without a debug-flag mess, a feedback loop that never silently loses what a tester reports (including a dedicated way to flag a safety concern specifically), and privacy-safe metrics that tell me whether the app is actually being used and helpful, without ever collecting anything personal. The migration to a paid developer account and a new bundle identifier (com.mommyrefuel.ios) on 19 August was also purely operational — the free personal account's identifiers had been auto-claimed during device testing and were no longer available, so everything needed a clean, permanent home before a real submission could happen.

Live Activities, switched on for real
The Rest Window / Reset Live Activity had existed in the code since v1.4, but it needed to be explicitly enabled for production use (NSSupportsLiveActivities), which happened at 12:22 on the 19th. Small commit, but it's the kind of detail that decides whether a feature that already works in development actually reaches anyone.
The website finally tells the truth about what exists
Until 19 August, mommyrefuel.com was still speaking the language of a pre-launch waitlist — which had been accurate on day one, but stopped being accurate somewhere around the fourth or fifth feature. That day I reworked it end to end: a new Trust & Privacy section built around four real pillars (private by design, deterministic safety, native to iPhone and Watch, built for real life), copy that now says plainly this is a built app heading to TestFlight rather than an idea collecting emails, and a nine-card features grid describing what actually ships — daily score, personal baseline, today's focus, recovery and safety, ask for help, Refuel AI, maternal timeline, weekly report and doctor visit mode, private journal.
The same day, the site gained a complete Ukrainian translation at /uk/ — every visible string, not a partial pass — with a language switcher and the right hreflang alternates, and the ecosystem section was rewritten to describe the real built surfaces (Apple Watch, widgets, Apple Health, Siri, Care Circle) instead of aspirational ones.

Closing out the founding week
That's thirteen days of history: from a first prototype commit on 13 August to a site that finally described a real, tested, Apple-ecosystem-integrated app heading toward TestFlight on 19 August. I'm writing this changelog so that history stays visible instead of turning into a vague 'we've been building for a while' line later. The app went on to reach a live, free App Store pilot around 12 September 2026 — that's its own post, with its own real dates.

Questions mothers ask
Had the app reached TestFlight by 19 August 2026?
This post covers the readiness work — environment model, safety review package, metrics, feedback loop, the developer-account migration. It documents preparation, not a confirmed TestFlight or App Store submission date.
Was the safety content clinically reviewed by this point?
No. The safety rule catalog and metadata were built to make review possible and to prevent the app from ever falsely claiming a clinical review happened before it does.
Does the founder dashboard collect personal data?
No. It's a beta/debug-only internal view built entirely on the same privacy-safe, value-free lifecycle and engagement metrics used elsewhere in the app — no personal content, no third-party analytics SDK.
Why did the bundle identifier change?
The original identifiers were auto-claimed by a free personal Apple developer account during earlier device testing and became unavailable to the new paid account, so everything moved to com.mommyrefuel.ios for a clean, permanent setup.
Availability can vary with the installed app version. Statuses are founder-confirmed at the time of writing.



