null
/
Closer
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs(date-memories): add date reflections requirement to iOS parity plan

This commit is contained in:
null 2026-06-30 18:15:15 -05:00
parent a90809bd40
commit 8d563d4fd4
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ClaudeiOSPlan.md
View File

@ -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