· campaign review

For the third trip to wake them.

Mom Alarm Clock’s campaign starts with a familiar morning: another trip to their room, another unanswered text. Review the live beta invitations, upcoming videos and launch plan here.

OCTOBER 1 ANDROID OPT-IN CORRECTION

Verified group-first Android Play opt-in route and corrected owned social copy.

Six owned posts were edited and reloaded with the current Android instructions: r/droidapptesters, r/AndroidAppTesting, r/alphaandbetausers, the Facebook invitation, YouTube post, and Instagram caption. A new corrected X post is pinned, with a reply explaining the Group-page permission message and same-account requirement; the older X post remains historical with its correction reply. Publication and edits do not establish followers, installations, completed tests, GA availability, or paid spend.

iPhone beta: join Mom Alarm Clock on TestFlight. Android: on each Android phone, first join the Mom Alarm Clock beta Google Group, then opt into Play testing with that same account. Phones may use the same Google account or different accounts. “App not available” can reflect missing Group membership or a different selected account. At 05:31 UTC on October 2, Play Console showed 1 tester opted in; that does not prove an installation, working two-phone test, or GA availability. The TikTok card remains unchanged because no authenticated Mom Alarm account edit path was present; its asset wording is retained as a historical description. QA, parity, and future GA live-store/destination proof remain open.

Now

Dated campaign activity

The September 28 approved alarm/reminder PNG is published on Facebook, Instagram and X. The September 30 TikTok card is a distinct asset: its title is “Still waking them up and chasing chores?” and its image shows alarms, reminders, wake-check and sync features with the exact TestFlight and Android Group routes. It has no description/caption because TikTok’s rich-editor text corrupted, so no clickable URL or installation is claimed. TikTok Studio showed Everyone and Pinned, and the public post UI readback and screenshot confirmed publication September 30. Dated publication checks and later caption edits are recorded below; the original approval packets remain unchanged. The September 29, 15:27 UTC read-only monitor observed Facebook 36 followers, Instagram 0, TikTok 1, X 0 and YouTube 0 subscribers. No qualifying milestone or new audience comments across nine monitored posts were found; hidden comments and private messages were outside coverage. These counts do not establish campaign attribution.

UNKNOWNactual spend / exposure
FREE_ONLYno new paid spend authorized
6edited and reloaded Android-corrected owned posts
R2GA family story R2 separately approved; placement remains gated
Approved Mom Alarm Clock iPhone beta invitation: morning alarms and everyday reminders

Live iPhone beta invitation

TestFlight is the current beta destination

Open the Mom Alarm Clock TestFlight join page

Current official API readback — Oct 9, 21:49 UTC: the matched app/bundle has latest non-expired iOS 2.0.1 Build 22 marked 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, feedback enabled and 3 group-linked tester records. Those records are not 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. The public US App Store listing was rechecked on Oct 9 and still showed version 1.0.3; V2 GA is unverified. October 8 historical snapshot: the public link showed 2 of 20; two public-link accounts had build 20 installed, and build 21 was internal/Ready to Submit. These dated observations do not prove current availability or completed paired-phone tests. October 2 historical snapshot: at 04:58 UTC, TestFlight build 2.0.1 (19) had an enabled public link with cap 20 and 3 INSTALLED account records. This does not establish unique families, completed two-phone tests, remaining capacity, or per-social attribution.

October 1 history: the 1 of 20 public-link observation is dated history. 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 showed build 18 offered, the public link/cap 20/feedback enabled, and EMAIL/INSTALLED plus PUBLIC_LINK/INSTALLED each 1. Apple reported 7 public-link views and 3 accepted invitations for Sep 1–Oct 1. Those interval acceptances do not show current installed testers, unique families, completed two-phone tests, or per-social attribution; remaining capacity and individual installed builds are unknown.

Historical Build 18 beta update: testing instructions were corrected and reload verified. Install the latest build offered in TestFlight on both phones and use the two-phone checklist below.

Source: October 1 correction readbacks for the current Android edits and pinned X post; September 30 original-publication observations below are historical context. These post checks do not establish beta joins, follower growth or account-wide comment coverage.

Verified September 28, approximately 18:05–18:14 UTC. Facebook, Instagram and YouTube post text was refreshed, along with those profiles and X’s bio. Instagram’s website leads to the updated beta-first landing page. A September 28, 21:11–21:12 UTC check found zero visible audience comments on five selected posts (one per platform); one TikTok brand comment was excluded. This is not account-wide coverage, and email alert delivery remains untested. These are completed edits, not evidence of follower growth.
Still visible: the original beta artwork remains on the earlier Facebook, Instagram and TikTok posts; the new image was published separately. TikTok’s original caption still contains the old feedback route and unverified QR/reminder/calendar claims; reliable editor persistence is unresolved. At September 28, 23:25:14 UTC, the native TikTok post menu offered no Edit control and the old caption was unchanged. A creator clarification comment with the beta scope and TestFlight feedback steps was published and reload verified. The September 28 pass ending 19:36:43 UTC observed 161 views before that comment, 1 like and 1 saved creator comment; attribution is unknown. The September 28 profile observation showed 1 follower and 0 following; the September 30 native profile readback showed 0 followers. No growth attribution is claimed. No image-replacement control was found in the inspected Instagram or TikTok editors; Facebook exposed photo-edit controls, but replacement was not established. YouTube’s TestFlight profile link is now published, clickable and publicly verified. Advanced description links still require phone verification plus video/ID verification or channel history.
September 28 published captions · historical record

