GrapeGrape
Semantic search for designers

Find it by meaning, not by memory.

Describe a user flow the way you remember it and the right note comes back. No naming convention to keep up with across a project folder, and no scrolling through research sessions and critiques you filed months ago.
Meaning based search across everything you have ever written
Exact matches still work when you know the term
Narrow down by folder, tag or date when you know where to look
The same search on desktop and on your phone
No naming convention to keep up
Your filing can be a mess. Search reads what the note is about.
Best match first
Results are ranked by how close they are to what you described.
Folders and tags when you want them
Structure helps, it is just no longer the only way back to a note.
Results

Three things that stop being a problem

Feature lists are easy to write and hard to care about. This is what changes for designers.
Draw the idea inside the note
An infinite canvas sits in the editor, so a wireframe and the thinking behind it stay together.
Explain a decision six months later
Ask why a pattern was chosen and get the note where you argued it out.
Run research without a second tool
Record the session, get the transcript, and pull the quotes into the summary.
In practice

What that looks like for designers

A few moments in a normal week where the app earns its place.
Kickoff
Collect the constraints, screenshots and references into one note per problem.
Exploration
Sketch on the canvas, write the tradeoffs underneath and link to related notes.
Critique
Record the feedback session so you are listening instead of typing.
FAQ

Questions Before You Install It

The rest of them live in the help center.

Keep both in the same note.

Drawing canvas, screenshots, research and the reasoning behind a decision in one place, so the rationale survives longer than the file name.