3 ms·
Nice...i like the simple design and functionality. But, a serious question in regards to how you implemented it. Isn't that how you would usually go about impl
by scorpioxy 18y ago
Nice...i like the simple design and functionality.
But, a serious question in regards to how you implemented it. Isn't that how you would usually go about implementing something?
As in, the rule of thumb is: think of the least functionality needed to launch a first version, use a CSS framework to avoid writing your own, use a JS framework to avoid writing your own, start up with a simple design, use some kind of code framework to avoid re-implementing common functionality such as authentication and caching..., and so on....
After testing the water with that, you can start replacing stuff if needed, hiring a designer for a more fancy look and the like...
- monological 18y agoYes all those things that you mentioned are done by default. What I'm simply saying is that you have to watch out for the temptation of adding non-critical features or rolling your own solution without doing your hw first. It's easier said than done. In regards to design, people spend a lot of time creating photoshop mockups, then modeling it with css and html. I'm just saying, if you want to get it done quickly, just skip all that and keep it minimal.