The image’s original GitHub approval binds its original caption and scope. The September 28 text below records Rob’s later direct copy instruction; it does not rewrite those approval receipts or authorize future media.

Facebook and Instagram · verified September 28, 23:10:53 UTC

Still making repeat trips to wake them up?
Still reminding them to take out the trash?

With Mom Alarm Clock, you set your child's alarms and schedule chore reminders from your own phone. Get live alarm and reminder status updates as both phones sync.

Tag a parent or caregiver who could use this.

Try the iPhone beta with two iPhones: https://testflight.apple.com/join/j28Ec4ZB
Already testing? Update in TestFlight first.
Feedback: take an in-app screenshot → Share Beta Feedback.

X · verified September 28, 23:18:58 UTC

Still waking them up? Still chasing chores?
Set your child's alarms and chore reminders from your phone. Get live status updates as their phone syncs.
iPhone beta: https://testflight.apple.com/join/j28Ec4ZB
Update in TestFlight. Screenshot → Share Beta Feedback.

Recorded status updates depend on synchronization; they do not prove physical wakefulness or chore completion. 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 above. YouTube’s new image placement remains unverified. The older posts and their saved captions are retained as dated history.

Earlier saved benefit-first caption · historical post wording

Tired of another trip to wake them? Set their alarm from your iPhone and see the wake-check result on yours.

In the Mom Alarm Clock iPhone beta, the alarm rings on your child’s phone and they complete a wake-up check. You can see whether that check was completed on your phone, without another unanswered “are you up?” text.

We need parents and caregivers with two iPhones to test setup and alarm delivery before launch. Tell us what fails or feels confusing.

Join the iPhone beta: https://testflight.apple.com/join/j28Ec4ZB

Keep your normal backup alarm and use demo child details while testing. Send feedback using the screenshot or TestFlight steps in the testing instructions below.

The benefit wording and TestFlight feedback corrections are saved and verified after reload on Facebook, Instagram and YouTube. The September 28 verification pass ended at 19:04:25 UTC, with Facebook reconfirmed shortly afterward. These checks establish saved text, not audience growth.

What takes more reminders at your house: getting out of bed or starting chores? Tell us what you would want Mom Alarm Clock to get right. If you know a caregiver who could test the iPhone beta, share this invitation with them.

Next

The next work, and who handles it

October 2 status: progress depends on evidence, completed beta tests and the gates below.

Codex · productionTwo exact beta story cuts await owner decisions; adult beta v4 is revision required. No further beta-video production or beta-video spend is planned. Continue GA film work with genuine current-build recordings; before any social publication, complete human listening, motion, word-alignment, runtime and current-build parity checks. Every launch ad must show both alarms AND reminders.
Codex · beta qualityAt 04:58 UTC on October 2, TestFlight build 2.0.1 (19) had an enabled public link with cap 20 and 3 INSTALLED account records. This does not establish unique families, completed two-phone tests, individual installed builds, remaining capacity, or per-social attribution. Collect completed two-phone tests, confusing setup steps and reproducible failures; an installed record alone does not establish reliability. The October 1 observations remain archived above.
Codex · organic distributionFive owned actions are verified: X, Facebook, YouTube, Instagram and TikTok. They establish publication only, not followers, testers, completed tests or paid results. Continue ethical free beta recruitment and feedback monitoring. Android’s current route is Google Group first, then Play opt-in with the same account; at 05:31 UTC on October 2, Play Console showed 1 tester opted in. That does not prove an installation or completed two-phone test. At least 12 testers continuously opted in for 14 days is required for Android production access and remains unmet; it does not gate iPhone GA.
Codex · customer funnelThe customer-page review preview exists. Complete its mobile/release review, full human QA and the longer feature film before treating the shorts → customer page → optional follow/join → feature film path as a finished production funnel.
Codex · launch preparationCheck the live store destination and product claims, assemble final captions and platform previews, and prepare the proposed paid settings. Finished launch videos and the exact paid setup remain subject to Rob’s review before activation.
Two-phone testing checklist · install latest TestFlight build

Use a parent iPhone and a second iPhone for the child side. Keep your normal backup alarm and use demo child details.

  1. Update to the latest available beta in TestFlight on both phones, then pair them. Tell us where setup is confusing or fails.
  2. Create one alarm from the parent phone. Check whether the same alarm and time appear on the child’s phone.
  3. Let the alarm run while the child’s phone is in the state you normally use overnight. Try only the wake-up check offered in this build.
  4. Compare the parent phone’s recorded result with what actually happened on the child phone.
  5. Schedule one chore reminder from the parent phone, such as taking out the trash or walking the dog. Compare its display and recorded status on both phones as they sync. Test any calendar-event flow separately; do not treat an event as a completed chore.

Send screenshot feedback: while using the beta, take a screenshot, open its thumbnail, and finish any Markup with Done. Choose Share Beta Feedback, describe what happened, and tap Submit.

Or use TestFlight: open TestFlight, select Mom Alarm Clock, and tap Send Beta Feedback. Choose Include Screenshot to attach an image or Don’t Include Screenshot to send comments alone, then tap Submit.

