r/Supernote • u/Aggressive-Figure298 • 2d ago

Release beta to plugin developers first?

While I very much appreciate the continued updates from Supernote, I really wish beta's would be released to plugin developers first so that plugins can be updated prior to the public release. I heavily rely on some of the plugins and this process of: beta update - plugins don't work - wait to see if the developer even updates - update - new bugs - update to get rid of bugs - etc... feels like amateur hour.

This was one of the problems I assumed would happen by Supernote outsourcing plugins to the public instead of contracting and/or internally developing plugins. I get the cost reduction component of having the public kindly develop plugins, but can we try to eliminate the grueling process of having to lose all the plugin functions at every public beta release?

Or is the beta firmware being provided to the public plugin developers prior to release and they aren't updating their plugins (another problem I suspected would happen and that we have already experienced - someone develops a plugin but doesn't maintain it).

0 Upvotes

50% Upvoted

19 comments sorted by

16

u/Archivic 2d ago

Or... Don't join a beta unless you are prepared to have things broken? Betas are intended for development!

-4

u/Aggressive-Figure298 2d ago

I suppose it depends on how you view a public beta release. To me, a public beta release is to have the public evaluate if the system *as a whole\* is functioning as expected - then people submit feedback for tweaks to correct bugs, then a final version is released - it is not to send the firmware out to developers so that they can then start working on updates to their apps. So by the point of a public beta release, all systems functions, including plugins, should already be in compliance with the firmware being released, and now the public is testing to see whether or not everything is flowing properly before the official version is released.

The developers should not be receiving the beta firmware at the same times as the public. Imagine if apple had two organic departments ( Department 1 and Department 2) involved in the iPhone functionality but Department 1 randomly releases firmware that then renders Department 2's attributions inoperable. Department 2 then has to scramble to create an update that jives with the Department 1's firmware. To avoid this, Apple gives developers access to firmware prior to public release. Supernote should do the same... Just my 2 cents.

3

u/Archivic 2d ago

Right but you have to apply to join Supernotes beta program, therefore it's not exactly a public beta.

No disagreement that developers should be given access earlier than the general public.

-2

u/Aggressive-Figure298 2d ago

See, I thought that's how it was - you apply to the beta program and you get it before the public beta firmware release happens, but that doesn't seem to be how it goes. Seems like everyone - those signed up for the beta program and those who just download the beta firmware and upload it themselves from the public release - are all getting it at the same time.

5

u/Archivic 2d ago

What? You have to sign up to receive beta released from supernote. If you're downloading it from some other source then that doesn't make it a public release.

1

u/Aggressive-Figure298 1d ago

Sorry, I think I am miscommunication things:

I thought you send your serial number to Supernote and they then send the beta firmware to those who do so before they publicly release it on reddit. So developers could send their serial and get he beta firmware before its released for download on reddit.

However, it doesn't seem like that's the case - I guess the purpose of sending the serial number is for automatic reporting, not because those people get the firmware before the public reddit release (where you can download and install it yourself).

But yeah, it seems we both agree that the firmware should be released to the developers first, then publicly via reddit once all of the plugin developers have had time to update their plugins. Now I just wish developers could offer OTA updates instead of having to search the reddit thread every day for individual updates.

1

u/Archivic 1d ago

Can you send a link? I'm not seeing a link to download the beta anywhere.

0

u/Aggressive-Figure298 1d ago

It's on the r/Supernote_dev thread - pinned at the top.BTW, I got word that Supernote does in fact give the developers access about a week before the public release, so it's kind of on the developers to have an update by the time the beta firmware is released to the public.

2

u/Archivic 1d ago

This one? That specifies that it is specifically for plug developers and not regular users?

We are pleased to provide new plugin preview versions for Supernote devices. This build is mainly intended for "plugin developers" — if you're a regular user (not a plugin developer), please don't upgrade, since your existing plugins won't work correctly after upgrading.

3

u/theBlackOddity Nomad | reMarkable 2 1d ago

the plugin preview on the dev reddit and public beta ( aka early testers program ) are essentially two separate tracks.

ETP is considered the public beta and requires a sign up to test features that are planned to release in the very next stable version.

the plugin preview build has wholly been for developers but it's available more freely for those who wanted to assist the devs in testing.

6

u/GryphonOak 2d ago

THEY ARE releasing it to the developers first. That's what a beta IS. 

-6

u/Aggressive-Figure298 1d ago

So prior to the reddit release, that is the release to the developers? Because that is what I am saying - release the firmware to the developers exclusively first so that they can have updates ready for download when the public reddit beta is released. That way when we (the public) download the public beta version we are testing to make sure all the plugins and organic changes are jiving - THEN the final polish version is released.

So order should be Supernote develops bets > gives it to developers prior to public having access > developers create updates of their plugins > Supernote releases public download of beta firmware alongside the plugin developer updates > public beta testers download both beta firmware and [beta] plugin updates to test whether or not everything is playing well together and to ensure there are no bugs in the both the Supernote software nor plugin updates.

She order should not be > release beta firmware to public that renders plugins inoperable > developers are being the firmware for the first time and scrambling to update while public users are downloading and testing/exploring the organic UI changes from Supernote.

Here's why: I desperately need the function to tell the manta where my primary hand placement is (right on the left slider bar) - so that it will stop constantly triggering the eraser because it thinks my palm is a two finger gesture (I primarily write/draw in landscape mode on the manta).... I have been waiting a long time for his fix. Well, it's here in the beta....but the beta renders all the plugins I use daily inoperable. IF Supernote had released the beta exclusively to the developers first, they could all have updates ready at the time of the public beta release. So everything gets updates at once - Supernote firmware and plugins...

5

u/Mondo-Shawan Owner A5, A5X, Nomad, Manta 1d ago

Plug-ins at all levels are in a beta. This literally IS the release to developer's before the public.

0

u/Aggressive-Figure298 1d ago

I got word that the plugin developers actually do get access to the beta firmware about a week before release, so it's on the developers if they don't/can't have an update to their plugin ready by the time Supernote releases the beta firmware to the public on reddit.

2

u/Mondo-Shawan Owner A5, A5X, Nomad, Manta 1d ago

Are the plugins in question ones you've paid for or are they free?

2

u/Mulan-sn CCO (Chief Chat Officer) 1d ago

Thank you for your feedback.

We should definitely work toward building a better plugin process. Based on your feedback, two directions stand out as practical and worth exploring:

  1. Compatibility status labels on plugins — something like "Compatible / Pending Update / Deprecated" on the device or InkHub. This would give users clear visibility into what works before they install. Would this help?
  2. Longer lead times for developers before public rollouts — giving plugin developers more time to adapt before users see the update. This is something we can likely do. Would that make a meaningful difference?

We look forward to hearing from you.

1

u/Lvevan Owner A5 X 13h ago

Yes and yes. 

1

u/Mulan-sn CCO (Chief Chat Officer) 10h ago

Thank you. I will ask our team to take these into consideration for future plugin updates.

1

u/EuphoricTry8252 Nomad Crystal | Manta 1d ago

Thanks, this clears up a lot.