Home / Product / Consumer App

Affirmology End-User App, v1 Spec (player-first)

Updated Jun 20, 2026 · Affirmology_EndUserApp_v1_Spec_v1.md

Affirmology End-User App, v1 Spec (player-first)

Jeff's seed, 2026-06-20: the end-user app's audios should keep playing when the user leaves the app, should loop/repeat, and should be a full player. "I need to get the Apple subscription to build that part." This spec starts v1, led by the player (the heart of the experience), with the platform decision that makes it possible.

What v1 is (the minimal lovable version)

A member receives their personalized Sacred Audios and listens to them in a premium, looping, background-capable player. Strip everything else away and v1 must do three things beautifully: deliver your audio, play it like a real player (loop, background, lock screen), and hold your growing library. Everything richer (the full Hermes companion, EFT and other modalities, the Living Profile) layers on after.

The player (the heart of v1)

• LOOP / REPEAT: single-track repeat, and repeat-all for a playlist. The whole point of an identity audio is repetition, so this is core, not a nice-to-have.
• BACKGROUND PLAYBACK: keeps playing when the user switches apps or locks the screen. Essential for a morning walk, a gym session, a sleep install. This is the capability the PWA cannot give and the native app can.
• LOCK SCREEN + CONTROL CENTER + AIRPODS controls: play/pause/scrub from the lock screen, Control Center, and Bluetooth/AirPods (native MPNowPlayingInfo + remote command center).
• FULL PLAYER UI: large play/pause, a scrubber, a prominent LOOP toggle, the audio's title and a cosmic cover, and a calm visual that fits the brand.
• SLEEP TIMER: fade out after N minutes, for the before-bed audios.
• DOWNLOAD / OFFLINE: cache the audio so it plays without a connection (v1 or fast-follow).

Platform decision (and why the Apple subscription is the gate)

• A PWA cannot do background audio, screen-off looping, or lock-screen controls on iOS. Apple restricts it. So v1 must be a NATIVE app on iOS.
• CLEANEST PATH: CAPACITOR. Wrap the existing web app in a native shell and add a native audio plugin for background playback, lock-screen controls, and looping. This reuses the web UI we already have (this is queue item C13) rather than rebuilding from scratch, and the SAME build also ships to Android.
• REQUIRES: the APPLE DEVELOPER PROGRAM (about $99/year, confirm current price) to build, test on device via TestFlight, and publish to the App Store. Android adds a one-time Google Play fee (about $25). So: getting the Apple Developer Program is the unblocking action for this whole track.

Core v1 features beyond the player

• ONBOARDING + CHART INTAKE: birth data in, the first Sacred Audio generated.
• THE LIBRARY: the member's audios (their suite), each playable in the player, each with its PDF report.
• RECEIVING NEW AUDIOS: new audios (Casts / Structures) arrive in the library, with a notification.
• ACCOUNT + TIER: sign-in, the tier the member is on (Structures vs the golden companion), and credits balance (even if credit purchase is v1.1).

Out of scope for v1 (capture, build later)

• The full Hermes command-center chat in-app (can be a lighter "request an audio" in v1, full companion later).
• EFT tapping and other modalities beyond the first set.
• The Living Profile depth, the Wisdom Circle direct-contact, the social/sharing features.

Build path

1. Get the Apple Developer Program (Jeff's action, the gate).
2. Wrap the existing web app in Capacitor; add a native audio plugin (background mode + lock-screen controls + loop). Decide which plugin (e.g., a Capacitor media/background-audio plugin) during the build.
3. Build the full player UI (loop toggle, scrubber, sleep timer) over that native audio layer.
4. The library + onboarding reuse the existing web app and the cloud content pipeline.
5. TestFlight for on-device testing, then App Store (and Google Play from the same Capacitor build).

Open questions to lock before building

• v1 scope: player + library only, or also in-app audio creation (Cast)? Recommend player + library first; creation can be "request and it arrives."
• Are tiers/credits in v1, or does v1 ship to you, Sol, and a small beta with everything unlocked?
• The player's visual design (we can prototype a few directions).

Near-term workaround (so you can loop today)

Until the native player exists, you can loop an exported mp3 by importing it into a player app that supports repeat (Apple Music with Repeat One after adding the file to your library, or a third-party audio looper app). Not elegant, but it gets you the on-repeat listening now while the real player is built.

Next action

Get the Apple Developer Program, that unblocks the whole track. In parallel, I can spec the player UI in detail and the Capacitor audio approach, and we lock the v1 scope questions above. Tell me when you want to go deeper on any piece.