Tracking the beta, day by day.

Historical Android closed-beta readback — Oct 9, 18:10 UTC. Play closed Alpha 2.0.1 version code 9 is available to selected testers with 2 closed opt-ins. Production is inactive; its gate requires 12 testers opted in continuously for 14 days and is incomplete. A separate native Group read at 21:12 UTC found 4 members; Group membership is not installs, Play opt-ins, families or paired testers. Current tester capacity, installs, paired-phone tests and incoming feedback count are UNKNOWN. On each Android phone, first join the Group, then opt into Play testing with that phone’s selected Play Store account. Send private feedback to momalarmclock@gmail.com. Alarms and reminders, and phone-reported parent status, require current-build proof; they do not guarantee waking or chore completion.

Historical iPhone TestFlight metadata readback — Oct 10, 14:09:16–22 UTC. Official App Store Connect API fields verify the app and bundle match, and latest non-expired iOS 2.0.1 Build 23 is VALID and IN_BETA_TESTING internally. The selected enabled external public group is configured for external testing; its latest known active iOS 2.0.1 Build 20 is VALID and IN_BETA_TESTING externally. Its public link has an enabled configured limit of 20 and feedback enabled; it has 3 group-linked tester records. Those records do not establish public-link usage, remaining slots, installs, families, active users or completed paired-phone tests. These fields do not prove universal phone eligibility, downloads, current installation, updates or paired-phone behavior. Feedback is enabled, its configured address is not disclosed, and new feedback plus reporter or device evidence are unverified. App Store Connect team identity remains UNKNOWN. The public US App Store listing was rechecked on Oct 9 and still showed version 1.0.3; V2 GA is unverified.

Historical Android readback — Oct 8, 14:33 UTC. Alpha 7 / 2.0.1 was available with 2 closed opt-ins and the Group had 4 members; neither measure established installs, families, or paired-phone tests. The Oct 9 Alpha 9 readback supersedes that earlier current status.

OCT 1 HISTORY / OCT 2 PLAY READBACK

Dated beta-route observations; outcomes still unmeasured.

At 00:56 UTC, iPhone build 2.0.1 (18) was in external Testing and the public TestFlight join showed 1 of 20 joins. This is a historical point-in-time participation observation, not a completed two-phone test, growth result, or GA release. At 18:08 UTC, an App Store Connect upload-date inventory found build 2.0.1 (18) latest uploaded. At 18:23:19 UTC, its group readback found build 18 offered; the public link, 20-person cap and feedback were enabled, with builds (17), (15) and (14) also associated. Tester-count categories EMAIL/INSTALLED and PUBLIC_LINK/INSTALLED were each 1. Apple’s public-link metric for Sep 1–Oct 1 reported 7 views and 3 accepted invitations. These interval acceptances are not current installed testers, unique families, completed two-phone tests, or per-social attribution; remaining capacity and individual installed builds remain unknown. At 02:47 UTC, the Android beta Google Group had one member (the owner), zero pending members or messages, and zero unread conversations. At 08:47 UTC, Play Console showed closed testing Alpha 2.0.1 (code 6) available to selected testers through the configured group, with zero opted-in testers. That zero is historical: at 01:22:49 UTC on Oct 2, the Play dashboard for com.momclock.momalarmclock showed 1 currently opted-in tester. Production is inactive, and 1 opt-in does not establish an installation, two-phone use, or 12 concurrent opted-in testers for 14 days.

The new dual-beta signup page gives the exact iPhone TestFlight and Android Google Group routes. On each Android phone, join the Group and then opt into Play testing with that phone’s selected Play Store account; Group membership and Play opt-in remain separate. At about 01:44 UTC, the older Sep 28 TikTok post moved from Everyone to Only me because its caption was outdated. The newer Sep 30 dual-beta card remains public and pinned; it has no description, so its printed routes are not claimed clickable. This privacy correction preserves historical observations and implies no reach, follower or join change.

