As the title states, I believe the Bubble-created plugins should be open sourced so that others can fork and improve them. That is all.
3 Likes
GH5T
2
They should make their plugins kind of open-source, I agree on that.
For a moment I thought you were talking about all bubble plugins, apologies.
Jici
3
The main issue is Bubble plugins, for most of them, are not āreallyā plugins. They donāt use plugin editor to create them. A lot of them should also be natively integrated to Bubble like API Connector (that should have is own tab), RTE, multiselect dropdownā¦
Because they are not real plugins and they probably use some stuff that are not publicly available (thereās a lot of thing that Bubble plugins can do that we cannot do in Plugins builder)ā¦ so I donāt think itās possible for Bubble to make them open source.
6 Likes
GH5T
4
Yeah, theyāre basically built-in to the editor themselves. Not built the same way as contributor plugins.
1 Like
Iāve always thought that the source was available at some point in time because how else would any one ever have figured out the āpā prefix custom type naming convention to bind return objects to plug-in types?
Yes, Iāve noticed this too
they were snooping API calls, most likely. I forget the name of the tool for that
1 Like
Yes I suggested this as well on another post. I highly agree!
GH5T
9
If only they introduced a way for us to build the plugins natively through code with typesafe capabilities. Then things would get interesting.
Creator of Bask here.
The āp ā prefix thing can be introspected in the Chrome devtools network tab when Bubble saves API initializations in the bubble plugin editor.
As for developing with Typescript, Bask has a build mode that I think could work with TypeScript. If not, Iām pretty sure I could push an update to get it to work. We already allow devs to build bundles using esbuildā¦ would just be a question of ensuring weāre recognizing/loading typescript files correctly.
Let me know if you want to explore this further/be willing to test the capability.
2 Likes
Aaa I see. I always wondered how on earth any one figured that out 
1 Like
For a short period of time (less than hour) 2 or 3 years ago, those plugin codes were accessible through the āSee Plugin Codeā button.
It was nice until it lasted.
2 Likes
Sorry for the noob question here but I must ask, as itās been on my mind for a while. If the plugin code isnāt accessible, how do we know itās safe? E.g., not sending data somewhere or doing something else malicious.
Bubbleās plugin code is just as safe as the rest of their application/platform. If youāre concerned Bubbleās plugins arenāt safe, youāre in the wrong forum.
As for 3rd party plugins - I do believe those are ripe for exploiting users. I imagine Bubble does some level of checking it for overt hackery but, I think there is a lot that people could slip into these that could make it onto the marketplace. The worst Iāve seen (which isnāt that bad) is people tracking plugin usageā¦ this could be engineered to hoover up user data that users otherwise wouldnāt want stored in a database somewhere. Thereās a chance Iām wrong.
2 Likes
wevit
16
Why plugins, ? make whole bubble opensource, and if you think they canāt make it opensource, they CAN but will never do that, all because of money.
Donāt say opensource Donāt make money.
Appreciate the reply and thanks for the concern, but Iām in the right forum. Was referring to third party plugins.
3 Likes
autom8
18
Bubble, like any business needs to make money to keep improving the platform and payback the investors. They arenāt obligated to opensource anything. Its a private business.
But I do agree with the OP that it would be a great idea to opensource Bubble published plugins for educational purposes.
wevit
19
So when did I said to not charge users ?
Yes they arenāt obligated but if they wish they can.
I never said that itās a government business.
Looks like this person is a bubble founder disguised in another account 
Forum
Academy
Marketplace
Showcase
Pricing
Features
