Brand and support foundation
Omnisant's public experience was refined around the core philosophy of reducing fragmentation across modern life.
What changed
- Refined public website language around calm systems for complex lives.
- Added the Why page to explain the problem Omnisant was built to solve.
- Added support resources for quick start, calendar sync, permissions, mobile use, troubleshooting, operating habits, and release notes.
- Improved product screenshots with more realistic household coordination examples.
- Strengthened privacy, permissions, and shared-context language.
Why it matters
The product experience now better reflects the real problem Omnisant is designed around: fragmented information, repeated questions, duplicated effort, and disconnected household context.
Future format
Clear updates. No developer noise.
Month / dateRelease titleShort summaryWhat changedWhy it matters
Release notes should stay calm, concise, and useful. They should not include commit hashes, internal issue IDs, or hype language.