Historical earlier-October-1 review record, superseded by the later addendum below: an existing Facebook beta post was refreshed with both routes and the full alarms, reminders, wake-check and sync explanation; no boost was enabled. At that earlier checkpoint, the three-video owner-review queue listed adult beta story v4, cartoon beta v4, and brown-father beta story v3. This historical queue does not state the current decision.

At about 03:00 UTC, the original blue-yellow YouTube avatar was published and retained after reload. The channel profile also has clickable iPhone TestFlight and Android Google Group signup links; the Google Group is the first Android step and Play opt-in follows. Three July Shorts whose retired picture or pattern descriptions were not audited for current parity were changed to Unlisted at 02:38 UTC, removing them from channel discovery; old direct links may still be available. Current-build genuine app capture remains blocked: no installed app or Build 18 metadata was found in the named simulators, and guarded build permission is pending. These observations claim no viewing, subscriber, join, feature, GA-live, Android-install, or paid-spend outcome.

At about 09:37 UTC on Oct 1, the official US App Store product page still showed version 1.0.3 and “Version 2 is coming soon”; iOS 2.x GA is therefore not verified live. This public-store readback is separate from the historical TestFlight observation above. The earlier Chrome App Store Connect browser session redirected with authResult=FAILED; the later limited read-only App Store Connect API beta-group readback at 18:23:19 UTC established the dated beta-group fields above, not complete TestFlight UI access or an available-slot count.

Capture-status addendum — Oct 1, about 15:45–15:47 UTC: the public US App Store listing readback today still showed 1.0.3. Build 18 physical-device (iphoneos) IPA and source exist, but no qualifying Build 18 simulator app or complete current-build RC1–RC4 two-phone capture has been verified. The selected Xcode 27 guarded fresh build did not run: direct preflight observations showed memory free at about 49% with pressure level 2, below the runner’s required 50% and level 1; resolver write confinement also remains unverified. No GA or Android-install claim is made.

Later October 1 addendum — at 19:51 UTC, the Android Google Group showed one member (owner only) and zero pending members: zero external Android signups were confirmed then. The verified u/momalarmclock Reddit post is Google Group sign-up only; it does not provide a Play install/opt-in route or attribute an acquired tester. The Reddit profile has Android and iPhone beta links and displayed 0 followers at its initial observation; that is a baseline, not growth. Adult beta story v4 is rejected and revision required. Rob’s current priority is no further beta-video production or beta-video spend; GA video work continues. The later Oct 2 review readback supersedes that historical queue: the three exact beta-video items are revision_required; ios-ga-listing-v2 is wording-only approved. Neither status authorizes placement.

OCT 1 / ANDROID OPT-IN CORRECTION

Current Android route corrected; outcomes still unknown.

Six owned posts were edited and reloaded with group-first Android Play instructions: r/droidapptesters, r/AndroidAppTesting, r/alphaandbetausers, the Facebook invitation, YouTube post, and Instagram caption. The new corrected X post is pinned with a group-warning reply; the older X post remains historical with its correction reply. The Facebook Beta Test Apps post was edited and reloaded. Startup Beta Testers was edited and reloaded but remains pending admin review, so it is not public. TikTok remains unchanged because no authenticated Mom Alarm account edit path was present. These actions do not establish a follower, install, opt-in, tester, completed-test, GA, or paid-spend result.

iPhone beta: direct TestFlight join. Android: first join the Mom Alarm Clock beta Google Group, then opt into Play testing with the same Google account on each phone. Skipping the Group can show “App not available.” The observed invitation does not prove a completed opt-in, installed build, working two-phone test, or GA availability. The unchanged TikTok card’s printed routes remain an asset description only; it has no description/caption, so clickable routes or installations are not claimed.

Current published image posts and captions

