Subscribe
Sign in
Code or no-code for MVP? What is your approach?
19
Replies
Best
Anas sai
Code is more flexible
Report
Share
IMO low-code develompent for MVP stage seems reasonable. No-code solutions are not so flexible, code stuff is too expencive, so low-code takes best from both methods.
@ffffilipp cannot agree more! As we discussed and agreed with @arbonum above no-code is the best choice for the earliest stages when you are validating the hypothesis. No-code is excellent for prototyping.
@elenat no-code is also a good way to make an alternative to pitch deck for the conference where you gather and measure future demand.
I had a lengthy discussion about this with a highly experienced CTO back then, and he shared some valuable insights. He advised me not to deceive myself by thinking that an MVP is not essentially 1.0 of your product.
If you consider your MVP as the initial version (which I strongly recommend deciding as early as possible), then you should steer clear of any no-code solutions. Trust me, it will become a nightmare in a matter of months when you find yourself supporting this branch of development with early adopters who are constrained by the limited options offered by a no-code platform.
However, if you're just experimenting with your ideas in a "lab mode," then by all means, go ahead and use no-code solutions.
@arbonum then no-code fits rather for prototyping and hypothesis validation from your pov? mvp should be built with coding for the sake of flexibility. correct?
I think no code for a simple site should be enough - It depends on the complexity of the product too
A simple code solution! I think it allows for the app to grow as the customer base does!