29 lines
1.2 KiB
Markdown
29 lines
1.2 KiB
Markdown
# Copy Guide
|
|
|
|
Product goal: **private, mutual-reveal relationship questions with real encryption and calmer UX**.
|
|
|
|
## Voice
|
|
- Warm, calm, and direct.
|
|
- Speak to the couple, not to the implementation.
|
|
- Prefer concrete relationship language over product scaffolding.
|
|
- Keep labels short enough for small Android screens.
|
|
|
|
## Do
|
|
- Say "private answer", "saved reflection", "question pack", and "reveal".
|
|
- Use "mutual reveal" when explaining that both partners answer before seeing each other's response.
|
|
- Use verbs for buttons: "Answer", "Reveal", "Open", "Remove".
|
|
- Let empty states offer a gentle next step.
|
|
- Name emotional intent when it helps: care, honesty, repair, closeness.
|
|
|
|
## Avoid
|
|
- Internal terms such as "local", "preview", "placeholder", "seeded", "database", and "later batch".
|
|
- Roadmap copy inside the app.
|
|
- Overexplaining technical state.
|
|
- Claims about encryption that are stronger than the implemented reveal model.
|
|
- Destructive language as a primary action unless the screen is explicitly confirming deletion.
|
|
|
|
## Examples
|
|
- Instead of "Loading local prompts": "Loading prompts".
|
|
- Instead of "No local answer yet": "No answer yet".
|
|
- Instead of "Partner sync can land here later": "Open a saved answer when you are ready to look at it together."
|