The app is built. This portal is the operating plan for standing up a low-cost proof-of-concept, letting testers click through the UI while the app-store accounts register, and running a controlled family pilot — with a live view of what it costs.
Four moving parts run in parallel. The key insight: UI testing does not wait for app registration or the backend. Testers hit a password-protected web build in a browser on day one, while the slower tracks (Apple/Google accounts, keys, backend) catch up.
Phased checklist: front-end-first UI testing, demo backend, app-store registration, closed pilot, public launch. The master TODO.
→Where to run the POC, why Global Accelerator waits, and the AWS vs. Azure-credits play — with a running cost table.
→Whom we pilot to, the "Family Connector" seed strategy, UI-flow test scripts, and feedback capture.
→Memberships, keys, the permanent bundle-ID brand lock, and the revalidation rules that decide what you must freeze first.
Because this whole site sits behind Cloudflare Access, it can safely carry the confidential material — the running app build and the full architecture / flow-diagram set — that never goes on a public page.
The mobile Ionic/Angular app built for the browser — click through onboarding, family, feed, capsule and Sage flows. UI shell: live data needs the demo backend (Roadmap P3); until then API-backed screens will show empty/error states.
↗The full internal diagram set — data model, auth, capsules, Transcend/Sage, video pipeline, communities, trust model, monetization, financials, and more (Mermaid, dark theme).
The bundle ID com.mifamilias.app is permanent — APNS and Firebase keys bind to it, and the native projects hard-code it. Changing the display name or logo later costs one review cycle; changing the bundle ID means a brand-new app with no users, ratings, or history to migrate. Lock name + bundle ID + logo before generating signing/push assets. See Apple & Play registration.
Deploy the web build to Cloudflare Pages behind Access. Testers click through flows in a browser. Register Apple/Google accounts in parallel.
Stand up the AWS demo box, wire the app to it, push builds to TestFlight / Play internal testing. Seed demo data.
Recruit 2–3 "Family Connector" households. Structured UI feedback, then store review + launch.
Portal + running web app build + full architecture doc set deployed to mifamilias-devsite.pages.dev, gated by Cloudflare Access (email PIN).
Roadmap, hosting/cost model, and pilot plan captured. Pricing verified against public AWS / Apple / Microsoft pages (July 2026).
Confirm final display name, bundle ID, and logo. Blocks signing/push asset generation.
MiFamilias Developer Portal · pricing captured July 2026, reconfirm before spend