Created July 29, 2026 · Version 1.0

From working foundation to both app stores.

The complete execution plan for Remii: a real multi-device household operating system, every prototype feature implemented, Firebase authorization enforced, the Remii assistant operating across household data, subscriptions live, and production releases available on iOS and Android.

Identity: com.krampus.remii Stack: Expo 57 · React Native · Firebase Owner: Dave / Krampus Limited Design: supplied prototype, no deviation

One month gets the family pilot—not the entire production vision.

The aggressive path below reaches a real mixed-device pilot at the end of Week 4, feature-complete code around Week 10, and store deployment around Week 12 plus external review time. No tile counts as complete until it is real, synced, authorized, and tested.

Week 4Family pilot

Week 10Feature freeze

Week 12+Store release

Delivery principles

These rules keep the broad product coherent without turning the build into two native apps or a pile of disconnected demos.

01 · Product

Broad, thin, and real

Holisticness is the product. Every domain participates in one household, one permission model, one timeline, and one assistant—but depth lands in ordered phases.

02 · Engineering

One cross-platform codebase

Expo and React Native serve both platforms. Native modules appear only for concrete needs such as notifications, camera, files, calendar access, and location.

03 · Trust

The backend is the boundary

Client-side Kid Mode is presentation. Firebase Auth, Firestore Rules, callable Functions, and Storage Rules enforce household and role permissions.

04 · Identity

Parent acts; child is effective

Parents stay signed in as themselves while acting as a child. Sensitive records retain both actor UID and effective member attribution.

05 · Delivery

Commit verified increments

Each vertical slice follows test → implementation → focused verification → commit. Production identity and secrets stay Dave-owned from day one.

06 · Completion

No fake feature completion

A screen is complete only when create/read/update/delete, sync, empty/error/offline states, permissions, and device verification all work.

Target architecture

Small enough to build quickly, with privileged operations kept off the mobile client.

Expo mobile appiOS + Android · one codebase

→

Firebase AuthParent + child email/password

→

Firestore + StorageHousehold records and files

↔

Callable FunctionsChild identity, AI, billing webhooks

Security RulesDefault deny · household membership

FCM / NotificationsRequests, chores, events, reminders

AI providerServer-side tools · confirmations

RevenueCatHousehold subscription entitlement

Execution phases

Ordered by dependency. Checkboxes are saved to the shared backend and drive the progress meter for everyone.

CompleteNextLaterRelease gate

Current baseline

The verified foundation already in the repository.

CompleteJuly 29

OutcomeA real Expo 57 app that visually matches the approved prototype and compiles for both platforms.

EvidenceESLint, TypeScript, Expo Doctor, iOS simulator, Android/iOS bundles, browser interaction checks.

Register Remii in the Developer portfolio and preserve its independent Git history.Alex

Create Expo SDK 57 + TypeScript foundation in ~/Developer/remii.Build

Preserve the supplied prototype under raw/prototype-web/ as immutable reference.Build

Reproduce Remii visual language: Nunito, purple/cream palette, cards, mascot, tabs, holiday background.Build

Build working Home, Calendar, Grocery, Chores, and More surfaces with local interactions.Build

Prove parent-to-child switching with persistent Kid Mode labeling and child request behavior.Build

Select Firebase and app identity: com.krampus.remii.Alex

Inspect Silver Spoon read-only for Dave-owned Expo, Firebase, EAS, and secret-boundary patterns.Build

Production identity & Firebase foundation

Separate Dave-owned cloud and store identity before product data exists.

Week 1Critical path

Exit gateBoth dev builds boot against a separate Remii Firebase project with emulator-backed rules tests and no private key in the mobile bundle.

Commit rhythmIdentity → Firebase client → emulator/rules → EAS profiles → CI, each as a verified commit.

Household identity, roles & child accounts

The security model every later feature depends on.

Backend smoke completePhysical-device matrix deferred

Exit gateMom, Dad, and one child sign in separately; parents invite/manage; cross-household access fails; act-as-child retains actor attribution.

Primary filessrc/auth/, src/household/, functions/src/auth/, Firestore Rules and emulator tests.

