Monthly Community Update - Aug 2024

[randomanon]

@georgecollier

You can do it by calling your own backend workflow with no plugins other than native API Connector. Yeah a workaround but you don’t need plugins or regex

Shouldn’t have to expose an internal backend workflow, it’s a hacky workaround. Shouldn’t require users to look up a hacky workaround on the forums for a problem most of them will come across.

@georgecollier

This will never change. Third party vector DBs work well and can be integrated easily using the API. Don’t expect Bubble to invest time in it when their own DB is orders of magnitude slower for CRUD.

Third party “AI designer” tools also work well and can be integrated easily using the Figma to Bubble plugin. There are probably hundreds of other examples of cases where you can point to third party solutions for things that are native to Bubble and can be easily integrated into Bubble. It’s definitely the path of least resistance to adopt a regressive stance so I can understand the instinct.

@georgecollier

That’s what plug-ins are for. It’s not reasonable to expect Bubble to be able to support every use case exceptionally well. It’s a broad platform.

Plugins are there to accommodate individual users’ niche use cases, not for ubiquitous things that every single app needs. Websockets will eventually become this, maybe as soon as in 6-12 months. That’s why I mentioned it as being long-term.

[gf_wolfer]

Second this. I was optimistic about some of the promised performance and WU improvements before the migration but now that it’s only 2 months away my hope is fading, just like my bank account soon will be