I built out a plugin that uses an algorithm to run a relatively basic computation on an argument of 2 numbers. The main .js file is ~150 lines of code - a couple Math.Min/Math.Max here and there + several iterative loops processing small arrays…nothing too crazy.
I’ve noticed that the time to return an object via a Bubble app workflow takes ~5 seconds when hosting npm packages natively inside the Bubble plugin editor via dependencies vs. hosting the algorithm and npm dependencies on my own server (or even something like CodeSandBox), which both return results instantaneously using very little server resources. Anyone else experiencing slow’ish server-side processing with computational plugins?
Taking a quick look at usage / revenue of all Bubble plugins on the plugin marketplace … plugins generate very little revenue compared to Bubble’s core business (subscriptions/Bubble app resources) which would explain the minimal updates to the plugin editor, outdated Node, no console/debug, etc. assuming their team is following the standard Silicon Valley / Bschool product-driven growth model w/ no moonshot projects around plugins. My guess is that Bubble will put more resources into marketplace products like plugins after they mature a bit, much like Twilio.