The bulkiness of framework is another important aspect to consider before choosing a framework for sure. I depends of the scale of app you are building and you don't want extra file sizes/load times for features you don't use.
Yeah of course!! For big projects, research is definitely very important because using a wrong framework can result in low performance and it is not easy switching to another one after some time. However, for a small project like it was mine, and it was needed to be up for a very short time, Materialize turned out to be quite good. Not sure how it performs in big projects though.
The bulkiness of framework is another important aspect to consider before choosing a framework for sure. I depends of the scale of app you are building and you don't want extra file sizes/load times for features you don't use.
Yeah of course!! For big projects, research is definitely very important because using a wrong framework can result in low performance and it is not easy switching to another one after some time. However, for a small project like it was mine, and it was needed to be up for a very short time, Materialize turned out to be quite good. Not sure how it performs in big projects though.
For larger projects time spent on preparation work (research, planning, wireframing, etc) is crucial.
A.Lincoln has a great quote on this:
"Give me six hours to chop down a tree and I will spend the first four sharpening the axe."
Yeah exactly! That's how it should always be done _^