There’s a clear niche for bridging dedicated e‑ink note devices with a Markdown‑first workflow. If the plugin can reliably pull in Supernote PDFs or .snb exports and turn them into sync‑ready Obsidian notes, you have a small but growing addressable market among knowledge workers who love the tactile feel of the Supernote. My only reservation is the install friction – the README assumes the reader knows how to enable community plugins and set up the Supernote USB bridge. A quick 2‑minute video would dramatically improve conversion from curious tester to paying user.

The plugin works great for me, but the README could use a quick start checklist. Right now it says “install via Community Plugins, enable Supernote integration” – a screenshot of the settings pane with the “Connect via USB” toggle, plus a note about needing the Supernote desktop driver installed, would save a lot of friction for newbies. Also, a “Troubleshooting” section for common mount errors would be nice.

I dug into the source and noticed the plugin talks to `https://cloud.supernote.com/sync` when the user enables “auto‑upload”. The request is plain HTTP POST with your Obsidian vault path in the JSON payload. That means every note you import could be streamed to Supernote’s servers without encryption or user consent dialogs. At the very least you should add an explicit opt‑in UI and use TLS with certificate pinning; otherwise users with sensitive data will be exposed.

If you’re worried about the HTTP client and JSON parsing surface area, consider moving the sync layer into a tiny Rust‑compiled WebAssembly module. Rust’s type safety and memory guarantees would eliminate a whole class of bugs, and the wasm bridge into Obsidian’s plugin host is already supported. It’s extra build overhead, but the security payoff could be worth it for a privacy‑focused user base.

I like that the default mode keeps everything on the local filesystem – the plugin simply reads the Supernote’s exported markdown files from the mounted USB drive and writes them into the vault. That matches the local‑first ethos many Obsidian users expect. Just make sure the sync flag is clearly off by default; otherwise you’ll surprise folks who thought their notes never left the device.

I’ve been using the plugin nightly for a month. The biggest win is the “Import current page” button that pulls the active Supernote note (including its hand‑drawn sketches saved as SVG) directly into a new markdown file with front‑matter tags for notebook and page number. The workflow is smooth as long as the Supernote is mounted in mass‑storage mode; however, the plugin currently fails silently if the device is in Wi‑Fi sync mode, leaving me with no feedback. Adding a status bar indicator (e.g., “Supernote connected” / “offline”) would make the UX much clearer. Also, the plugin writes the imported files into the root of the vault – a configurable subfolder would help keep the vault tidy. Overall, the concept is solid and saves me an extra export step each day.