[oomkiller]

Sure it's possible to ignore, via Turbolinks or similar. I have witnessed the shift back to the backend over the past year or two, including in the Phoenix community. With HTTP2 inbound and microsecond response times via Phoenix, the case for making your new app a SPA is harder to make, if you take an honest look at things. There are some benefits to be had with React Native, or Angular2 Dart + Flutter, but mobile apps are very difficult to justify, given the increased friction they cause to new users.

[allover]

Hrm, can't really agree with the premise, I feel like the backend not being fast enough should never have been a significant reason to write an SPA.

[oomkiller]

Why would you build a SPA, if not for a more snappy user experience?

[maxthegeek1]

Not sure why http2 and SPA's are in conflict here. If anything they complement one another.

[oomkiller]

They definitely complement each other, but HTTP2 helps out with the request/response cycle and reduces latency in general, which reduces the threshold between rendering on the client and backend.