Share your Bubble experience

Started using it 4 years ago and have been using it ever since!

Like: The flexibility, speed and less to worry about.
You can build almost anything and re-iterate on it very fast, which is great for fixing bugs or adding new features at a speed that impresses customers. And I say less to worry about, as you don't have the concerns of managing your own servers

Common problems: Can be slow depending on the application you want to build and doesn't have much to help you with good UI design, it's all on you to make every pixel look good (sometimes a positive if you have an eye for design)

Learning curve: Tough question which depends on what you want to build, how good you want to get at it and what type of programming and/or API experience you already have

The learning curve question is like asking what is the learning curve of Excel.
In Excel if you only want to show names and emails in columns and rows, then the learning curve is somewhat quick. But if you want to setup pivot tables, custom scripts and charts then it can take a while to master.
Similar in Bubble, if you only want to build an app that has and shows basic information and has no User accounts or data Privacy, then it's pretty quick. But if you want to have a secure multi tenant SaaS with various user types and subscription levels which has it's own API and integrates with 3 other services, then it gets complicated and takes a while to learn.

Best way to know is to sign up and try out some of their tutorials, its free to do so. Dedicate a day or two and see if you catch on to it or enjoy building on it. In the end you will only get as good at it as you are motivated to build something.

Bubble is the "best" no-code tool available today for bringing web-based products to life.

I run a no-code agency and we focus on high-polish web apps built using Bubble. The high polish takes time but is easier to work with if you invest in a good foundation/components.

The reason we go with Bubble instead of some other tool that's more focused on front-end/design is because when your stitching together different 3rd party tools, your workflow becomes disjointed and that has a cost. Webflow might be easier to design with, and Zapier more turnkey for APIs to play with, but it call all be done with Bubble. That saves on cost, development time and risk exposure. This flexibility is one of the foundations of the platform and is why if some feature we dream up isn't possible/easy with native Bubble functionality, I can write some custom Javascript or add some 3rd party API to get the feature I want.

It doesn't come without issues, and maintaining a complex app without the niceties of automated tests can be a huge pain, but once you've set it up you can generally trust its going to be stable.

@sergey_shvets if you're comfortable writing some JS and be patient with the design learning curve, you should be able to create a lot.

Hi there !

The pro : Really easy to get into things done. The quick tutorial helps you to archive the basic stuff then you can deep dive into more complex interaction quite easily.

The way I'm using it : in order to make prototype, in one of two days maximum. This is a really cool way to setup application and show it to you customers.

The bad stuff : Number one, is the speed of the application, it's damn slow. If you are trying to make the number one reactive application on the market, forget about bubble.
Scale is another issue, no way to export the application and therefore you're stuck with this vendor and of course you depend on their platform..
Design is another topic, not realy the best experience in order to build great user experience.

Hope this helps :)

I tried bubble and couldn't figure it out, didn't like it, etc.

anvil was better in some ways, and worse in some ways.

and both too expensive.

webflow wasn't functional enough.

i'd say it's worth spending an hour a day for two weeks on whichever platforms you have energy for so you can see for yourself.

We are built with bubble on our actual platform (app.electricianpath.com). The reason we choose to build with bubble is because of how much you can do with it and make a webapp with complex data and work flows.

The learning curve is longer than most no-code platforms. But it's worth it. It can do much more than most platforms. And you always learn more possibilities as you use it more.

Bubble is really powerful. In most cases, it will cover your needs for product dev. Buy the course on Udemy (one about building Project Management app) and go through it. By the time you are over, you will be building your own product. Don't spend time on anything else.

Bubble has really changed my life. Beforehand, I'd hire developers for projects, but now I can do them myself.

Like: Flexibility and customization to control any aspect of the app. You can really do anything, and it's so powerful. You're building visually, so as long as you understand what should happen in a certain workflow, you're just telling the system how to act (Do this when this button is clicked). It's pretty simple.

Common problems: As with any vendor, you will experience downtimes, though not too common. Also, the editor can be slow at times, but this is highly dependent on your computer and internet connection. Also, sometimes when bubble releases new updates, they may sometimes have consequential bugs in the new code, which could cause errors in your app as well. Again, not too common.

Learning curve: It's high, but that's just a natural consequence for any system that's as robust as Bubble. I'd take the high learning curve any day over a limited functionality program. The thing is though, once it clicks ... it clicks, and you'll be able to build really quickly. I'd say for anyone that's brand new to bubble, they'll be able to be proficient in the system anywhere from 1-2 weeks if they dedicate enough time (Less if they signup for our tutorials at nocodify.com :) ).

Hopefully that helps! Let me know if you have any other questions.