For a failure, include the app build, both iPhone models/iOS versions, approximate time and time zone, and the steps that reproduce it. Use demo details and review the screenshot for child names or routines before submitting. We welcome confusing wording and missing-feature feedback as well as bugs.

Feedback steps checked September 28 against Apple’s official TestFlight instructions. Build 14 instructions were submitted in App Store Connect; this checklist is public reference guidance, not a claim of completed tester results.

Why

Start with the prompt parents are tired of repeating.

The strategy begins with repeated room visits, calls to get up, and chore reminders—not a feature list. These are candidate launch angles for review, not replacement posts or product claims.

1

Going back into their room again

Creative evidence: a release-matched parent alarm setup and the child-side wake flow. Claim gate: show only the specific wake-up behavior the current uploaded build and the public release demonstrate. Swipe-proof or lock-screen behavior stays a candidate until exact demonstration; the prior lock-screen Stop re-ring is not shipped.

2

The fourth “are you up?” text

Creative evidence: a real parent-and-child phone sequence and the status recorded on the parent phone. Claim gate: parent-set alarms and recorded status require matching release screens and two-device evidence. A recorded marker cannot prove a child is physically out of bed.

3

Repeating the chore reminder

Creative evidence: a real reminder from parent creation through child marking and parent view. Claim gate: reminders are a distinct candidate flow; show it only if the current uploaded build and the public release prove it. A recorded update is not proof a chore happened.

4

The alarm was swiped; they went back to sleep

Creative evidence: real child-phone alarm and wake-check screens, including the exact swipe or lock-screen path if available. Claim gate: do not promise that an alarm returns after a swipe unless the current uploaded beta build and public release demonstrate it; the earlier lock-screen Stop re-ring is not shipped.

5

At work before they wake up

Creative evidence: a real parent-phone setup and child-phone receipt on two devices. Claim gate: the remote-set flow must work in the current uploaded beta build and public release. Voice, games, points, streaks, bedtime, reminders, and calendar each need separate proof before appearing in public copy.

Published versus draft. Five earlier beta posts remain linked as history, alongside the three new static invitations on Facebook, Instagram and X. Rob has authorized free organic posting. Feature demonstrations still need release-matched evidence; the retained historical ads below are review references and must not be posted as current ads.

BETA REVIEW HISTORY · PENDING CUTS

Two pending review cuts retain iPhone TestFlight and Android Google Group signup wording.

Review the two pending exact files first. Their Android Google Group signup wording is review history, not the current Android route; current Android access is Group first, then Play opt-in with the same account. Android signup in these files is not an Android app install or Play Store route. Adult beta story v4 is rejected and revision required. Rob has stopped further beta-video production and beta-video spend; GA video work continues. Older iPhone-only video assets below in the review history are references only and preserve their recorded approval history.

Beta · Rejected / revision required · AI-generated adult editorial dramatization · about 20 seconds

This is a rejected historical beta asset, not a current recruitment video. It is a story, not an app screen recording or proof a child woke. Its prior iPhone TestFlight and Android Google Group sign-up wording did not provide an Android install link.

Open this exact MP4 · Review this exact file and decision

Rejected and revision required. No further beta-video production or beta-video spend is planned. No current publication, paid activation, Android install claim, GA claim, other cut or future-version approval.

Beta · Pending exact owner review · AI-generated adult editorial dramatization · about 20 seconds

The video now invites iPhone testers to TestFlight and Android testers to the sign-up list. It is a story, not an app screen recording or proof a child woke. iPhone beta: TestFlight (latest build on two iPhones). Android: join the beta sign-up group; the Android install link is not ready. iPhone feedback: in-app screenshot → Done → Share Beta Feedback.

Open this exact MP4 · Review this exact file and proposed scope

Pending owner review only. Future owned organic beta placement needs an exact owner decision, current-build parity, and full-speed listening, motion, caption and word-alignment QA. No current publication, paid activation, Android install claim, GA claim, other cut or future-version approval.

Beta · Pending exact owner review · fictional cartoon editorial dramatization · about 20 seconds

The video now invites iPhone testers to TestFlight and Android testers to the sign-up list. It is a story, not an app screen recording or proof a child woke. iPhone beta: TestFlight (latest build on two iPhones). Android: join the beta sign-up group; the Android install link is not ready. iPhone feedback: in-app screenshot → Done → Share Beta Feedback.

Open this exact MP4 · Review this exact file and proposed scope

Pending owner review only. Future owned organic beta placement needs an exact owner decision, current-build parity, and full-speed listening, motion, caption and word-alignment QA. No current publication, paid activation, Android install claim, GA claim, other cut or future-version approval.

Current wake-check status · placement HOLD. Cartoon beta story cut v2 is rejected reference history and does not request approval. Parent beta, parent GA, beta narration v3, and GA narration v2 have exact chat approvals for their recorded scopes. The older cartoon beta and cartoon GA remain revision history. Human QA and current-build parity remain open; GA also needs verified live iPhone release and destination. Narration approval is for future assembly only; the full feature film is unfinished.
Creative

Current wake-check video decisions

