33 ms·
I think the prototype in this case is more to flesh out the idea and its associated functions, without concerns for code quality or security. It would help a l
by Zikes 13y ago
I think the prototype in this case is more to flesh out the idea and its associated functions, without concerns for code quality or security.
It would help a lot in building the road map for an application, but you definitely wouldn't want to use any of it in production.
- 1qaz2wsx3edc 13y agoSome frameworks are designed to help with this step though. For instance: Rails has scaffolds & generators, angular.js has directives (plain old html views you can open), html itself can be used for mock-ups (and there are plenty of others as well). Specifically, why build a partially functional prototype only to throw it away for another framework down the road. It seems naive to me, because the effort you put into the prototype is mostly dropped (except for high-level mental models). Rather then building a throw-away prototype, I think it's better idea to build a prototype you can refactor and improve, with one set of tools.