Shared data shell, realtime sync & offline behavior

One pattern for every household domain.

Implementation completeDevice UI matrix deferred

Exit gateA mutation on one phone appears on another, survives restart, handles offline/retry, and never crosses households.

Data postureTyped repositories, server timestamps, bounded listeners, explicit loading/empty/error/offline states.

Daily-use core & Week-4 family pilot

The first genuinely useful connected household loop.

Local + simulator implementation complete; human/physical pilot deferred to final validationFeature complete

Final validation (deferred)Real mixed-device pilot with family on physical phones (sign-in, core flows, notifications). This is moved to the very end of the plan and is NOT required to complete feature development in Phase 4–7.

BuildsInvite-only TestFlight + internal Android builds can be produced for simulator + limited testing; full physical pilot is end-of-plan work.

Holistic household feature breadth

Turn every approved prototype tile into real household CRUD.

Week 5–6Feature breadth

Feature gateEvery non-sensitive prototype domain is implemented, synced, role-aware, searchable, and represented in Home/Remii (local + simulator). Human/physical device proof for these domains is deferred to final validation at the end of the plan — it is NOT a gate for completing feature development.

Scope ruleSimple complete workflows first; no dead tiles and no speculative deep integrations.

Documents, medical & emergency mode

The highest privacy and irreversible-action risk in the product.

Week 7Security gate

Feature gatePrivate records are least-privilege, storage paths are protected, deletion/export works (local + simulator), and medical copy makes no diagnostic claim. Full physical export/deletion and real-device hostile testing is deferred to final validation at the end of the plan.

Required reviewPrivacy/data inventory, child access, retention, incident response, store disclosures, and legal review before public launch (not required to finish feature development in Phase 7).

Native integrations & device capabilities

Add concrete integrations after the internal data model works.

COMPLETE — engineering-owned slices (simulator + local gates)Physical proof deferred to final validation

Feature gateEvery requested permission is triggered by an explicit user action in code, denial is handled gracefully in the app (survivable), and both platforms have equivalent core behavior in the implemented code paths. t0701 (background handler) + t0702 (explicit device calendar export) complete with RED-GREEN tests + simulator exports. All other native + full permission matrix deferred to final validation. Phase 7 engineering boundary reached.

Native ruleUse Expo modules first; add custom Swift/Kotlin only for a demonstrated unsupported requirement. Device permission proof runs once at the very end.

Meaty Remii assistant

The cross-domain experience that makes holisticness useful.

Engineering vertical completePhase 8

Exit gateRemii answers from authorized household data, performs structured actions, confirms sensitive changes, and cannot cross household boundaries.

ArchitectureCallable Function → server-side tool registry → Firestore/Functions. No model key or broad Admin capability in mobile.

Subscriptions & household entitlement

One paid household, both platforms, pricing still Dave's decision.

Week 9–10Revenue

Exit gateSandbox purchases, restore, renewal, cancellation/refund, family account switching, and entitlement enforcement work on both stores.

DecisionDave approves products, price, trial, free behavior, and household entitlement owner before store setup.

Decide monthly/annual pricing, trial, free limits, household member limit, and launch offer.Dave

Create Dave-owned RevenueCat project and separate iOS/Android apps for com.krampus.remii.Alex

Create App Store and Play subscription products, entitlement, offering, and localized display details.Alex

Install RevenueCat SDK with public platform keys; map entitlement to the household owner, not arbitrary child profiles.Build

Build Plans screen exactly in Remii's design with real localized offerings, purchase, restore, manage, legal links, and errors.Build

Create RevenueCat webhook Function with signature verification, idempotency, and household entitlement projection.Build

Define grace period, billing issue, expiration, refund, owner change, and deleted-account behavior.Build

Test purchase/restore on StoreKit sandbox and Google license test, including app reinstall and parent account switching.Build

Confirm children cannot purchase, change plan, or expose billing details unless explicitly allowed by a parent flow.Build

Quality, privacy, compliance & operations

Convert a feature-complete build into something safe to release publicly.

Week 10–11Code freeze

