html5 - What speaks against single-page apps from a user experience point of view? -


i them more , wonder why not more common. explanations involving caching or seo make sense me, don't see them directly driven user experience considerations. in way traditional sites page reloads better user?

personally think best argument normal page reloads user's perspective when it's harder break many basic browser functions. in general back/forward buttons work, bookmarking works, copying , pasting links works, history works, page titles work, getting error page when server call fails works, works expected. free.

i have seen single page application implemented in way breaks 1 or more of above more times can count.

it's naturally not problem if just right (and in general nicer use), not sites do.

just example here's screenshot how site spa , justifiedly (they have music player don't want interrupt page loads), broke basic browser function in way might not have thought of. trying find song listened couldn't remember exact title... because of spaness page titles weren't reflected in browser history.

soundcloud browser history screenshot


Comments

Popular posts from this blog

Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on project.Error occurred in starting fork -

windows - Debug iNetMgr.exe unhandle exception System.Management.Automation.CmdletInvocationException -

configurationsection - activeMq-5.13.3 setup configurations for wildfly 10.0.0 -