These five editorial cuts describe parent-set alarms, a game, quiz or QR choice that turns off the alarm, everyday reminders, and recorded parent status as phones sync. The 20.375-second parent beta and 40.125-second parent GA cuts have exact chat approvals for future owned organic scopes. The 20.375-second cartoon story cut is rejected reference history and requests no approval; the older 20.375-second beta and 40.125-second cartoon cuts also remain revision history. Approval is separate from human listening, motion, caption and word-alignment QA, current-build parity and actual placement. The videos contain no real app UI or full demonstration; GA also needs verified release and destination.

Beta · Exact chat approval recorded · AI-generated adult dramatization · 20.375 seconds

Parent-set alarms with a choice of game, quiz or QR scan to turn off the alarm; everyday reminders and recorded parent status as both phones sync. Editorial cards, not real app UI or a full product demonstration.

Open this exact MP4 · View exact approval and scope

Approved for this exact future owned organic beta scope only; human listening, motion, caption, word alignment and current-build parity remain before placement. Recorded status does not prove physical wakefulness or chore completion. No paid activation or finished full-demo claim.

Beta · Changes requested by owner · fictional AI-generated cartoon · 20.375 seconds

Parent-set alarms with a choice of game, quiz or QR scan to turn off the alarm; everyday reminders and recorded parent status as both phones sync. Editorial cards, not real app UI or a full product demonstration.

Open this exact MP4 · View requested changes and exact identity

Opening animation does not depict enough action; revise as a fully animated story and obtain fresh exact review. This file is not approved for placement. Recorded status does not prove physical wakefulness or chore completion. No paid activation or finished full-demo claim.

Beta · Rejected reference · fictional cartoon story · 20.375 seconds

Sourced cartoon scene motion with the approved parent beta narration at its original pace, captions and a beta CTA. It is an editorial story, not actual app UI or a full product demonstration.

Play this exact MP4 · Read the revision feedback

Rejected reference: the child is not shown with their own phone or tablet, and the acting does not clearly show the parent’s repeated wake-up burden or how the app solves it. A revised beta asset needs Android sign-up alongside iOS when authorized and verified. No placement, paid activation or finished full-demo claim.

Future GA · Exact chat approval recorded · AI-generated adult dramatization · 40.125 seconds

Parent-set alarms with a choice of game, quiz or QR scan to turn off the alarm; everyday reminders and recorded parent status as both phones sync. Editorial cards, not real app UI or a full product demonstration.

Open this exact MP4 · View exact approval and scope

Approved for this exact future owned organic GA scope only; human QA, current-build parity and verified live iPhone store/destination remain before placement. Recorded status does not prove physical wakefulness or chore completion. No paid activation or finished full-demo claim.

Future GA · Changes requested by owner · fictional AI-generated cartoon · 40.125 seconds

Parent-set alarms with a choice of game, quiz or QR scan to turn off the alarm; everyday reminders and recorded parent status as both phones sync. Editorial cards, not real app UI or a full product demonstration.

Open this exact MP4 · View requested changes and exact identity

Opening animation and voice-over-only treatment need a full animated story; revise and obtain fresh exact review. This file is not approved for placement. Recorded status does not prove physical wakefulness or chore completion. No paid activation or finished full-demo claim.

Reference archive · five superseded combined/status/GA cuts and two alarm-only teasers · revision required

These older files and review receipts remain available as history. Their approvals do not transfer to the four wake-check revisions; none is a current placement candidate.

Historical future-GA parent cut · 38 seconds

Open older parent GA MP4 · Older exact review record. Superseded; review history only.

Historical future-GA cartoon cut · 38 seconds

Open older cartoon GA MP4 · Older exact review record. Superseded; review history only.

Historical parent status cut · 22 seconds

Open older parent status MP4 · Read-only historical approval. Revision required before any new placement.

Historical cartoon status cut · 22 seconds

Open older cartoon status MP4 · Read-only historical approval. Revision required before any new placement.

Historical combined-cut approval

The recorded approval applies only to its exact older asset and scope. The wake-check revision needs separate review.

Historical combined parent cut · 20 seconds

Open older combined MP4 · Read-only historical approval. Revision required before any new placement.

Historical alarm-only parent hook · 13 seconds

Open older narrated parent MP4 · Older review record. Reference only; reminders and exact revised review required.

Historical alarm-only cartoon hook · 12 seconds

Open older narrated cartoon MP4 · Older review record. Reference only; reminders and exact revised review required.

Customer-page review preview. Open the iPhone beta and Android sign-up page with optional social follows and the narrated short previews. This is a review page, not a claim of published customer traffic. The longer feature ad and current-build UI capture remain pending; these shorts are not the full feature ad.
Earlier review archive · 2 music-only cuts + 5 retained sources/drafts
Revision required · earlier music-only comparisons

Earlier caption/music versions retained as references. All earlier single-feature cuts, including the reminder-only archive, require both alarms AND reminders plus exact revised-asset review before launch use. Source files and historical gallery approvals remain intact.

Parent-led hook · 15 seconds

“Another trip to their room?” A fictional AI adult leads into parent-set alarms, a child wake-up check and the result shown to the parent.

Open the parent launch-review MP4

Animated family hook · 13 seconds

“Back at their door. Again.” The fictional cartoon keeps the morning humor, then explains the same alarm, wake-up check and recorded-result flow.

Open the cartoon launch-review MP4

