To code or to NoCode

Say something nice to that_guy_iain…

Post Comment

3

If it starts getting traction, it may be very difficult to tell if you can handle 100 concurrent users, 1000 or just 10. Using NoCode through a company will likely mean that you have no idea what sort of traffic they can manage, which may affect your application's growth.

^this. it's hard for me to predict the efficiency of the code that is behind the hood of no-code tools. When your writing your own code, you can manage your own code's time complexity as well as space dimension, but I don't know how to do this with no-code tools. It could be that your no-code tool works, but its so slow that its really unusable for your users, which isn't where you want to be. Now, I don't have much exposure to no-code so everything I said could be false.

Take it with a grain of salt.

indietoinfinity

·
4 years ago
·
Reply
1. 1
  
  I agree. I can imagine that the code base under the hood of a no code SAAS will be much less efficient as a 'built from scratch' SAAS. That being said, no code is great for MVP's and internal tools as it means you can validate your idea first before jumping into building it for real.
  
  yusl212
  
  ·
  4 years ago
  ·
  Reply
1

I think solutions like Webflow & Bubbles are really powerful for no-code MVP's or internal tools. Depending on how complex a tool gets and how big you would like to scale custom-coded solutions might still be the right choice - at least for now.

morris_togo

·
4 years ago
·
Reply
1

The main problem that I see with no-code is that you are essentially building someone else product and business for them.
Your product can be cloned in the blink of an eye and although a business is not just product, if the product becomes the same as every competitor, then it is just a race to who has the deeper pocket to waste on ads.

filippo_b

·
4 years ago
·
Reply