Faster and lighter web experiences are the next big things and teams of developers are reengineering their solutions to make them faster not only because speed metrics are being taken into consideration by search engines but because of the value of time for customers. Time is money is an adage that every one of us knows well and for the context of web development, more time for building and loading a web application is money spent by the web application owner and the customers.
Most of the optimization rooms are on the user side, the browser, where manipulating the DOM and rendering it faster has become a top-level priority that puts frontend engineering teams on a challenging time after they have built and chipped amazing user interface.
Let’s recall that my opinion is that the user experience has more weight and priority than the productivity of the software engineering team or the alone software engineer like me. But my product management and design skill instinctively spoke cognitively out loud to tell me why I have not said product manager and designer instead of software engineer because what I am going about with you with these words is also about the design and management of a tech product that deals with web applications development productivity and performance testing and benchmarking for not only tech decision making but also for shipping better experience to end-users.
Tech people ground their decisions on science, knowledge, data, and tech then why just decide to choose a framework without having clear performance and user experience data and why not use all the available framework to build our solutions and ship to each user the one that is most efficient given the user’s environment.