Both creative directions stay in the campaign. The real-life look carries the parent’s frustration and relief; the cartoon is an additional opening to test. “Real-life” here describes fictional photorealistic characters, not filmed customers or testimonials. The existing cuts are preserved below, with their revision needs visible.
Play the new cartoon concept · review only

A 10-second fictional family scene, with audio normalized for playback. It uses softly rendered 3D characters rather than the requested 2D illustration. This is an opening hook, not the full Mom Alarm Clock ad. No social post or paid placement using this cut is approved.

Open the review MP4 directly

Review focus: does the scene capture another trip to wake them, and does the sound feel natural? The requested line was “Third trip. Same blanket.” The file has non-silent audio, but the spoken wording still needs a listening check. The requested one-finger gesture also needs full-motion review.

The cartoon supplies the opening joke. Actual app screens will come from real recordings. No invented child testimonial, simulated app interface or promised wake-up outcome.

Play the clean parent footage · source for the next edit

A five-second fictional photorealistic parent performance from Creatify. This source has no app UI or promotional text. We can reuse the glance and smile with current app recordings, revised copy and natural-speed narration.

Open the clean parent source MP4

Source footage, not a finished advertisement. Original audio and commercial-use clearance remain to be checked before launch use.

1 · Golden Hour whole-family lead · 20 seconds — unrendered

Hook: One family morning, fewer repeated wake-up prompts.

Storyboard: adult morning context → real parent alarm setup → the supported child wake choice → parent sees only the recorded result. A release-matched reminder scheduling → same reminder → recorded update beat is required alongside the alarm. Calendar may be added separately after proof; missing reminder proof holds the whole ad.

Real capture needed: release-matched Golden Hour screens and two-device flow, natural-speed adult voice, rights-cleared sound. The 17.6-second voice source is not a finished mix.

Status: plan only; no playable cut or cleared public asset.

2 · Choose their wake-up check · 23 seconds — unrendered

Hook: Which wake-up check fits your morning?

Storyboard: real parent-side choice picker → one readable supported choice → real child-side action and recorded result → a release-matched parent-set reminder and its recorded update. Both alarms AND reminders are required. Close with the iPhone beta invitation only if the shown behavior is in its uploaded build.

Real capture needed: release-matched picker and two-device result for every choice named. Held quiz modes stay out.

Status: plan only; exact choices and release parity unproved.

3 · Get up and scan · 19 seconds — unrendered

Hook: A wake-up check away from the pillow.

Storyboard: parent chooses the supported QR wake check → physical printed wake code → real iPhone camera scan → genuine matching result → a separately proven parent-set reminder and its recorded update. Both features are required. Close on a verified beta or public iOS destination.

Real capture needed: physical camera and code, a matching release-matched build result, and public release parity. A pairing QR or simulated scan cannot stand in.

Status: plan only; physical scan proof outstanding.

4 · Set it. See the update. · 21 seconds — unrendered

Hook: Tired of repeating the same chore reminder?

Storyboard: parent sets an alarm → supported child wake check and recorded result → parent creates one reminder → child sees and marks that same reminder → parent sees its recorded update. Both features are required. Close with the iPhone beta invitation only if this exact flow is supported there.

Real capture needed: one coherent two-device reminder sequence in a release-matched build and the public release. The recorded update does not prove the chore happened.

Status: plan only; reminder flow and parity need proof.

5 · Your family’s routine · 22 seconds — unrendered

Hook: Mornings have more than one moving part.

Storyboard: real alarm time and days → supported wake choice and recorded result → required parent-set reminder and its recorded update. Calendar is an optional separately proven informational beat, each flow labeled for what it actually does. Close with a verified destination.

Real capture needed: release-matched screens for each distinct flow and two-device evidence where a parent update is shown.

Status: plan only; alarm and reminder runtime proof required; calendar remains separately conditional.

Current creative direction: preserve the fictional photorealistic adult characters and the separately approved cartoon family concept. Use genuine release-matched UI, natural adult narration, plain parent captions and physical QR proof where claimed. No synthetic person is a customer testimonial. Every finished launch ad must include both alarms AND reminders with release-matched proof. Finished ads must exclude retired features, unshipped lock-stop behavior, Android availability promises, rendered prices, rating incentives and invented outcomes.
Media inventory and readiness. The parent beta and GA wake-check cuts plus the two narration tracks have exact chat approvals; the three cartoon cuts are revision references. Approval does not publish media: human listening, motion, caption and runtime parity checks remain open, and future GA placement still needs release and destination proof. Older cuts and source footage remain labeled reference history. The longer genuine-app/calendar feature film remains unfinished and needs current-build footage from an approved capture environment. Paid activation remains on hold. The five numbered cards remain storyboards.
Free

Reach caregivers through useful participation.

The immediate goal is adults who can complete a two-phone beta test and give useful feedback. Followers and views are signals; neither proves an install or a working morning routine.

Make the existing invitation easier to find

The Facebook post remains Featured and the X invitation is now pinned. Instagram’s post menu and Insights → Manage post menu offered no Pin option; its invitation is not pinned. YouTube has verified clickable iPhone TestFlight and Android Google Group signup links. TikTok’s older inaccurate post is Only me; its Sep 30 dual-beta card is public and pinned but lacks a caption and clickable routes; the owned-brand avatar/account is unverified because the current login allows no mutation.

Build a useful listening feed

