Does it make sense to build a no-code MVP even if you know how to code?
I'm planning to start building an MVP for an idea I have been exploring for the last few months. As a web developer with 2 years of experience, based on previous experience I believe it would take me 2-3 months to launch.
My co-founder, who is a product designer, suggested we use Bubble.io instead. She claims that even though the platform is geared towards non-technical people, it would allow us to launch a lot faster, even taking into account the time it would take me to learn how to use it.
I'm a pretty skeptical about her claims. I'd love to hear other people's opinions on this, especially devs who have build their product on Bubble or other similar no-code tools:
Have these tools saved you time? What advice do you have for me?
This is something I also struggle with as an engineer with quite a bit of experience. I actually used Bubble.io for a proof of concept for enhancemeet.com and was thrilled how quickly I got it "out the door". My overall takeaway is that for something that is simply to build out, a no-code solution like Bubble might be a good first option. Then once you prove the market, you could re-factor from a traditional standpoint.
Agree here. If something can be built with NoCode,I prefer that way. Saves a lot of time from writing code, fixing issues, handling servers and deployments.
Super vague question, but based on your experience, how complicated does something have to be for you to rule out Bubble? Any types of features in particular?
What I'm building isn't super complicated, but it has different kinds of users (Admin, regular user, guest) that interact with each other (not in real-time though). I've seen some pretty complex Bubble apps, but I wonder if there's a certain point where it starts to get hacky (e.g requiring a lot of custom code and plugins)
That's a great question! For me, I'd build outside of the platform as soon as complex business logic comes into play. For my POC, I just needed CRUD operations and user role handling, all of which Bubble was great for.
I also didn't have to use any plugins other than the built-in database system. I figured once I needed to use plugins, I'd also just build it myself.
That makes sense. Thanks! And Enhancemeet looks pretty cool :)
I think a lot of productivity can be gained by doing a hybrid between no-code and traditional development. For example, in my case, I use my own no-code platform to speed up everything that has to do with backend development (data modeling and management, data security, workflow management, ...). Then, using Figma, I design the front end, including navigation between pages, component blocks, etc., I export everything to NextJS with our exporting tool and integrate everything doing traditional development. In this way, you can have an MVP in a very short time to test the business idea. Once you have tested the business idea, you can now focus on scaling it, etc., probably replacing some pieces. IMHO.
I've built 100+ apps on Bubble, including 1 that got me a YC interview.
Pros
Cons
I think this is the future of web development.
Instead of building MVPs from 'scratch' via code.
Prototypes will be built with no-code solutions. Although there are some applications that are too complex to be 'stubbed' out by no code.
To answer your question I'd ask, what's the most complex, detailed, feature that you'll NEED in your MVP?
Does that make sense?
As a developer, I refuse to use no-code tools for anything more than basic idea validation. If you can build something simple using no-code tools, prove it'll work and people will buy it, move to custom asap so you don't get boxed in tech wise.
2-3 months seems too long. If you need to validate could sketch something in Figma or build a super stripped-down version in less time.
It really depends if your goal is getting something usable from the start or having a base to pitch your idea to possible customers.
It depends on the project but if I can build it much faster with no-code, I prefer that way. After seeing the project goes where I can spend more time to code and building a much better product.
https://twitter.com/farukdurak/status/1546406174681346049?s=20&t=5lSf_m4a73wYYfOKCQYb-A :)
It depends on what you're building. But if it's more than just a few simple inputs/outputs I'd stick to code. You avoid a huge platform lockin and also get way more flexibility and structure.