How Unnoodle works
Unnoodle runs inside your web app, so understanding your product never means leaving it. It observes how people use the product and forms its flows by itself. Where only a person knows the answer, your team writes it once, on the screen it describes.
01
No switching tabs
The answer to “how does this work?” usually lives somewhere else: a Confluence page, a Notion doc, a wiki, or a thread from last spring. Every search pulls you out of the work, and many end with asking a colleague. With Unnoodle, explanations, flows and answers appear inside the product, next to the thing you are looking at.
02
Flows, observed, not recorded
As people use your app, Unnoodle observes where they go and what they do, and forms your product's flows from it. Nobody records a journey or draws a diagram.
03
Ask about your product, where you are
Ask how something works, such as which steps follow checkout or what a status means, from the screen you are on. Unnoodle answers from the flows it has observed and the vocabulary your team has written.
04
Explanations on the element itself
Open an explanation and Unnoodle scrolls to the element it describes and draws an arrow to it. No more “the toggle in the top-right of the settings panel”.
05
What only people know, written once
Some knowledge lives only in people's heads. Point at a part of the screen, capture its state, such as a button that is disabled, pending or done, and write what it means. Write your product's terms and definitions once; Unnoodle suggests candidate terms from the page, so nobody starts from a blank list.
06
Questions that stay with the product
Questions and answers stay attached to the screen they are about, as threads with replies, instead of disappearing into Slack.
07
It won't point at the wrong thing
Elements resolve by id, then test id, then unique text, and nothing is shown on ambiguity. If what an explanation described is gone, Unnoodle stays quiet instead of misleading you.
08
Owned by the people who know
Everything belongs to a context, a domain or area of your product, with owners responsible for it. Account security includes MFA, sessions and an audit log.
09
Getting started
During the private beta we set up your workspace together with you. Your developers then add the @unnoodle/browser npm package to your web app, with your workspace's key. Unnoodle opens as a panel beside your product (⌘U), keeps its styles separate from yours, and works with any web framework.
Coming next
- AI-written explanations: Unnoodle drafts the explanation for a screen or state, and the context's owners approve it before anyone sees it.
- AI-proposed vocabulary: Terms and definitions found in your product, proposed by AI and confirmed by their owners.
- Agent access: How your product behaves and what your team has explained about it, readable by the coding agents you already use.
Not available yet. Listed so you know where this goes.