Five outgoing listening follows/subscriptions were observed earlier. TikTok’s later profile showed 0 following, so that follow is no longer verified as persistent. Read relevant caregiver conversations and prepare helpful, contextual replies for review. Outgoing follows are recorded separately from followers gained. No follow-for-follow, mass tagging or copied promotional replies.

Invite people who have already shown interest

The checked Facebook page/post exposed no eligible-engager invitation control or count. Eligibility remains unknown. Recheck any native Page tool before preparing a reviewed invitation round. Do not import contacts or invite Rob’s personal friends indiscriminately. Availability is account-specific and must be checked in the UI.

Recruit where testing requests belong

The Facebook beta-testing group welcomes developer app testing requests. At 2026-09-28 21:29:21 UTC, native verification confirmed that the approved two-iPhone invitation was published as Mom Alarm Clock. Open the published group post. The post showed no comments; publication alone does not establish tester delivery, beta joins, or follower growth. A separate target, Startup Beta Testers, now has one verified submission awaiting admin approval at September 28, 22:44 UTC. The earlier failed composer was canceled; the later successful submission remains pending, with no public permalink or outcome attribution.

Four Reddit invitations requested adults who can complete a two-phone beta test and report where pairing, alarm delivery, or the recorded status is confusing or fails: r/alphaandbetausers, r/betatests, r/TestFlight, and r/TestMyApp. No attributable beta joins are known.

What is actually done? See the dated free-work ledger. New reach, followers, link clicks and completed tests are recorded only when observed. The first X text post is published and reload verified. At 2026-09-28 21:29:21 UTC, native verification confirmed the approved Facebook community invitation was published; its public permalink is verified. The post showed no comments. No tester delivery, beta join, or follower gain is attributed. X is pinned; YouTube has verified clickable iPhone TestFlight and Android Google Group signup links. TikTok’s older inaccurate post is Only me; its Sep 30 dual-beta card is public and pinned but lacks a caption and clickable routes; the owned-brand avatar/account is unverified because the current login allows no mutation.
Approved community beta invitation · publication verified Sep 28, 21:29:21 UTC

Published destination: Facebook beta-testing group post, as Mom Alarm Clock. This is an approved reference draft, not an exact transcription of the published post. Native publication and permalink were verified Sep 28 at 21:29:21 UTC; the actual publication time is unknown. The post showed no comments. Publication does not establish tester delivery or a beta join.

We’re building Mom Alarm Clock for parents tired of another trip to a child’s room to get them up. In this iPhone beta, the parent sets the alarm on their own phone, it rings on the child’s phone, and the parent can see the recorded wake-up-check result.

We’re looking for adults who can test the two-phone setup and tell us where pairing, alarm delivery or the recorded status is confusing or fails. Use demo child details and keep a backup alarm.

The beta is available now: https://testflight.apple.com/join/j28Ec4ZB

Take a screenshot in the beta and use Share Beta Feedback, or open TestFlight → Mom Alarm Clock → Send Beta Feedback. Add what happened and submit; see the complete steps. What would you want this morning routine to get right?

Work-session routine: campaign operations are scheduled for 09:15, 15:15 and 21:15 local time for routine reply and inbox triage, subject to signed-in access and service availability. Review an approved post’s reach, replies, saves/shares and profile visits after comparable reporting windows. The separate six-hour follower monitor remains read-only; neither routine guarantees instantaneous operation. Copy-to-chat review remains manual: copying does not submit or record a decision.

Source guidance: X’s guidance on genuine participation and followers; Common Sense Media’s official social links. No community affiliation or endorsement is implied.

Organic

Use the live invitation, then answer a real parent question

The current Facebook, Instagram and X alarm/reminder invitations do the beta invitation job. Do not repost them just to fill a calendar.

At 19:17:49 UTC on October 1, Rob approved beta-recruitment-copy-v1 (SHA-256 c6054f2a0e76822d99afd0b9385ca1ee6f6b9a5b9ce25b0b520a1ae7a253fb78) as copy only for future review-gated owned organic beta use. It does not authorize posting, emailing, Play installs or paid activity; Android still needs Rob’s readiness signal and its exact-build two-phone pass, while its verified access route is Google Group first, then Play opt-in with the same account. iOS use needs a fresh TestFlight build, capacity and feedback-path check.

Next: caregiver conversation

Prepared for authorized free organic posting: “Who has to check whether your child’s school-morning alarm was set—you, another caregiver, or the child? What would you want to see on your phone?”

One product-specific question per post. Respond from the account when possible without promising a response time or asking for ratings.

Then: full feature explainer

Held until the iOS integrator supplies uploaded version/build, enabled features, and two-device results, and matched screens exist. Sample angle, only where the shipping build proves it: “Set the alarm from your phone; see the recorded update.” A Tap-Wake quiz or QR angle is conditional on matching release proof. Reminders and calendar stay conditional.

Potential post 1 · The repeated wake-up prompt — draft

Hook: How many times did you ask them to get up this morning?

Visual: parent writing down a morning routine, then the existing beta invitation card; no simulated app screens.

Sample caption: “Still going back to wake them up? Still reminding them about chores? Set their alarm from your iPhone. Schedule chore reminders from your iPhone. Get alarm and reminder status updates as both phones sync. Try the two-iPhone beta, update in TestFlight first, and tell us what happens.”

Status: draft for exact asset and platform review; beta invitation only.

