"You look nice today". This habit of saying horribly false compliments to the user is an awful trend that is affecting programmers everywhere. See https://www.npmjs.com/login , for example.
Like the AMC theatres pre-show messages where it says something along the lines of "Thank you for being _absolutely amazing!_"
Makes me cringe SO HARD every time. Why are we telling people they're amazing for existing? Haven't we identified the issue with much of today's youth is that their egos were often overinflated by their parents, teachers, etc, leading to problems of entitlement and whatever else that entails?
Using PleaseWait to actually show progress can be achieved by simply updating the loading HTML to show a number percentage, but we may update the API to make this easier in the future. And I agree that a skeleton project to show proper modularization of different components would be great! Our blog just started an Angular series, so we'll try to write one on how we split up our large Angular enterprise app in this re…
But it's missing the point - just like other comments said - if you need this you're doing it wrong. I sure was guilty of big sites just as much as the next guy. It just saddens me that insted of promoting what we've learned it the past years and applying to current projects we're doomed to repeat bad UX from before.
Maybe you're right, but I certainly think there are some valid cases where this could be useful. I'm not saying use it in every project, or use it as a workaround to a larger architectural issue, but if you have a single page app that does not render templates on the server, showing something like this while you make a few AJAX calls and compile the data returned into your client-side templates isn't the worse thing in the world. Slack and Asana do similar things, and I would hardly say that their engineering teams did a ton wrong. We actually built this because we're customers of both and enjoyed the screens they showed, so we wanted to see if we could make a generic library that others could use to do the same.
Why is this any different than Flash preloaders just a moment ago? And even worse - it doesn't show any progress so there isn't any user feedback. Every (bad) pattern seems to repeat itself. Just using current-cool-tech. I would much more appreciate that dev time would be put into a framework that allows graceful enchancement by deferring loading more heavy components and to allow user to interact with the site ASAP.…
Using PleaseWait to actually show progress can be achieved by simply updating the loading HTML to show a number percentage, but we may update the API to make this easier in the future. And I agree that a skeleton project to show proper modularization of different components would be great! Our blog just started an Angular series, so we'll try to write one on how we split up our large Angular enterprise app in this re…
Ofc a blog describing your experience would be just that knowledge promoting that i have in mind so kudos for that (and i'll be keeping an eye for it because it is a hard problem to get right).
Certainly, with web applications you would want the least amount of latency possible. This is a normal UX scenario -- as you indicated, there are factors which can simply be out of the hands of the application such as network connectivity. In cases like that, indicating to the user that something is happening makes for a better experience than not doing anything, or in the worst case (which certainly shouldn't happen…
Not realy. A user with a slow connection will know that and wait (because the problem will be global). Adding a preloader is just bloat that will make the site load even longer (and just piss off the user as he'll know that some of his scare bandwith was lost on the shiny spinning wheel).
Aside from the reality that a user won't always know their connection is slow / has slowed (particularly when it comes to bad routing between server and client), this is also typically used in cases where you are utilizing XHR.
Given that they're done in the background, the browser won't indicate them being made outside of dev tools. If they're asynchronous, again ideally they will take place as quickly as possible. This is unfortunately not something that can be relied upon.
"You look nice today". This habit of saying horribly false compliments to the user is an awful trend that is affecting programmers everywhere. See https://www.npmjs.com/login , for example.
Slack does this, Resource Guru as well. There's probably a lot more. I don't really mind, I think it's a nice touch.
Why is this any different than Flash preloaders just a moment ago? And even worse - it doesn't show any progress so there isn't any user feedback. Every (bad) pattern seems to repeat itself. Just using current-cool-tech. I would much more appreciate that dev time would be put into a framework that allows graceful enchancement by deferring loading more heavy components and to allow user to interact with the site ASAP.…
No need to be dogmatic, there are valid reasons to use these.
For example, we have some heavy reports that take a few seconds to load, so we show a screen similar to this while we crunch the numbers.
"You look nice today". This habit of saying horribly false compliments to the user is an awful trend that is affecting programmers everywhere. See https://www.npmjs.com/login , for example.
Like the AMC theatres pre-show messages where it says something along the lines of "Thank you for being _absolutely amazing!_" Makes me cringe SO HARD every time. Why are we telling people they're amazing for existing? Haven't we identified the issue with much of today's youth is that their egos were often overinflated by their parents, teachers, etc, leading to problems of entitlement and whatever else that entails?
I suspect it's because people feel better about themselves and have a happier outlook when they receive compliments. These warm fuzzies are associated with the product / setting, positively affecting people's opinion of the service.
I'm not sure why you're confused -- is it because things aren't the way that you think they should be? To me, the explanation above is pretty concise and fits the situation neatly.
Why is this any different than Flash preloaders just a moment ago? And even worse - it doesn't show any progress so there isn't any user feedback. Every (bad) pattern seems to repeat itself. Just using current-cool-tech. I would much more appreciate that dev time would be put into a framework that allows graceful enchancement by deferring loading more heavy components and to allow user to interact with the site ASAP.…
No need to be dogmatic, there are valid reasons to use these. For example, we have some heavy reports that take a few seconds to load, so we show a screen similar to this while we crunch the numbers.
What are your thoughts then about putting only that region of the page behind some kind of loading/awaiting indication?
My issue with whole-page takeover loaders is that they lose your control and spatial sense of the app. You can't, for example, page away if you decide the report is taking too long to load, or you went to the wrong section of the site when hunting around for a piece of information.
But it's missing the point - just like other comments said - if you need this you're doing it wrong. I sure was guilty of big sites just as much as the next guy. It just saddens me that insted of promoting what we've learned it the past years and applying to current projects we're doomed to repeat bad UX from before.
Maybe you're right, but I certainly think there are some valid cases where this could be useful. I'm not saying use it in every project, or use it as a workaround to a larger architectural issue, but if you have a single page app that does not render templates on the server, showing something like this while you make a few AJAX calls and compile the data returned into your client-side templates isn't the worse thing…
Asana's absurdly long load time was one of the main reasons I was glad to stop using it. It's definitely not something I would considered well implemented.