Share sheet for developers
Share it to Grape. It is a note now.
Share a page from Safari or a file from any app on your phone and it lands as a note beside a pile of runbooks and notes, with the source under the title, ready to read at your desk.
Grape1A page in Safari
2Two taps to share it
3A note in Grape
Article, selection or bookmark on iPhone, with the body shown before you save
Pick the folder in the sheet, or let it land in the default one
Photos, PDFs and recordings shared to Grape arrive as attachments
On Android a shared link is fetched and saved in the background
Two taps from Safari
Tap share, tap Grape, tap Save. The page is a note before you are back in the browser.
See the note before it exists
The title and the body sit in fields you can correct, and what is there when you press Save is the note.
Filed on the way in
Choose the folder from the sheet, or skip it and find the page in your default folder.
More than pages
A photo, a PDF or a voice memo shared to Grape arrives as an attachment in the note.
The same note as the desktop clipper
A page shared from the phone and the same page clipped in Chrome read identically.
On the laptop by the time you sit down
With sync on, the page you saved from the bus is open in the desktop app.
Results
Three things that stop being a problem
Feature lists are easy to write and hard to care about. This is what changes for developers.
Stop solving the same bug twice
Describe the symptom in search and get the note where you already worked it out.
Keep decisions where you can defend them
Ask what you decided about a service and get the note, the date and the reasoning.
Point the AI at your own stack
Bring your own key, or run a local model through Ollama, and keep the workspace on disk.
In practice
What that looks like for developers
A few moments in a normal week where the app earns its place.
Debugging
Write the symptom, the theory and the fix in one note, with the log you kept attached.
Architecture review
Record the conversation and keep the decision log next to the diagram.
New project
Keep the setup steps in a runbook that actually gets found again.
The rest of the app
What Else Grape Does
Every part of the app is built around the same idea: keep what you write, and hand it back when you need it.
AI Agent
Chat that reads your library and can act on it
Open
Memory
The agent remembers what you tell it
Open
Semantic search
Search that works on what you meant
Open
Voice and transcription
Meetings and lectures become searchable text
Open
Web clipper
Save any page from Chrome into a note
Open
Flashcards
Decks built from the notes you wrote
Open
Find it next time it breaks.
Runbooks, architecture decisions and the fix you worked out at midnight, in a local library you can search by meaning and keep offline.