Re:Ask HN: Using no-code tools to prototype faster in a star...
by Fasaiph on Sunday July 23, 2023 @03:36PM
(#36838916)
Thanks for sharing! I’m building an iOS app. I have no experience with Swift or React, so I thought Flutterflow would be a good place to start to get something out there.
From the comments on this thread, I’m getting the idea that no-code is not enough for an extensive Mobile app and the MVP probably have to be rewritten if the idea works. I think it’s okay tho - most ideas change so much since ideation and it’s more important to get feedback early.
I’ll start with a no-code tool just to test out the concept and get early feedback, and then learn UI dev once I encounter a limitation or there is a need to actually rewrite.
Re:Ask HN: Using no-code tools to prototype faster in a star...
by dumbdevengineer on Monday July 24, 2023 @08:00PM
(#36855913)
Yeah totally, agreed.
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?