Potential post 2 · Caregiver check-in — draft

Hook: Who checks that tomorrow’s alarm is set?

Visual: text question card or existing beta card, with no feature demonstration.

Sample caption: “Already checking in after you have left for work? Set their alarm from your phone. Schedule reminders for everyday chores. See the alarm and reminder status the app records as both phones sync. Tag a parent or caregiver who could use this. Try the two-iPhone TestFlight beta and keep your usual backup alarm.”

Status: draft for moderation and exact platform review; no outcome claim.

Potential post 3 · Repeating the chore reminder — proof gated

Hook: The third reminder about the same chore.

Visual: one real parent-created reminder, child mark, and parent-recorded update on two devices.

Proof gate: demonstrate that exact reminder flow in the current uploaded build and the public release; match screenshots and destination. Describe a recorded update only, never completion of the chore.

Sample caption: “Another reminder about taking out the trash? Set their morning alarm from your phone. Schedule the chore reminder from your phone. See recorded alarm and reminder updates as both phones sync. Try both routines in the two-iPhone beta and tell us where the flow is confusing.”

Status: sample caption is a draft only; not publish-ready until the exact reminder flow and asset are proved and reviewed.

Potential post 4 · Choosing a wake-up check — proof gated

Hook: What kind of wake-up check fits your family?

Visual: genuine current picker and supported child action, captured from the actual build.

Proof gate: confirm each named choice and result on the current uploaded build and the public release, then write platform-specific copy against those exact screens. Do not imply a check proves a child is out of bed.

Sample caption: “Which wake-up check fits your family? Try the alarm check offered in the current beta. Schedule an everyday chore reminder from your phone too. See recorded alarm and reminder status as both phones sync. Join the two-iPhone beta and update in TestFlight before testing.”

Status: not publish-ready; exact feature claim pending.

Potential post 5 · Setting an alarm before you leave — proof gated

Hook: Already at work before they wake?

Visual: a real parent-phone setup and child-phone receipt for one alarm, with both devices visible.

Proof gate: verify remote creation, delivery, recorded status, and public parity for the exact flow. Separate what the phone recorded from whether the child woke up.

Sample caption: “At work before they wake? Set their alarm from your phone. Schedule reminders for chores such as walking the dog. Get alarm and reminder status updates as both phones sync. Help test the two-iPhone beta and report what the app actually recorded.”

Status: not publish-ready; two-device proof outstanding.

Exact next-post gate. The full feature post is not an approved draft for publication. It needs shipping-build proof, public destination and parity, real screens, an exact caption stripped of conditional text, and Rob’s approval of the finished platform piece.

Prelaunch: prove and review

Confirm release-matched screens, destination, captions, comment handling, campaign links, reporting access, and approval. The X account is verified as @momalarmclock; its first text-only post is published and reload verified. Free organic posting is authorized. Finished launch videos and paid creative still require their separate review.

Day 0: verify public iOS

Confirm the public App Store version, destination, and feature parity before publishing launch work or starting Apple Ads. Record the exact version/build evidence and what remains unverified.

After GA: staged tests

Do not activate paid delivery. Preserve the private R2 preparation proposal ($20 first, $50 only after review, $30 reserve) as planning only; no spend or revenue outcome is implied.

Weekly: decide and iterate

Publish a short report, triage issues, compare one approved experiment at a time, and bring any material spend, targeting, creative, or public-message change to Rob.

Channel-specific management

Apple Ads: search terms, bids, spend, taps, and Apple-reported downloads. Meta: placement delivery, spend, impressions, and clicks. Facebook, Instagram, TikTok, and YouTube: manually check comments, inboxes, saves/shares, and recurring questions. The verified X profile is a fifth organic channel with its first published post: keep its bio and destination consistent, use release-matched screenshots, short caregiver questions or answers, and manual replies.

Facebook first among social channels

Pew’s 2025 U.S. adult survey reports Facebook use at 71% and X at 21%. That supports Facebook as the first social-community priority and Meta as the first social-ad candidate. Apple Ads remains the first proposed paid acquisition test. X deserves an approved organic presence, not equal initial spend; population reach is not evidence of Mom Alarm conversion.

X link measurement

Prepare an X-specific tracked link after destination and measurement checks. It can show visits or link clicks; it does not establish downloads, activation, or revenue. Keep those fields unknown unless the distinct Apple campaign-link or product evidence supports them.

Problem-first message angles

Lead with the repeated morning wake-up prompt or repeated chore reminder, then show only the release-proven action and recorded update. Do not turn swipe-proof, voice, points, streaks, games, bedtime, notifications, quiz/QR, reminders, or calendar into a public claim until the current uploaded beta build and public release demonstrate the exact behavior.

Paid

FREE_ONLY: no new paid activation or spend is authorized. Spend, revenue, balance, expiry, taxes and fees remain UNKNOWN unless source-backed.

September 30 paid preflight: Brand Page AdCenter was verified. The only available ad account displayed was Rob Wamsley. Billing linkage, account currency, native spending limits and Instagram Business Suite connection remain unverified. No ad or paid campaign was activated.
Current paid status: HOLD

Original Apple $100 promotional application confirmed; current native balance, expiry, cash exposure and fees/taxes are unverified. Private R2 preparation proposes $20 first, $50 only after review, and $30 reserve; it is not activation authority.

