What must? What can? And how much at all?

The basic question when choosing a framework. Do I want a complex framework that provides many functions - even those that I may not even need? Or would I rather choose a more modest framework that is easier to keep track of and program missing functions myself?

How widespread is the framework?

The simple logic behind it: Quality prevails. Or, what many others use can't be that bad. This works particularly well in reverse. No search engine hits or other indications of how widespread the framework is tend to speak against using it.

How good and comprehensive is the documentation?

Does the framework provide the components I need for my application? Is it what I am looking for? Anyone who has ever struggled through an incomplete, incorrect framework description knows that good documentation saves time. And nerves. Because the more complete the documentation, the easier and quicker it is to make a decision.

What do colleagues say?

The helpful and sometimes time-saving addition to documentation. What have others already used - and for what? What went well - and where did it get stuck? Takes comparatively little time (which others have already invested) and provides something to talk about during the next coffee break.