3 ms·
I'm struggling with this (SPA vs no SPA), and think you are stating the obvious: overall experience the end customer is going to need and expect. data analysi
by Scarbutt 9y ago
I'm struggling with this (SPA vs no SPA), and think you are stating the obvious:
overall experience the end customer is going to need and expect.
data analysis, frequent order entry, or highly dynamic UX
The hard part is, how do you measure that? obviously some web apps need highly dynamic UX, a spreadsheet, some not, a blog, choosing between these two is easy.
But most web apps sit somewhere in the middle, I don't know the answer, but for example, how much will github users benefit from the experience of a SPA?
- ljoshua 9y agoGitHub actually straddles the line a little bit. You'll note that when browsing around through folders in a repo on GitHub that you get the faux loading indicator along the top, and then it shows the contents you're navigating to. Same with switching between code and issues, for example. But switch to a different repo and you get a full page refresh. For my company's product, we're much more on the side of a traditional server-side app, because users will send off a batch of information (their customers to open a line of communication with), and then wait for the responses to roll in. But the dashboard page where we show responses is a partial-SPA, similar to GitHub: new responses are loaded asynchronously, and you will soon be able to switch to different views of the data without a reload. It's a good balance for our application. I realize it's not answering your question about how to measure it, but hopefully it provides some anecdotes.