The unchanged approved alarm/reminder PNG is live on Facebook (22:54 UTC), Instagram (23:01 UTC) and X (23:18:58 UTC), September 28. These are saved native publication checks, not attribution or proof of completed beta tests.

Facebook/Instagram current captions were edited in place and verified at 23:10:53 UTC; no comments were visible then. X’s new caption was verified at 23:18:58 UTC; 0 replies, reposts, likes and followers were observed then. Both current versions describe alarms, chore reminders and status updates as the phones sync. Read the exact current captions.

The later text follows Rob’s direct instruction. The original GitHub-bound caption, asset hash, scope and receipt remain historical approval evidence. Current copy is not misrepresented as that original packet. Earlier TikTok photo: photo published; CTA correction not complete. Its intended caption is missing and the inspected native menus offered no Edit control. This historical placement does not describe the new September 30 TikTok card. YouTube’s new image placement remains unverified.

October 2 review history · October 10 approval addendum

Recorded chat approvals: parent beta, parent GA, beta narration v3, and GA narration v2. Cartoon beta, cartoon GA, and the cartoon beta story cut are historical revision references; the story cut is rejected and requests no approval. The three exact beta cuts — adult beta story v4, cartoon beta v4, and brown-father beta story v3 — are revision required. Adult beta story v4 is a rejected reference; cartoon beta v4 and brown-father beta story v3 are internally superseded. These superseded or revision-required versions need no further decision; any changed cut needs a new exact review. Full-speed human AV QA, parity and GA release/destination proof remain open; approval does not publish media. The exact R2 illustrated lifestyle film and seven captions are owner approved on October 10 for their existing conditional future owned organic iPhone scope; unchanged approved files need no repeat creative approval. They have not been published as a campaign, and owner live cue, public US V2 Store/destination proof, final paired physical-phone parity, full human A/V/caption QA, native identity/rules/disclosure preflight, FREE_ONLY, and Facebook/YouTube holds remain. Future, materially revised, or full-demo media require separate exact review. The review desk’s feedback workflow requires Rob to paste text into chat and cannot submit or authorize action. The full genuine app demo remains incomplete awaiting Spark physical capture.

GA film capture · October 1 visual QA

Build 18 simulator UI tests passed, but the resulting single-device frames and showcase recording contain no-child-phone or this-phone-rings warnings, and some frames show test controls. Those assets are held out of advertising. A paired parent/child capture, genuine game or quiz or QR footage, matching reminder status, human audio/caption review, and an exact finished-film owner review remain open. No full GA film is claimed ready for placement.

Owned profile branding and routes · October 1 readback

YouTube’s blue/yellow avatar is published and its public channel profile has clickable iPhone TestFlight and Android Google Group signup links. Facebook’s Page has the blue/yellow avatar, updated bio and clickable dual-beta link. Instagram has the blue/yellow avatar and updated bio; the corrected caption on the existing beta post is verified, while that post’s attached image remains the older pink artwork. X has the blue/yellow avatar, updated bio, and dual-beta website link; the current dual-beta invitation is pinned, and its t.co routes resolved to the intended pages with HTTP 200. These are owned-profile and link checks only: no follower, click, conversion, tester, or paid-spend result is claimed.

TikTok remains open: its public profile still shows the older pink avatar and one follower. The owned TikTok login was unavailable in Chrome, so no profile mutation was made. The public September 30 dual-beta card remains pinned, but it has no description/caption; printed routes are not claimed clickable.

Facebook community invitations · October 1 readback

The existing Beta Test Apps invitation was edited in place and reload verified with alarms, reminders, parent-selected wake checks, sync-qualified status, the TestFlight feedback route, and the group-first Android Play opt-in route. No comments were visible at the check and no tester attribution is established.

The existing Startup Beta Testers invitation was similarly edited and reload verified, but remains one post pending admin approval; no public outcome is established. Neither update is a new post or proof of recruitment.

Reddit beta invitations · October 1 readback

