Anyone who has had even a passing interest in web application development within the last ten years will be able to appreciate just how rapidly patterns and practices have matured. Long gone are the days of monolithic JQuery-based web applications - organisations can now safely rely on established patterns and mature frameworks to achieve their intended result.
We often speak to clients that are yet to decide on a program-wide adoption strategy for web application development, and are looking for a silver-bullet answer to the question: “Which framework should we choose?”.
As is always the case, the “one-size-fits-all” answer doesn’t exist. When this is discovered, we often encounter cases where the default fall-back decision is to avoid making a decision altogether. This only results in moving farther and farther from modern practice, and further committing to legacy.
When evaluating whether to adopt a framework or library, attention must be temporarily diverted away from the zeitgeist and the marketing – and instead focused on some key factors. Drawing from our experience, we have prepared a generalised list of some of the most important strategic considerations:
The pace at which web technology continues to evolve presents a particularly difficult landscape for an organisation looking to set down roots, but the above considerations should help you to effectively evaluate the benefits of a given practice, framework or library.
Over the next few weeks on this blog, we will be applying these concepts to properly evaluate some of the web’s most popular modern libraries and frameworks, to provide you a Ring Leader opinion on whether a given approach is right for your technology team, program, or organisation.