From 8d563d4fd4d20740a1c09a390b80516b105b8108 Mon Sep 17 00:00:00 2001 From: null Date: Tue, 30 Jun 2026 18:15:15 -0500 Subject: [PATCH] docs(date-memories): add date reflections requirement to iOS parity plan --- ClaudeiOSPlan.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/ClaudeiOSPlan.md b/ClaudeiOSPlan.md index 26ecd180..5adae0cf 100644 --- a/ClaudeiOSPlan.md +++ b/ClaudeiOSPlan.md @@ -67,6 +67,11 @@ Implement byte-compatible Swift crypto for every Android wire format: read (tolerant of legacy plaintext; show a 🔒 placeholder when the key is missing) — mirror Android's `FirestoreUserDataSource` chokepoint + the pairing/legacy **migration** and **unpair-revert**. Until this ships, iOS shows the locked placeholder for name/gender (acceptable in dev; **not** for release). +- **⛔ Date reflections (REQUIRED before iOS launch — R22).** The new Date Memories & Replay feature adds an E2EE + `couples/{id}/date_reflections/{dateId}/answers/{uid}` collection with the same couple-key + read-gated + `secure/payload` reveal as the daily question (`date_history` is plaintext). iOS must implement the matching + reflection write/decrypt/reveal (mirror `FirestoreDateReflectionDataSource`) and the `date_reflection_*` / + `date_logged` notification types; until then iOS can't participate in date reflections. ### 2.4 Screens & features to parity (~48 + new messaging) All routes from the refreshed audit's screen map, **including the NEW Messages experience** (inbox + conversation