Why am I still not able to develop mobile plugins?

Meta
1

It’s been months now since I’ve waitlisted for it, and am seeing more ‘top-tier’ agencies pushing mobile plugins. This is not ideal as us little guys or smaller agencies will get in much later, when the agencies have already created an established a 1-to-1 connection with the app-makers. This is creating a monopoly. You guys already know who I am referring to, I don’t even have to say the name.

As an established plugin developer, I should have had the privilege to develop mobile plugins by now.

2 Likes
2

Nick shared some useful details here: Timeline native mobile - #10 by nick.carroll

3

Thanks for this.

1 Like
4

I’ve bring point this a long time ago …

1 Like
5

100% with you on that one. It’s a shame that they a-listed the usual suspects (which totally deserve the credit, they are not to be blamed for that privilege of being honored as close group of agencies who were selected exclusively make money from mobile plugins. Anyway , as we develop and use our own plugin , due to bubble approach with this ‘waitlist’ , we shifted 2 customer projects to another platform and currently not considering it for mobile native development. Thats more of an attitude and community relationship that we cannot tolerate

6

I should of searched first… I was just kind of eager to put a point across.

Appreciate that. I was almost close to selling my plugins and calling it a day, but then I would be just feeding the beast.

1 Like
7

Good points. I don’t want this to sound like excuses, but the unfortunate reality is that when the team launched the closed alpha for the native mobile plugins editor they had full confidence that it would turn into a public beta shortly after.
As nick pointed out in the other post, a number setbacks now mean we’ve had to pick In App Purchases as the first “must ship”.
And you might say “well why don’t you just flip the switch and make the close alpha a public beta anyways?”. The problem with that is that an alpha release is alpha for a reason. Unstable. Quirky. A poor experience. So going from a handful of testers to hundreds (or thousands) could reflect very poorly on Bubble. Especially if the team knows they won’t be able to address user feedback using the beta for weeks or months.

Hope that makes sense and of course I’ll keep sharing your comments internally

8

I totally understand. It does make sense. I’ll be an eager patient cowboy.