Why we changed our onboarding story.
We were explaining more features when what people needed was a clearer view of how their own context becomes useful.
The problem was not a missing tour.
Our earlier onboarding tried to explain Notes, Books, Pages, actions, and sharing as separate features. Each part was understandable on its own, but the complete product felt broader instead of clearer.
Memova only makes sense when those parts stay connected. A conversation can become a Note, the Note can deepen a living Book, and that Book can produce a Page or prepare the next action without losing where the idea came from.
We now begin with one transformation.
The new story starts with context a person chooses to keep: a conversation, note, file, meeting, or experience. Memova organizes it into a Book that grows over time, then helps turn that context into something reviewable and useful.
- Capture the context that matters.
- Connect it inside a living Book.
- Review the Page or next action before anything is shared.
Clarity also means showing the boundaries.
The product story cannot stop at generation. Sources remain private by default, generated results preserve their relationship to the underlying context, and consequential actions wait for the user’s approval.
That is why the homepage now pairs the Apollo product walkthrough with explicit Trust & Control—not as a separate promise, but as part of the same workflow.
What we are testing next.
We are looking for a simpler signal than feature recall: after the first screen, can someone explain Memova in one sentence, and can they see what their first Book would be about?
- Does the first screen make the input-to-Book transformation obvious?
- Does one complete example teach more than several disconnected feature cards?
- Can people distinguish the private Book from the Page they may choose to share?