Exit gateAll critical journeys pass on store-like builds, policies match code, Firebase recovery is rehearsed, and no release-blocking defect remains.

Testing ladderUnit → component → Rules/Functions emulator → Maestro device → EAS build → pilot → store review.

TestFlight, Play testing & store submission

Production assets, review evidence, staged rollout, and live verification.

Week 11–12+External review

Exit gateApple status is Ready for Sale and Google production release is available to intended countries, with live install/purchase/sync verified.

Schedule riskStore review and any required Google closed-test duration are external critical-path time; start them as early as policy permits.

Launch stabilization & client handoff

Production is complete only when it can be operated and recovered.

First 30 daysOperate

Exit gateDave owns every account, runbooks are current, support has no launch-blocking pattern, and one restore/hotfix path has been exercised.

OwnershipNo Alex/Bear-owned production dependency unless Dave explicitly approves and it is documented.

Monitor daily for launch week, then weekly: crashes, auth failures, denied writes, Functions errors, AI failures/cost, notifications, and purchases.Alex

Triage pilot/production feedback by blocked journey, data risk, billing, privacy, or polish; commit fixes in small verified increments.Build

Verify Firebase billing, budgets, backups, IAM, Secret Manager, EAS, stores, RevenueCat, AI, domain, and support all remain Dave-owned.Alex + Dave

Rotate any credential exposed during setup using additive swap → verify → revoke; never break live clients.Alex

Run one production hotfix drill and one Firestore/Storage recovery drill using non-sensitive test data.Build

Deliver source, architecture, data model, deployment, secrets, store, support, recovery, and release documentation to Dave.Build

Close launch only after both stores are live, the family pilot remains healthy, and the 100% definition below is satisfied.Gate

No tasks match this filter.

Complete 21-screen inventory

The prototype route map is the contractual feature inventory. “Real” means backend CRUD, permissions, sync, states, tests, and device verification.

#	Screen	Production behavior	Primary data	Native / external dependency	Target
1	HomeCurrent shell exists	Live household summary, schedule, requests, chores, notices, announcements	Cross-domain projections	Push deep links	Week 4
2	CalendarCurrent shell exists	Internal events, recurrence, assignment, reminders, conflicts, filters	events	Optional device calendar	Week 4
3	GroceryCurrent local interaction	Realtime list, categories, quantities, favorites, history, child requests	groceryItems, groceryRequests	Barcode scan, push	Week 4
4	ChoresCurrent local interaction	Recurring assignments, proof, approvals, rewards, wallet ledger	chores, completions, walletEntries	Camera, push	Week 4
5	MoreCurrent tile index	Role-filtered navigation and accurate live status for every module	Cross-domain counts	None	Week 4–7
6	Family	Household roster, invitations, roles, important dates, removal	members, invitations	Share links	Week 2–4
7	Member	Profile, permissions, credentials, preferences, Kid Mode context	members	Photo picker	Week 2–4
8	School Hub	Schools, teachers, classes, assignments, activities, files, reminders	schoolItems	Files, calendar, push	Week 5
9	Document Vault	Secure upload, categories, preview, expiration, access, deletion	documents + Storage	Camera, files	Week 7
10	Home Maintenance	Assets, recurring service, warranty, contacts, costs, history	homeAssets, maintenanceTasks	Camera, push	Week 5
11	Vehicles	Profiles, registration, insurance, mileage, service and reminders	vehicles, vehicleServices	Camera, push	Week 5
12	Bills & Expenses	Recurring bills, due/paid state, month view, owner, reminders	bills	Push	Week 5–6
13	Subscriptions	Household services, renewal, price, cancellation notes, alerts	householdSubscriptions	Push	Week 6
14	Medical Center	Member-scoped organizational records, providers, appointments, files	medicalRecords + Storage	Files, calendar, push	Week 7
15	Pet Center	Profiles, care, medications, appointments, supplies, records	pets, petCare	Camera, calendar, push	Week 6
16	Vacation Planner	Trips, itinerary, bookings, packing, files, travelers, countdowns	trips, tripItems	Files, calendar, location	Week 6
17	Gift Planner	Private ideas, occasions, budgets, purchase/wrap state	gifts	Share sheet optional	Week 6
18	Family Timeline	Memories, photos, dates, people, captions, visibility	memories + Storage	Camera, media library	Week 6
19	Emergency Mode	Selected contacts/info, offline availability, explicit activation	emergencyProfile	Phone, maps, offline cache	Week 7
20	Plans	Real products, household entitlement, purchase, restore, manage	entitlements	RevenueCat, stores	Week 9–10
21	Chat	Authorized cross-domain answers and structured actions with confirmation	authorized domain reads, AI receipts	AI Functions	Week 8–9

