73 lines
3.2 KiB
Markdown
73 lines
3.2 KiB
Markdown
# Closer visual identity
|
|
|
|
Closer should feel private, warm, and made for an equal partnership—not clinical, gamified, or like
|
|
a public dating profile.
|
|
|
|
Product goal: **private, mutual-reveal relationship questions with real encryption and calmer UX**.
|
|
Visual decisions should reinforce that promise before decoration, novelty, or growth mechanics.
|
|
|
|
For the full working asset set, including illustration, notification, store, and logo-export
|
|
requirements, see `docs/brand/asset-system.md`.
|
|
|
|
## Brand mark
|
|
|
|
The mark is one heart formed by two equal halves. Pink and lavender represent two people meeting at
|
|
the center; neither side visually dominates. Keep the mark intact and do not separate, rotate, add
|
|
text inside, or place it directly over a busy image.
|
|
|
|
- Launcher source: `docs/store/sources/app-icon.svg`
|
|
- Android adaptive layers: `app/src/main/res/drawable/ic_launcher_*`
|
|
- Minimum clear space: one quarter of the mark's width on all sides.
|
|
- Minimum digital size: 24 px. At small sizes, use the solid monochrome mark.
|
|
|
|
## Core colors
|
|
|
|
| Role | Color | Hex |
|
|
| --- | --- | --- |
|
|
| Trust / deep background | Aubergine | `#24122F` |
|
|
| Primary brand | Deep purple | `#56306F` |
|
|
| Connection accent | Lavender | `#B98AF4` |
|
|
| Partner one | Soft pink | `#F7C8E4` |
|
|
| Partner two | Soft lavender | `#D9B8FF` |
|
|
| Warm light surface | Blush white | `#FFF8FC` |
|
|
|
|
Use the deep tones for trust and privacy, and the softer tones for connection and warmth. Product
|
|
text must continue using semantic Material theme colors so contrast remains correct in light and dark
|
|
mode.
|
|
|
|
## Store voice
|
|
|
|
- Primary promise: **A private space for two.**
|
|
- Supporting idea: **Private by design · Made for connection.**
|
|
- Feature graphic support line: **Daily questions, private reveals, and gentle ways to reconnect.**
|
|
- Prefer calm, specific language. Avoid promises to “fix” a relationship, competitive streak copy,
|
|
urgency, or public/social framing.
|
|
|
|
## Rotating privacy messages
|
|
|
|
Approved production rotation:
|
|
|
|
- **Your relationship is yours, not ours.**
|
|
- **Answer honestly. Reveal intentionally.**
|
|
- **For conversations that belong to the two of you.**
|
|
- **No audience. No public feed. Just the two of you.**
|
|
- **Private by design.**
|
|
- **A private space for two.**
|
|
- **Not even Closer can read your answers.**
|
|
- **End to end encrypted private responses.**
|
|
- **Built for trust, not tracking.**
|
|
|
|
All legacy couples have been migrated to encryption version 2. Answer-bearing writes fail closed
|
|
when the couple key is unavailable. These claims describe deployed behavior.
|
|
|
|
## Asset rules
|
|
|
|
- Store graphics and screenshots should use the same purple/pink palette as the product.
|
|
- Lead with privacy and mutual connection before feature volume.
|
|
- The Play feature graphic should show the heart mark, the primary promise, and compact product cues
|
|
for private reveals, two-person use, and daily rituals. Do not turn it into a feature checklist.
|
|
- Do not show intimate answer content, real email addresses, invite codes, or notification tokens.
|
|
- Use clean demo data and crop out development indicators before publishing.
|
|
- Re-export `docs/store/app-icon-512.png` and `docs/store/feature-graphic-1024x500.png` from the
|
|
SVG sources after any mark, palette, or store-copy change.
|