- Does the framework have good documentation and plenty of blog and article support for helping you get started? If you can’t compose a simple one-page example using the documentation and example code provided, you may want to select a more mature framework. The only exception to this is when the framework solves a critical problem that would otherwise occupy one or more developers for a longer period of time to create. Just be certain it is easy to understand and customize if required.
- Are there third-party developers building extensions using the framework? Do a simple Google search to see what is available – if developers are willing to extend it, often it will come with better support and opportunity to reuse other toolsets for faster time-to-market.
- Does it allow your developers to code how they want, or does it require changing the way they think to fit the framework? Some frameworks require using their approach, their tools, their way of thinking. This can be a real advantage if your developers share this same way of thinking, but terrible for your startup if they don’t.