It seems like a lot of headache rtight now, especially with plugins. For example, despite bubble documentation saying that most plugins are compatible, it looks like there’s a huge limitation of workflow-only access, no visual plugins. This renders the majority of popular plugins such as VideoJS by @pork1977gm useless on Mobile. Is ListShifter (Floppy) available at all?
Is there a long term plan for this? I’m having a hard time seeing where bubble native has a better value than wrapped webapps. Is bubble native meant for *new projects only*? If there isn’t a focus at all on simplifying the converting of web app to mobile app, that sort of disenfranchises the majority of existing bubblers. An approach I wouldn’t be surprised at, given recent decisions, but I would love some clarity if possible.
As a prospective builder, how would you interpret this? Moreover, how best would you use this plugin within the native mobile environment as the plugin page suggests?
So this is my take on all of this… hopefully what I’ve written is somewhat correct.
This is true…
Server-side action plugins would be compatible, but not any visual elements or client side actions as they’re based on entirely different frameworks
There will be a new plugin editor which I believe is still in Beta with handful of developers testing it. When that’s released, that will contain the extra functionality allowing us to get the visual elements working in the mobile builder (because it contains the react framework).
Right now, if a plugin has the mobile category ticked, like shown below, then I think that’s probably what triggers the text you circled to say “Web & Native mobile”. This is only true for any server-side actions inside the plugin simply because they don’t run on the mobile (by that I mean the browser), they’re node based and run from Bubble’s servers instead (same with API calls).
