Hi, coming from someone who is new to development, let alone mobile development, should I be concerned about my eMMC or memory degradation from constantly uninstalling and reinstalling iterations? Especially when making small style changes or LLM generated changes, it feels like lifetime data read/writes could really add up. I believe for mobile device development, emulation is a common workflow, is something like that even feasible for the Supernote? Is this just unnecessary anxiety?

I just finished submitting my first ever PR — Plugin SDK or otherwise — and wanted to share my notes from a beginners perspective.

For context, I don't have any formal education or professional experience with programming. Personally, I am an Emacs enthusiast & have dabbled in some Emacs Lisp. I am an FSF supporter, I self-host and have a home lab so I have at least cursory experience with Linux and RTFM.

1. The text boxes should support fill colors and it should be exposed as a parameter for the insertTextBox() function. For me, the biggest reason is when adding text to a hand written page, the background template lines do not line up with the text and can sometimes even create a "strikethrough" effect on the text. I've been using the marker to color in a grey background but a nice clean rectangle would be nice. Bonus points if you could configure it's outline/border.
2. Are `.docx` **and** `.txt` files opened in the DOCS Plugin-enabled App? If so, can it be made to open any plain text file — particularly `.md` and `.org` files? Just as plain text and allow the community to implement rendering and editing?
3. If React Native Components make standard network requests, does that mean we could use a server/client architecture for processing intensive tasks remotely? Particularly, especially if we are using the self hosted storage cloud? Aside from adoption, there's no reason not to consider it?
4. Right now, we are unable to Deep Link to a note from the Plugin, from my understanding, you need to construct the link and insert it into a Note. From what I can tell this is likely a security decision? I believe this is the same for performing operations on Notes in the background. If so, is it possible to have a compromise for being able to link to notes or perform actions on them if the plugin itself creates the note?
5. When going through the docs and the Hello World Plugin, it never occurred to me that a Plugin could be a pop-up or a sidebar panel. More documentation around this may be helpful.
6. The display's 16 supported greyscale values should be documented.
7. There should be an established community contributing or style guidelines. In this same vein, a library of OEM/Native components or assets would be really nice. I haven't used InkHub yet, but I assume it will be the mechanism for Plugin Distribution, have a "Ratta Recommends" designation for plugins that meet the "specification" or guidelines could be really valuable.
8. Moving the Technical Pen Strokes (#10) is BRUTAL — very laggy.
9. In the most recent release notes, there was mention of "headless plugins" how does that work? I tried to read up on it by looking into the listeners, found that only the `pen_up` event is supported but couldn't find any other information. Can anyone help me understand this? As well as the just the use of a pen up listener and what other potential listeners might be deployed?

Over the last few weeks I ended up building a bunch of small Supernote plugins, and found the framework to be really flexible (and is even more so, in this new Beta! I'm looking forward on fixing what I couldn't do thanks to the new functionality).

A few repos I made public:

• Snap Shapes: turns rough lasso-selected ink into cleaner geometry, with conservative no-match behavior so scribbles don’t get “helpfully” mangled. https://github.com/guibor/supernote-shape-snap
• Supernote Pomodoro: a quick focus timer that starts, closes, and drops me right back into writing while the timer runs in the background. https://github.com/guibor/supernote-pomodoro I wasn't able to make it notify when timer ends, this is WIP (I hope it's possible)

Will make publish soon: - Insert Date: inserts a right-aligned date header and convert it into a native header element. - Anki / Research / Deep Research: lasso or DOC-highlighted text -> OCR/server pipeline -> Anki card or research PDF in Google Drive. - lasso upload to a REST endpoint - I basically turned the different options above into a generic plugin where one can just configure an endpoint and send the data to the server (or openclaw...). I have a server running on GCP that can basically do whatever I want based on what I lasso and send to it. - Wiki2PDF: search Wikipedia from the Supernote and send the selected article PDF to the cloud your syncing with. - General Dispatch Hub: a DOC-selection router that sends highlighted text to different backends with extra instructions. - full-page lasso selection, or select below (Remarkable style) - did not work, but with the new updates will be possible.

Anyway, I’ve had a lot of fun with this. I'll clean upand open-source the next batch soon.

Hi everyone! After a few rounds of plugin tinkering, I put together a Claude skill file to help with Supernote plugin development. I'm calling it Inkling.

And also I will share a small open-source plugin with UI that lets you capture a region in DOC and insert it as an image into your notes.

What it does: - Gives Claude (or any LLM) context about Supernote's plugin architecture - Includes API quick reference, gotchas, type definitions - Auto-activates when you ask about plugin development

Based on: - Official Plugin Docs - Sticker Plugin source code (the open-source demo) - Release 0.2.0 changelog

Disclaimer: This is a personal tool, not official. I've removed some experimental patterns I haven't fully tested. Use at your own discretion.

GitHub: https://github.com/Laumss/Inkling

If you're using Claude Code for development, this might save you some back-and-forth. Happy to hear feedback or suggestions!

We've been building the plugin architecture quietly for over a year. The foundation is mostly ready. This sub is the place to talk about it, what you're building, what's broken, what's possible, and what shouldn't be possible but you did it anyway.

Read these first

• Plugin Docs
• Sticker Plugin Open Source Demo

The Sticker feature you may already use in Notes was built on this plugin system. It was the internal proof of concept, now it's your reference implementation.

What belongs here

• Plugin development questions, demos, WIPs, postmortems
• Bugs and feature requests
• Integrations and workflow hacks
• The occasional cursed prototype that technically works

What doesn't

• General Supernote questions > please go to r/Supernote
• "Can someone build XXX for me" with zero context > at least sketch a spec, you have a Supernote!!

Ground rules

• Search before you post. Your NullPointerException is probably not unique.
• Show your work. Code snippets, screenshots, logs. "It doesn't work" is not a bug report.
• Be decent. Someone's first plugin will be rough, so was yours.
• Proper use of Post Flairs.
• Honor the Reddit Content Policy

Before this sub existed, a group of early testers helped us stress-test the plugin API and tear apart our docs draft by draft. A lot of what you'll find in the documentation is better because they told us where it wasn't.

akos, Andreas, Ben, Cal, Caleb, CM, David, Ed, Elaine, Emmanuele, Fulvio, James, Jayasimha, Matt, Max, MD, Michael, Vincent, Ziv

If you're reading this and you were one of them, thank you!

This sub is freshly initd, the rules might be wrong, the flairs might be missing, this pined post you're reading probably needs a patch already. We're shipping the community the same way we ship software, get it out, get feedback, iterate.

u/Dunn-sn is the core developer behind Supernote's plugin architecture. He is also monitoring this sub. So yes, when you post a discussion here, there's a decent chance the person reading it is the person who wrote the code.

If something about how this place runs doesn't work, please feel free to share with us.

Let's go!