Re:The Disadvantages of Single Page Applications (2014)
by buckbova on Monday July 13, 2015 @04:41PM
(#9880911)
I don't suspect he was referring to the gocardless product site, but instead the actual dashboard product.
Re:The Disadvantages of Single Page Applications (2014)
by virtualwhys on Monday July 13, 2015 @05:05PM
(#9881093)
That's where I was.
Not seeing any SPA requirement to click "Payment History" and js display a hidden layer.
Anyway, as far as SPA approaches go this site works well, pretty snappy, no FOUC, just pointing out that server-side + javascript for ajax/effects/transitions is also a viable means to creating a positive user experience.
Re:The Disadvantages of Single Page Applications (2014)
by stevedomin on Monday July 13, 2015 @07:25PM
(#9881827)
I was actually referring to the product site itself.
But you're right our dashboards are also SPA.
Mobile aside, what is really gained in the SPA approach here when you have what is essentially a brochure site? That is, there isn't a lot of content, and it's all static AFAICT, so why not just send the minimal amount of html over the wire and be done with it? Html fragments are already covered for FAQ et al so don't even need to make a round trip to the server.
Anyway, you'd get above checkmarks for free and, if you generate server-side content using a type safe language (Scala, OCaml, Haskell, C#, etc.), for the most part you'd avoid the code salad of client-side typing.
Obviously I have a server-side bias, am curious to see real world use cases where SPAs are a must vs. a trend.