Re:How to avoid common SPA pitfalls when using third-party p...
by samizdatum on Tuesday January 26, 2016 @05:37PM
(#10976774)
SPAs don't need to have horrendous UX?
Re:How to avoid common SPA pitfalls when using third-party p...
by blhack on Tuesday January 26, 2016 @07:06PM
(#10977259)
Sure they don't, but saying that you are going to force logically separate pages onto a single page is starting from a point of bad UX and trying to dig yourself out of it.
Re:How to avoid common SPA pitfalls when using third-party p...
by samizdatum on Tuesday January 26, 2016 @07:56PM
(#10977489)
In theory, the only irreducible UX distinction surrounding logically separate pages in a traditional website vs a SPA is that the SPA doesn't do the full postback, which is arguably a better UX.
Sure, in practice many SPAs might be subpar, but then the debate shifts to "are SPAs are difficult to implement correctly," rather than "SPAs for blogging engines (necessarily) creates horrendous UX". There are existence proofs of well-designed SPAs with logically separate pages and excellent UX.
As an aside, someone who pattern matches on "SPA = horrendous UX" might not even notice a well-designed SPA, further entrenching their belief that SPAs are a Bad Idea from a UX perspective!
Re:How to avoid common SPA pitfalls when using third-party p...
by fweespeech on Tuesday January 26, 2016 @05:42PM
(#10976816)
SPAs for situations where they are not needed are horrendous UX in and of themselves due to the usability issues for power users that manage JS execution via browser plugins. [e.g. uBlock]
Re:How to avoid common SPA pitfalls when using third-party p...
by samizdatum on Tuesday January 26, 2016 @05:57PM
(#10976901)
Saying an application has a "horrendous UX" because you refuse to run its code seems strange to me.
You could disable CSS and images and call the result ugly, but I don't think that entitles you to call the website ugly?
Re:How to avoid common SPA pitfalls when using third-party p...
by fweespeech on Wednesday January 27, 2016 @10:37AM
(#10980562)
> Saying an application has a "horrendous UX" because you refuse to run its code seems strange to me.
https://gds.blog.gov.uk/2013/10/21/how-many-people-are-missi...
If you want to ignore 1% of the internet, you go right ahead.
Re:How to avoid common SPA pitfalls when using third-party p...
by samizdatum on Wednesday January 27, 2016 @08:14PM
(#10985230)
Fair enough, but I think that's a separate issue. If we go down this path, we'd be diluting the term "UX" to homeopathic levels. I wouldn't criticize an iOS-only app for bad UX because it ignores half the market.
I feel like SPAs are one of the most abused concepts on the internet right now.
A cloud-based 3D modeling software? Yeah, that definitely needs to be some form of SPA.
Your twitter clone, blogging engine, etc. not only doesn't have to be an SPA, but shouldn't be one because it creates horrendous UX.