2.1 KiB
2.1 KiB
Future — ideas & improvements backlog
Non-blocking ideas: things that work today but could be better, plus feature ideas. Actual bugs
(broken/incorrect behavior) live in ClaudeReport.md, not here.
QA
Improvement & feature ideas surfaced while QA-testing as a consumer (each works today — none are defects).
- Inclusive sex/gender options in onboarding. Profile step 2 ("What's your sex?") offers only Female / Male, and it drives Desire Sync question tailoring. For a couples app, consider adding a non-binary / "prefer to self-describe" / "prefer not to say" option (with a sensible tailoring fallback). Prompted by: Pass G sign-up flow.
- Home "waiting to play" copy doesn't say whose turn it is. Both partners' Home shows "Your partner is waiting to play" for the same session, so each thinks the other is mid-game. Consider turn-aware copy ("Your turn — finish your part" vs "Waiting on {partner}"). Prompted by: B-002 (resume is fixed; this is the copy nuance).
- Exempt high-value/user-initiated pushes from the promotional rate limit. Game-completion ("results ready") and similar pushes share the same 20/day, 100/week cap as reminders/re-engagement. During normal heavy use a legitimate results-ready push was suppressed. Consider a separate (higher/uncapped) budget for partner-action/results pushes vs promotional reminders. Prompted by: Round 5 E-003 results-ready verification.
- Suppress the redundant "tap to see results" push when the recipient is already on the results screen. When both
partners finish a game at nearly the same time, both are already viewing results yet both still receive the
results-ready push. Mirror the existing chat-message guard (
activeThreadMonitor) for the active game/results screen. Prompted by: Round 5 results-ready test. - Friendlier paywall empty/error state. A-OBS fixed the raw SDK error leak; as a follow-up, when plans genuinely can't load, consider a retry-with-backoff + an offline-aware message, and hide the disabled "Continue" until plans load. Prompted by: A-OBS (env had no RevenueCat sandbox, but the state is worth polishing for real failures).