Partner activity feed

Summary

Each partner sees a curated feed of the other's public actions — reads, listens, watches, shared entries, milestones logged, cycle status. Private data (mood logs, private journal entries, AI chats) is never surfaced.

Why it matters

Feeling connected is the whole point of couples-first — but pushing everything creates surveillance dynamics. A partner activity feed gives shared presence without shared surveillance. It's also a retention mechanic: seeing Rahul finished an audio card makes Priya more likely to open the app.

Standard couples-connectivity patterns (Life360-style location, calendar sharing) are too heavy for this context. Read receipts alone are too light. A feed of learning + journaling activity is the right shape.

Implications

• Public actions shown in the feed:
  • Cards read (with duration)
  • Audio + video listened/watched (with completion state)
  • Shared journal entries written
  • Milestones logged
  • Cycle status (fertile / period / predicted period — not the specific day of log)
• Private actions NEVER shown:
  • Private journal entries
  • Mood + sleep logs (except aggregated in weekly report)
  • Symptom logs
  • AI chat questions
  • Bookmarks
• Reactions are lightweight: "Listen too", "Read", "React" — no comments (see ai-not-community).
• Feed is a home strip + a full screen (surface-mobile-home-partner-activity).
• Notification cadence: 1 push/day max for partner activity; the daily rollup is a soft ping ("Rahul finished 2 things today").
• Sensitive stages: during postpartum, the feed becomes gentler — hides "sleep hours" comparisons that could trigger guilt.

Related

• couples-first
• ai-not-community — reactions, not comments
• household-as-billing-unit
• surface-mobile-home-partner-activity
• surface-mobile-home-shared — strip surface

Sources

• Design principle
• Feedback pass: 2026-07-27 UX simplification