6
11 Comments

My Problem with No Code

Hello again IH community,

I noticed that there are many people that use no code on this platform, and I think that the rise of no code has been great for creators to ship products, but there is a stark problem that I see with No Code and I wanted to address it, specifically Bubble.io.

First I will talk about the problem with no code in general and then I will touch on the problem that I see with Bubble.

No Code has Risk.

When you use a no code platform like bubble you are opening yourself up to platform risk. What happens if Bubble shuts down tomorrow? Most likely your app will be lost seeing how many components in Bubble and other no code platforms are dependent the server side code that Bubble has built.

Will Bubble shut down tomorrow? Probably not, but you open yourself up to that risk when deciding to use it or any other no code platform.

No Code is not good for exiting

If your goal is to not get acquired or you never see yourself selling your app then you can ignore this part. Most companies looking to purchase your app will not move forward if you depend on something like bubble or all your automations are done through a 3rd party platform. If you ever have any ounce of thought that you would sell then do not use a 3rd party no code solution.

Bubble is great to validate, create MVPs etc, but you are hurting yourself in my opinion if you choose a no code platform to build your entire app.

Bubble.io's Terms of Service

I was skimming through the terms of service, yes I am a nerd 🤣. I found a couple of interesting things that I think you as a founder should be aware of.

If you have trademarks, when using Bubble you are granting Bubble in their words "a limited, non-exclusive, non-transferable, sublicensable right to use your trademarks on the platform". As a brand this is nuts, to just give that type of access to your brand is scary because they will not adhere to your guidelines.

They can remove user components at any time for any reason. They say "BUBBLE WILL HAVE NO LIABILITY TO ANY BUYER OR SELLER FOR LOSS OF PAYMENT, LACK OF SUPPORT, REMOVAL OF USER COMPONENTS, OR ANY OTHER CONSEQUENCES ARISING FROM THE TERMINATION OF A BUYER OR SELLER’S BUBBLE ACCOUNT, REMOVAL OF A USER COMPONENT FROM THE BUBBLE MARKETPLACE, OR ANY ACTS OR OMISSIONS OF BUYERS AND SELLERS WITH RESPECT TO THE BUBBLE MARKETPLACE. "

This makes you so vulnerable, in fact I would rather build everything from scratch then use Bubble because for me I am not comfortable using their platform knowing at any time they can remove things.

Before using a low code/no code platform please read their terms so you know what you are getting yourself into.

Conclusion

You may be fine with Bubbles terms and if you are more power to you. You also may be comfortable with the risk and that is fine if you are go out and build. I think it is important to be aware and to be knowledgable of what you are getting yourself into before you make a mistake that you didn't know you were making or weren't aware of.

If you want to stay up to date with me (just some random guy on the internet who has hot takes every no and again) you can find me on x.com/blakerunyon_io.

Thanks for reading ❤️

Do you agree?
  1. Yes
  2. No
  3. Neutral
Vote
on October 14, 2023
  1. 2

    When I first heard about Bubble, I was so stoked! I'm an avid Webflow user and I thought it would be the same thing. Sadly, it is not. Very hard to learn, and like you pointed out, many issues.

    I truly believe it is easier to build a prototype with something like Firebase and React, especially with ChatGPT. Less limitations and you learn a skill you can use forever, regardless of the platform.

    Great post!

    1. 1

      I agree, the biggest issue for me was the learning curve was very high to make anything useful. Plus skill on bubble does not transfer to anything else BUT Bubble. Thanks for reading.

  2. 1

    I think you may be overstating some of the risks you've identified here, but I certainly agree that platform risk is real. And actually, it's two other points that would concern me more than the ones you mention.

    The first is that the way that no-code platforms charge for higher usage varies and can change fairly radically, and of course the price may go up more than you'd have anticipated. I forget which platform it was, but one just recently started charging an extra fee for each foreign language you supported on your site on their platform. For some people, this made doing business on the platform enough more expensive that they were looking to jump.

    The second is that, if and when you migrate to some other platform, you don't have code to take with you. You're starting over and all the details you worked out along the way are at risk of being overlooked as you recode.

    I'm a bit of a stuck record on this point, but if you want a lowish-code platform to build things on that's completely open and has lots of options for changing providers and for hiring people who know how to do more advanced work, WordPress deserves serious consideration. Not to mention that a lot of the capabilities you'll have to write yourself in other frameworks are already available as low-cost or free plugins.

  3. 1

    What about the other platforms? like softr, Glideapps, etc...

    1. 1

      I have never heard of those and I could do a follow up post sometime in the near future. I would venture to say though that caveats like platform risk, pricing fluctuations etc would still apply.

  4. 1

    The other platform risk, which has happened with Bubble, is that they change their pricing. In particular, if they don't just increase prices but change how they price, it can suddenly bite you.

    The biggest story of this risk right now is Unity's retrospective change to charge per-install.

    1. 1

      Great point, I didn't even think about the pricing changes. It is so true though, I remember the reddit pricing changes which required many third party apps to shut down.

  5. 1

    I understand your points.

    I think at the end of the day, each founder must sit down to evaluate the risks involved in building no code tools in relation to their long-term goals.

    With no-code blowing up, a lot of founders might overlook the risks involved and dive in headfirst.

    Thanks for the fresh perspective/reminder, Blake.

    1. 2

      100% I think that the risks will vary from founder to founder and what might work for me won't work for you or vice versa. I think the worst thing is making an uneducated decision. If you evaluate the risks and are fine with them then great, but at least do yourself the favor of knowing. An uneducated decision is always a poor decision.

Trending on Indie Hackers
Meme marketing for startups 🔥 User Avatar 11 comments 40 open-source gems to replace your SaaS subscriptions 🔥 🚀 User Avatar 1 comment After 19,314 lines of code, i'm shutting down my project User Avatar 1 comment Need feedback for my product. User Avatar 1 comment We are live on Product Hunt User Avatar 1 comment Don't be a Jerk. Use this Tip Calculator. User Avatar 1 comment