This is not an angle I’ve heard before - how does an SPA save money?

It’s cheaper to build single page apps using web developers than to build and maintain multiple platform-specific native apps.

Not everything needs to be a native application, nor should it be. The vast majority of SaaS and such apps are SPA/equivalent and would NOT benefit from being yet-another-installable app.

Could you provide examples (not exceptions) maybe to support your PoV?

> The vast majority of SaaS and such apps are SPA/equivalent and would NOT benefit from being yet-another-installable app.

Could you provide few examples of such apps that would not benefit from being native?

So the smaller-scale correlate would be that SPAs can make more sense for proof-of-concept or hobby-developed applications that need some cross-platform access.

Offload computations and rendering to the client

Which computations and what rendering? Very little money is saved from SSR vs CSR, rather the lower data transfer saves everyone money and time.

> Very little money is saved from SSR vs CSR

this seems counterintuitive.

SSR means most processing happens on big iron inside a dc, this has to be more efficient than each user buying a new machine every few years just to have that peak js-perf needed for the latest frameworks.