re: Some questions about SPA UX VIEW POST

TOP OF THREAD FULL DISCUSSION
re: Hey, thanks for the reply! Here are my thoughts: The user experience doesn't have much to do with SPA/non-SPA in this regard. It's just up to you...
 

I'm not UX expert though, what I was trying to say is that what you attribute to SPAs intrinsically to me seems it's more about UX issues than the technology itself.

Well, if I show a loader on every page, the distinction between an SPA and a server-rendered app vanishes. The 'smooth' transitions are definitely the part of SPA UX (please see the new section I added to my post: 'The Back button').

Well, it can still be faster even with that.

This is something I see on dev.to as well. If you're on an article and navigate to another one, when you hit Back, there's no communication between the client and server. What if someone has commented on the article while you were away? Does that get handled (and updated) via WebSockets, or not at all?

Don't know about the details of dev.to yet, but SPA doesn't mean you never ever hit the refresh the button though.

mobile.twitter.com AFAIK is more or less like that. If you go back and you end you in the homepage, the homepage will pile up the new tweets and push them at the top of the feed.

But keep in mind that not all SPAs are the same.

I'm still convinced what you highlighted in your post is more of a design/UX issue than a technology shortcoming :-)

Thanks for your comments. Yes, looks like I've made it appear like a criticism of SPAs than questions about UX. But I disagree that this is a pure UX question -- avoiding page reloads is impossible in a traditional app but is (almost always?) possible in an SPA so there's definitely UX difference arising out of technological differences.

But keep in mind that not all SPAs are the same.

That's a relief to hear. So, my SPA can have spinners on every page, whether you navigate away from it or to it? 😊

code of conduct - report abuse