4 ms·

Aside from cost-savings for the business I can’t really think of one.

• yunohn 5y ago
  This is not an angle I’ve heard before - how does an SPA save money?
  • eloisius 5y ago
    It’s cheaper to build single page apps using web developers than to build and maintain multiple platform-specific native apps.
    • yunohn 5y ago
      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?
      • perryizgr8 5y ago
        > 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?
        • yunohn 5y ago
          I haven't wished for any/most web-apps that I use to be native. This is also the status quo. As such, people with an opposing viewpoint (like the earlier commenter) should provide a basis for their argument. https://yourlogicalfallacyis.com/burden-of-proof https://yourlogicalfallacyis.com/burden-of-proof
    • easygenes 5y ago
      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.
  • 3np 5y ago
    Offload computations and rendering to the client
    • yunohn 5y ago
      Which computations and what rendering? Very little money is saved from SSR vs CSR, rather the lower data transfer saves everyone money and time.
      • hansel_der 5y ago
        > 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.