Inspiration rarely shows up on schedule inside your notes app.
You might spot a line worth keeping while browsing, find a screenshot in your photos that needs filing away, or get a link in a chat that you'll forget in five minutes. In that moment you're standing inside some other app—you'd have to copy it, switch to your notes app, create a new note, paste, and add a title. That's not many steps, but it's just enough friction to turn "let me jot this down" into "I'll deal with it later."
Abox Note puts the capture entry point at the system level: on platforms that support system sharing, you can share text or a link from another app straight to Abox Note and it creates a new note immediately; on some systems, you can also long-press the home-screen icon and use a shortcut to start a blank note right away. Capture doesn't have to wait until you've opened the app and found the right screen first.
The entry point lives in the system, not deep inside the app
If capture only happens inside the app, the tool is asking you to enter its workflow before you can save anything. But inspiration usually strikes somewhere else entirely—in a browser, your photo library, a chat, or wherever you happen to be reading.
System share solves "the content is already in front of me—how do I get it into a note with one fewer step." Home-screen quick creation solves the other end: you already have a sentence in your head, you just haven't opened the app yet. Both move "start capturing" earlier into your everyday flow, instead of requiring an in-app detour first.
In the current shipping product, the common path looks roughly like this:
- Select text, a link, or an image in another app, open the system share sheet, and choose Abox Note;
- The app creates a new note and opens the editor, with the shared content already in the body;
- When you want a blank page instead, you can also long-press the home-screen icon on supported systems and choose quick creation.
When you share a single URL, the app tries to fetch its title and turns it into a Markdown link, cutting down on the manual work of tidying up link titles afterward. Images go into the note's usable asset path rather than leaving behind a temporary image you can't get back later.
Why every share creates a new note instead of appending to the current one
One intuitive approach would be: if a note is already open in the editor, append the shared content to it. That looks "smarter" and leaves one fewer note in the list.
Abox Note doesn't take that path. System sharing is, by default, meant to be "capturing a new piece of material," not "guessing which note the user happens to be writing right now." The currently open note could be a draft, a long piece being organized, or something entirely unrelated to what's being shared. Auto-appending would tangle the two intents together, making them harder to separate later.
So every share event produces exactly one new note. Share twice in a row and you get two separate records. The title and first line make clear that the note came from a share, so it's easy to recognize this batch of material later in the list and decide whether to merge, rewrite, or file it away.
This is a trade-off between "creating fewer notes" and "not accidentally corrupting what you're currently writing." Capture prioritizes clear intent first; organizing can happen later.
On cold start, a share takes priority over "return to where I left off"
Mobile notes apps often remember where you left off and jump straight back to that note the next time you open the app. That's helpful for continuous writing sessions.
But when the app is cold-started from a system share, two intents collide: one wants to restore the last edit, the other wants to open the content that was just shared in. If restoring the old note still took priority, the shared content—even though it's already saved—might be hidden behind another note, and you might mistakenly think the share failed.
Abox Note makes the priority explicit: system share ranks above the home-screen quick-create shortcut, and the shortcut ranks above restoring the last edit session. Only when there's no share and no quick-create request does the app return to the last editing position.
Ordinary users don't need to memorize this rule. What they need is a straightforward result: coming in from the share sheet, you should see the note you just saved; coming in from the home-screen shortcut, you should see a blank editor.
What this capability solves, and what it doesn't
System share is well suited to getting text, links, and images that show up outside the app into your note library as quickly as possible. It isn't meant to turn every file type into a universal inbox, and it doesn't replace pasting, dragging and dropping inside the app, or continuing to edit a note you already have open.
It's also not the same as sharing out. Turning a note into a web link, exporting a PDF, or publishing a space as a static site are exits for content leaving your workspace; system share is about how content gets into the workspace in the first place. Both the entry and the exit matter, but they're different problems.
Home-screen quick creation is also only available on some systems. Desktop still relies on in-app creation, pasting, and drag-and-drop for similar work. The product doesn't pretend every platform has the same system-level entry point—it just hooks capture into whatever operation users already know, wherever the system allows it.
The first mile of capturing something often decides whether you ever come back to write it up. Putting that step into system share and the home-screen menu isn't about adding one more feature toggle—it's about letting "save this now" happen right where the inspiration still is.