Mobile-first creation and secure open flow
The product already has concrete depth in secret creation, share flows, browser viewing, and local decrypt behavior across five secret types.
Roadmap
A direction page based on the current codebase, not invented product mythology.
The present system already shows where Anomonus is strongest: mobile secret creation, browser reveal flows, and deeper security controls around transport, identity, and device state.
Viewer clarity and legal transparency
The public website should explain the viewer-first web model, the legal boundaries, and the real security architecture with less guesswork.
Transport, device, and lifecycle controls
Current architecture direction clearly emphasizes device binding, Tor, pinning, lifecycle enforcement, and secure deletion paths as differentiators.
Focus tracks
The areas where the current product story is strongest and most concrete.
Secret workflow coverage
Keep the product centered on its implemented create, share, open, RSVP, and steganography flows rather than vague platform language.
Security posture communication
Make the public site accurately describe ticketing, local decrypt, secure storage, Tor, device binding, and browser limitations.
Operational trust surfaces
Use legal, transparency, and architecture pages to show where the current system is strong and where boundaries still matter.
Stay aligned
Keep the website aligned to the real app and viewer stack.
The more the public site reflects the actual mobile, viewer, and security architecture, the stronger the Anomonus brand becomes.