I think one important lesson here is that by abandoning the traditional SPA approach, you're also opening up your site to be indexed by search engine crawlers much more easily.
this is something i struggle to understand. especially with SSR/isomorphic rendering.
the vast majority of websites that need indexing should not need JS to create the html.
the vast majority of web apps that benefit from being SPAs are behind some form of login/auth and so do not need indexing.
yet there's this obsession with writing SPAs that can be pre-rendered for better indexing. i only assume this is a solution to the desire of using nodejs and javascript as a server-side language regardless of merit.
Some sites are a combination of content (blog, products etc) and a login area with a complex UI. A SPA works well for sophisticated user interfaces but is overkill for content that is just for reading. But then you have to decide is it worth jumping back and forth between JS and your server side language (Java/Ruby/Python) or maybe it would be nice to just have one language to rule them all...
the vast majority of websites that need indexing should not need JS to create the html.
the vast majority of web apps that benefit from being SPAs are behind some form of login/auth and so do not need indexing.
yet there's this obsession with writing SPAs that can be pre-rendered for better indexing. i only assume this is a solution to the desire of using nodejs and javascript as a server-side language regardless of merit.