SPA by default
September 25, 2024
SPAs incur complexity that simply doesn’t exist with traditional server-based websites: issues such as search engine optimization, browser history management, web analytics and first page load time all need to be addressed. Proper analysis and consideration of the trade-offs is required to determine if that complexity is warranted for business or user experience reasons. Too often teams are skipping that trade-off analysis, blindly accepting the complexity of SPAs by default even when business needs don’t justify it. We still see some developers who aren’t aware of an alternative approach because they’ve spent their entire career in a framework like React.
Via Simon Willison and over 2 years old, ThoughWorks expressing concern that the SPA pattern has become so ingrained that developers and teams rarely consider whether it’s the right approach for a given project.
