dumbdevengineer
dumbdevengineer on Hacker News
No-code tools should get you atleast 50% of the way there and by that point you should have a more complete list of any problems you are going to encounter and a more accurate vision of what the application should look like.
Definitely if you can do the no-code app in a way you can extend later that is more ideal than rebuilding it completely.
But for anything novel and complex no-code tools simply don't suffice, you can start with them for an MVP or example app but you'll very quickly have to move to coding it up fully custom(in my experience atleast).
When you go from no-code -> MVP you will likely have to throw away most of the no-code version and rebuild from scratch, so it is a question of how far can no-code get you and does it make sense for your use case?
So, it depends, what are you building?