The public r/alphaandbetausers and r/betatests invitations are verified iPhone two-phone TestFlight routes with feedback, describing alarms and chore reminders plus the wake check. The public r/TestFlight invitation was observed at about 10:27 UTC with iOS flair and a Brand Affiliate label; it had 0 comments at the initial baseline, with no attributable joins. The public r/TestMyApp invitation was verified as a public post by u/Prize_Arachnid_1908 with iOS flair and a Brand Affiliate label; it covers the two-phone alarm/wake check and reminder and requests TestFlight feedback. The account was logged in during inspection, but it is a nonbrand/personal account and Mom Alarm ownership was not verified. That earlier October 1 account-access observation is superseded. The current official u/momalarmclock posts are r/droidapptesters, r/AndroidAppTesting, and r/alphaandbetausers; all three were edited and reloaded with group-first instructions: join the Google Group, then opt into Play testing with the same account. Earlier same-day signup-only observations are historical and do not describe the current post copy. The observed invitation does not prove a completed opt-in, installed build, working two-phone test, or GA availability. One visible r/betatests audience comment reported a possible delayed parent alarm status after a child quiz; it was acknowledged and privately sent for engineering triage, not reproduced or confirmed. A separate r/alphaandbetausers audience comment asked about the physical wake QR and two-phone setup; the posting account replied with the QR distinction and invited feedback. This is audience interest, not a tested, installed, or converted participant. Both comment-alert emails were confirmed in Sent. An earlier status listed the four legacy Reddit posts for public-comment monitoring. The private comment-state ledger now records baselines for seven posts, including three official Android posts; registration does not prove subsequent monitor execution or alert delivery. First signed-in author-insights snapshot at 2026-10-01 11:29 UTC: r/TestMyApp 26 post views, r/TestFlight 73, r/betatests 31, and r/alphaandbetausers 131, for 261 post views total. At about 14:00 UTC, the r/TestFlight live page showed 170 post views and zero comments; this later observation is separate from the 11:29 snapshot and does not establish any causal change. These views can include repeated viewers and are not unique people, TestFlight joins, clicks, downloads, completed tests, or source attribution; joins remain unknown. Future read failures are unknown, not zero.

Third official Android invitation · October 1 correction readback

u/momalarmclock edited and reloaded the r/alphaandbetausers post on October 1. Its current instructions are to join the Google Group, then opt into Play testing with the same account. The observed invitation does not prove a completed opt-in, installed build, or working two-phone test. The initial readback found zero comments, with no proven joins or installs.

October 1, about 22:40 UTC recruitment measurement: native Reddit displayed 99, 27 and 26 views respectively for the official r/droidapptesters, r/AndroidAppTesting and r/alphaandbetausers posts; no human replies were visible (automated moderation only). At 22:36 UTC, the Group owner view showed 2 total members and 0 pending: one owner and one additional account of unknown origin, so no organic attribution. At about 22:40 UTC, Play Console showed 1 tester currently opted in and the requirement of 12 continuously opted-in testers for 14 days. At about 22:45 UTC, native u/momalarmclock UI showed “Comment posted successfully” and the public permalink for a permitted one-comment invitation in r/parenting_tech’s August/September showcase, which explicitly invited self-made parenting apps, platforms, links and feedback and had new October 1 comments: open the public comment. No views, replies, clicks or testers are claimed from that comment. These later observations do not reinterpret earlier dated Group or Play zero counts, establish unique viewers or tester attribution, or prove an install or two-phone test.

