When a plugin is widely adopted - @mishav’s toolbox, for example - the Bubble team should buy it and/or offer support for it. It’s the only way to ensure upkeep once it is widely adopted.
@mishav sems to have gone quiet - and as the last post here ( Weird console errors? ) says, there is always the risk that something has happened to the user who built the plugin. What happens in such cases?
Some plugins - Toolbox, CSS tools, and so on, are not just ‘nice to have’ - they’ve become critical to many users’ apps. And, there are thousands of users for these plugins.
In such cases, I’d like to suggest that Bubble should either a) buy successful plugins outright; b) build replicas of free plugins (such as Toolbox); so that in either case, ongoing support is guaranteed for plugins that have achieved critical mass.
Let’s face it - if Toolbox (and similarly relied upon plugins) craps out and the author isn’t around to fix it… Bubble users - and possibly Bubble Team - will suffer.
So, Bubble Team - how about a guarantee of support for plugins once they achieve critical mass? Perhaps you should write something into your marketplace agreements going forward that gives you the ‘right’ to do this (so long as a fair price is paid for widely used apps, to be arbitrated in cases of disagreement).