Historical staging — superseded by FREE_ONLY; no spending authorization
StageConditionEnvelope
Initial delivery and reporting checksHistorical proposal, superseded by FREE_ONLY. No funded experiments are authorized.No current authorization
One controlled comparisonHistorical inactive stage. Superseded by FREE_ONLY; no amount is released or releasable.Historical $100 more
ReserveHistorical inactive stage. Superseded by FREE_ONLY; no reserve is current or releasable.Historical $350
TikTok / Google / YouTube / X paidHistorical inactive stage. FREE_ONLY is current; actual spend and exposure are UNKNOWN.No authorization

Native controls must contain spending if the operator is offline. Apple daily budgets are averages and can be exceeded on an individual day. Verify account currency/time zone, end date and an eligible budget order or another documented native limit; retain headroom for reporting/billing lag and applicable taxes/fees. Keep activation blocked if aggregate containment cannot be demonstrated.

Full operating plan: Launch plan and daily operations covers prelaunch, GA day, five owned channels, daily checks, weekly decisions and the reconciliation ledger. Apple Search Results uses approved App Store product-page assets, not uploaded social MP4s.

Codex manages approved tests

Once approved tests are active, Codex checks actual source reports, pauses broken tests, and adjusts approved creative, search terms and placements within released channel and total caps. Record each change and its evidence window; small samples do not prove winners.

New unapproved creative, platforms, increased limits or changed activation scope require review. No live ad API, automatic optimizer or conversion feed is claimed. The two parent wake-check cuts have exact chat approvals for future owned organic scopes; the three cartoon cuts require revision and fresh exact review. Human listening, motion, caption and runtime checks remain pending. The older combined parent cut is reference history. The longer genuine-app/calendar feature film remains unfinished.

Measurement before interpretation

Separate Apple Ads new downloads/redownloads, campaign-link first-time downloads, Meta clicks, organic reach and product setup. Only report attribution when the actual source and reporting window support it. Not Enough Data or missing reports mean unknown, not zero.

Context, not an ad forecast

App Store Connect showed 229 first-time downloads and 12.4K impressions over Jun 29–Sep 26. Those are historical listing observations, not a new-release forecast or proof that ads will work.

Record each platform, campaign and reporting period separately
RecordRequired fields
Source and limitsPlatform/campaign IDs, creative version, report period, account time zone, source/pull time, attribution window, currency, released stage and native limits/end date.
Spend reconciliationReported accrued spend versus billed/settled charges; applicable fees/taxes; refunds/credits and status; additional pending exposure; cumulative reconciled exposure and remaining released allowance, without double counting.
Outcomes and decisionsSource-reported delivery, new downloads/redownloads, setup, trials, paid conversions, revenue and refunds only when available; sample size, unknowns, prior/new settings, reason and follow-up date.
Ledger math. Available room is released allowance less reconciled charged/accrued exposure and additional pending exposure or fee headroom, avoiding overlap. Preserve the unreleased reserve. Cost per new download requires nonzero attributable downloads from the same source/window; paid-customer cost and return on ad spend require measured attributable conversions/revenue. Overlapping platform attribution is not unique customers. No profitable-scaling claim when downstream data is unavailable.
Learn

A weekly loop that listens before it scales

The campaign should produce a short decision report, not a pile of platform numbers.

Each week

  • Collect App Store Connect, Apple Ads, TestFlight beta feedback, and manually checked native comments/inboxes. TestFlight feedback is a separate queue from social comments; continue manual checks until a controlled alert-and-inbox test succeeds for each platform.
  • Log the ledger with source and freshness. Separate platform delivery, App Store clicks, reported new downloads, campaign-link observations, setup/activation evidence, and complaints.
  • Triage store-path, setup, reliability, privacy, and misleading-claim issues first; record owner, severity, evidence, and resolution before repeating related creative. Do not solicit or reward ratings or stars.

Provisional decision rules

  • Pause or fix if the public store path breaks, delivery is wrong, feedback identifies a misleading claim, a reliability/setup issue appears, or reported acquisition cost worsens for two comparable checks without a credible explanation.
  • Continue the cap only while the ledger is complete enough to interpret and no material issue is open. Test one documented variable at a time: search theme, creative, placement, or landing route.
  • Manage routine adjustments within approved channel and total caps, using comparable spend, source-reported downloads and paid conversions when available. Codex reports the evidence and decisions to Rob; budget increases, new unapproved creatives and new platforms require approval. These are provisional learning criteria, not performance promises.
For authorized free organic postsFree organic posting, including X, is approved. Keep beta invitations accurate; feature demonstrations need matching uploaded-build proof and current screens. Retained historical ads remain review-only.
Before a videoRob approves the exact cut after rights, release parity, captions, final audio, screen proof, destination, and platform presentation review.
Before initial paid activationVerify the new store release and feature parity, material setup issues, exact reviewed creative, destination, account currency/time zone, end dates, native limits and reporting. FREE_ONLY remains in force. Any future paid campaign requires a new explicit decision for its exact scope, cap, dates and cash exposure; passing readiness checks does not authorize spending.
Historical staged-spend noteSuperseded by FREE_ONLY. No additional stage or reserve is current, released, or releasable.
Before any increaseRob reviews the weekly report and verified acquisition/activation evidence; no automatic budget increase.