No-code vs Just coding it [as a software engineer]
Currently, I am a full-stack software engineer (full-time job) and while working on my side gig, I thought "instead of investing the time to build out the frontend of my MVP why don't I just use Bubble, or Retool, or some other no-code solution."
My thought process was that I know my MVP will change and doesn't look pretty. I just need to validate my product and test for UX/UI - therefore I am HOPING that these no-code solutions would
- Make the initial development time faster than actually coding it
- Make future iterations faster than actually coding it
I have used Retool for work and it took me about a day max to get up to speed with it, whereas Bubble is nowhere near as easy. Then I read this article and it said that to a somewhat complex application would take several weeks to months?!
To give a bit more context on my MVP... it does not need to look pretty, I just need to dynamically display data on a container based on whether the corresponding data points' checkbox is checked or not.
That's when I started thinking... why don't I just code it if the alternatives take me almost the same amount of time? Is it just that Bubble has a very steep learning curve and if so does anyone have any good learning materials/tutorials?
TLDR; If Bubble has such a steep learning curve should I just code it instead?
Seems like it won't take months to build out that MVP in bubble, more like a week or two.
But yes - the learning curve is high. That's just because there's so much you can do with Bubble. True flexibility.
I'd recommend sticking out the learning curve, as it's only there once and afterwards you'll be able to build extremely quickly.
As for learning materials, there are a bunch of free ones on youtube as well as other platforms. We have some free in-depth tutorials at nocodify.com as well as paid tutorials. Check them out and let me know if you have any questions!
Bubble development is very similar to traditional coding. You are doing so many clicks and drag-n-drops, and settings. So I also see it is often better to start coding even.
But Bubble helps to overcome the barrier for people who think they couldn't code anymore.
Honestly, from my time spent trying to create MVPs and basic working versions of my ideas it just makes so much sense to create something that looks good as quickly as possible and focus on getting early feedback on the idea.
I tend to use WP themes from Theme Forest that come with Visual Composer or Elementor as it's no-code and pretty good to use.
THEN you can start dev work so you do not invest so much time into the basic build. At least with the no-code option you have the basics laid out and I can imagine that makes dev work a little easier (I'm not a dev though).
If you're a developer yourself, there are other alternatives to No-Code solutions - namely low-code solutions like boilerplates/starter kits. (Full disclosure, I am building a JavaScript SaaS starter kit/boilerplate, so my opinions have to be taken in context.)
There are some products that make perfect sense for No-Code solutions, but if you're expecting that you'll need to "eject out" of them at some point anyway, yeah, starting with a boilerplate can get you the speed boost you're looking for without sacrificing the expressiveness and freedom of actual code. Plus, you get the reliability of owning your solution entirely, not being reliant on someone else's platform and their plans.
I'd recommend doing a search for "{your favourite language} saas starter kit" and see what comes up, and compare it against Bubble or whatever other No-Code tools you're evaluating.