What “100% feature complete” means

This is the finish line—not “all screens render.”

Product completeness

All 21 prototype routes exist in the native app and preserve approved design/behavior.
Every advertised action is real; no dead tiles, fake sync, or demo-only success.
Home and Remii unify the entire household rather than acting as isolated apps.
Mom, Dad, and child can complete intended journeys on their own devices.

Identity & authorization

Separate email/password identities with parent-managed child credentials.
Household and role authorization enforced in Rules/Functions—not only UI.
Parent act-as-child is clearly labeled and keeps actor/effective attribution.
Cross-household access is denied and emulator-tested for every collection.

Data & reliability

Realtime multi-device updates, offline behavior, retries, and rollback are tested.
Uploads and sensitive records follow least privilege, retention, export, and deletion.
Firebase config, indexes, rules, functions, secrets, budgets, backup, and recovery are documented.
No private credential ships in the app or repository.

AI & billing

Remii reads only authorized data and uses server-side structured tools.
Sensitive AI actions require confirmation and produce audit receipts.
Subscriptions purchase, restore, renew, expire, refund, and switch accounts correctly.
Children cannot access billing or parent-only data through UI, API, or AI.

Quality & compliance

Lint, strict TypeScript, tests, Rules/Functions emulator, Expo Doctor, and EAS builds pass.
Critical Maestro journeys pass on iOS and Android store-like builds.
Privacy policy, terms, deletion, child-data handling, medical positioning, Apple labels, and Google Data Safety match the code.
Accessibility and low-end Android performance meet release criteria.

Deployment & ownership

Apple App Store status is Ready for Sale and Google production release is available.
Fresh live-store installs pass auth, sync, notifications, files, AI, and purchase smoke tests.
Dave owns Apple, Google, Firebase, EAS, RevenueCat, AI, domain, support, and billing.
Release tag, build evidence, hotfix, rollback, recovery, and support runbooks are delivered.

Critical-path risk register

These can move the store date even when code is progressing normally.

Store timingGoogle may require a closed-test period; Apple/Google reviews are external.Open listings and start eligible testing early; do not wait for code freeze.

Child privacyChild accounts, location, documents, medical, and AI create policy/legal obligations.Minimize data, parent-control access, complete counsel/policy review before public submission.

Auth modelParent-created child credentials cannot safely use only the client SDK.Use Callable Functions/Admin SDK with parent membership checks and emulator tests.

Medical/docsSensitive data increases impact of rules, retention, deletion, and disclosure errors.Treat Phase 6 as a security gate; no “safe” medical claims or broad file access.

Feature breadthTwenty-one screens can devolve into disconnected or fake workflows.Use one shared household model and repositories; complete vertical slices before adding depth.

AI actionsPrompt injection or weak authorization could expose or mutate household data.Authorize every server-side tool, confirm sensitive actions, bound logs/cost, adversarially test.

Native configBundle IDs, EAS identity, certificates, Firebase apps, and native files can drift.App config is source of truth; clean prebuild/EAS builds and device smoke prove release identity.

One-month promiseTrying to call the whole vision production-complete in four weeks creates unsafe shortcuts.Ship a real family pilot in Week 4; preserve the aggressive Week-10 feature freeze and Week-12 store path.

Dave’s issue reports

Upload a screenshot (or GIF ≤5 MB). The site will classify it against the live plan.

Report an issue

For Dave only. Screenshot or short video (export video as GIF < 5 MB). The AI will try to link it to an existing unfinished plan task or flag it as new scope.