Rich client side web apps gone too far (2014)

Re:Rich client side web apps gone too far (2014) by zo1 on Saturday March 28, 2015 @08:25PM (#9283367)

My biggest gripe with single-page apps is the lack of any sort of standard URL structure. With normal websites, even dynamic ones, you could pretty much put bookmarks almost everywhere. And the only times where you couldn't was probably in spots where the developers didn't want you to for some odd reason (say an intermediate page within a signup wizard).

But single-page apps completely break that. It then becomes some sort of hit/miss issue of whether or not that specific implementation of a single-page app's dynamic URL will behave nicely. Will it post, will it alter something, will it complain and just send me back to the main page? I don't know, and the URL doesn't necessarily tell me that.

Ironically, this is how I came across this post. I was trying to find valid/genuine criticism of single-page apps.

[ Parent | on HN ]

Re:Rich client side web apps gone too far (2014) by nacs on Saturday March 28, 2015 @08:34PM (#9283392)

That's more a gripe with badly-designed SPAs than all SPAs however.

Many SPAs use the history API[1] to make a URL for everything -- Backbone, Angular[2] and such support this for example. React.js apps typically use some kind of router component that supports this (or they can use Backbone's Router).

[1]: http://diveintohtml5.info/history.html

[2]: https://docs.angularjs.org/guide/$location

[ Parent | on HN ]