October 1, about 23:10 UTC recruitment follow-up: native Reddit displayed 101, 29 and 28 views respectively for the same official r/droidapptesters, r/AndroidAppTesting and r/alphaandbetausers posts. No human replies were visible: AutoModerator only on the first two and no replies on the third. The Group showed 2 total members and 0 pending; Play Console showed 1 tester currently opted in and the 12-continuously-opted-in-testers-for-14-days rule. The official Reddit profile was corrected with Google Group first and Play testing second links. The new Google Group onboarding post was verified as a group conversation, with no reply at readback. Rob reported that a nonmember Google account saw “App not available”; a second account that joined saw “Become a tester.” Based on Rob’s comparison, this is evidence that closed-beta opt-in is available to a joined account; actual install and two-phone behavior remain unverified. An attempted r/AndroidClosedTesting post was immediately removed by Reddit filters; no public reach is established. This later point-in-time snapshot does not revise the historical 22:40 UTC values, establish unique views, caused testers, installs, a successful two-phone test, or Group message email delivery.

Android closed-test and community readback · October 2

Play closed testing Alpha 2.0.1 (code 6) was available to selected US testers; the configured Google Group and web opt-in/feedback route were confirmed. This dated readback showed 1 opted-in account and the Group at 2 members / 0 pending. Those counts are not installations, families, or a completed two-phone test. The Startup Beta Testers invitation remains pending admin review. A new owned invitation in public Android ALPHA/BETA Testers was reload verified. Its rules welcome beta apps and require a build number, which the post includes; no comments were visible at the initial readback. No reach, conversion, or tester outcome is attributable.

Remaining work · October 1 superseded historical queue

At that October 1 checkpoint: adult beta story v4 was revision required; cartoon beta v4 and brown-father beta story v3 awaited exact owner review; and human listening, motion, caption and word-alignment QA plus current-build parity remained for the two exact approved parent cuts. The cartoon beta references are historical and have no current beta-revision or beta-production action. GA cartoon work, future-GA public release and destination proof, and current-build footage, runtime proof, assembly and fresh review for the longer GA film remain. No further beta-video production or beta-video spend is planned. The two approved narration tracks cover voice and wording only. Beta feedback and public comments require continued triage. The second Facebook community invitation and Indie App Catalog directory submission await moderation. TikTok’s older caption remains unresolved. Paid activation remains inactive. An earlier Oct 1 UI observation showed 1 of 20 public-link places, 2 campaign-group testers, and build 2.0.1 (18) Testing in the group and installed by the public-link tester; it does not prove a completed two-phone test or acquisition growth. The 2026-10-01 18:08 UTC upload-date inventory found build 2.0.1 (18) latest uploaded. The separate 18:23:19 UTC group readback found build 18 offered, the link/cap 20/feedback enabled, and one PUBLIC_LINK/INSTALLED plus one EMAIL/INSTALLED record; Sep 1–Oct 1 public-link reporting showed 7 views and 3 accepted invitations. These interval counts do not establish current installed testers, unique households, individual installed builds, remaining capacity, completed tests or per-social attribution. A separate per-build filter found one 2.0.1 (18) screenshot-feedback submission, privately triaged as a UX-state clarity concern; engineering reproduction remains pending.

Next distribution step

Do not publish another near-duplicate owned X post until there is a distinct angle or actual new product proof; focus on permitted beta communities and replies. The approved community beta invitation was confirmed published in the Facebook beta-testing group at 21:29:21 UTC; open the verified permalink. No comments were visible and no tester delivery or beta joins are attributed. The second target, Startup Beta Testers, now has one submitted invitation awaiting admin approval at Sep 28, 22:44 UTC; no public permalink, reach or tester acquisition is established. The earlier failed composer was canceled before this separate successful retry. TikTok’s creator clarification was published on the Sep 28 post, now Only me; no DM was sent.

One public child-privacy discussion was inspected for listening; it was not treated as customer feedback or a place to force promotion. The owned beta posts had no comments at inspection.

Comment handling

Keep criticism and bug reports visible. Answer a relevant concern once with useful information. Distinguish persistent abuse, spam, scams, threats, or exposed personal information from disagreement. Queue hide, delete, or block decisions for Rob. Do not offer review incentives. Do not publish child names, schedules, or raw private comments here.