PleaseWait.js – Show your users a beautiful loading page while your app loads
pathgather.github.io
PleaseWait.js – Show your users a beautiful loading page while your app loads
1–10 of 82 posts
Re: PleaseWait.js – Show your users a beautiful loading page while your app loads
#2Is it just me, or does anybody else think that it's a problem that the world even needs this in the first place?
I expect splash screens and slightly longer load times from desktop apps... if I click on a link to something in my browser, not so much. TBH, if a page/app takes more than a second or two to load, I assume there's something wrong with it (or my net connection).
Re: PleaseWait.js – Show your users a beautiful loading page while your app loads
#3Click Here to Skip Intro
Re: PleaseWait.js – Show your users a beautiful loading page while your app loads
#4Is it just me, or does anybody else think that it's a problem that the world even needs this in the first place? I expect splash screens and slightly longer load times from desktop apps... if I click on a link to something in my browser, not so much. TBH, if a page/app takes more than a second or two to load, I assume there's something wrong with it (or my net connection).
Exactly. Splash screens are so 1995 - we need to be getting users to something useful as fast as possible.
Re: PleaseWait.js – Show your users a beautiful loading page while your app loads
#5Is it just me, or does anybody else think that it's a problem that the world even needs this in the first place? I expect splash screens and slightly longer load times from desktop apps... if I click on a link to something in my browser, not so much. TBH, if a page/app takes more than a second or two to load, I assume there's something wrong with it (or my net connection).
For SPAs, something like this can be quite useful for a few reasons: branding (see Slack's and Asana's cool examples), having in-app authentication on any page (see the login form example on the demo page), and yes, showing some sort of notification while a good bit of data loads in the background.
For the majority of sites, I agree this may be overkill, but if you have a SPA that needs to load a good bit of data on the user's first use of your app (and verify authentication), this can (hopefully) be useful.
Re: PleaseWait.js – Show your users a beautiful loading page while your app loads
#6Why 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.
Having a skeleton project for gulp (or any other system) that shows how to properly split big, non essential, components and lazy load them would go much further to ease developing big applications and smoothen UX.
EDIT: typos.
Re: PleaseWait.js – Show your users a beautiful loading page while your app loads
#7Is it just me, or does anybody else think that it's a problem that the world even needs this in the first place? I expect splash screens and slightly longer load times from desktop apps... if I click on a link to something in my browser, not so much. TBH, if a page/app takes more than a second or two to load, I assume there's something wrong with it (or my net connection).
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 these days) blocking the user's browser.
Re: PleaseWait.js – Show your users a beautiful loading page while your app loads
#8Is it just me, or does anybody else think that it's a problem that the world even needs this in the first place? I expect splash screens and slightly longer load times from desktop apps... if I click on a link to something in my browser, not so much. TBH, if a page/app takes more than a second or two to load, I assume there's something wrong with it (or my net connection).
Is it just me, or does anybody else think that it's a problem that the world even needs this in the first place?
I agree. If you need this, go back and look at what you're loading. Do you really need all that CSS? Does that Javascript really need to be executed? Do you need it just to get started? Do you really need 15 tracking cookies and a Flash bug?
Re: PleaseWait.js – Show your users a beautiful loading page while your app loads
#9Why 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 regard :)
Re: PleaseWait.js – Show your users a beautiful loading page while your app loads
#10Is it just me, or does anybody else think that it's a problem that the world even needs this in the first place? I expect splash screens and slightly longer load times from desktop apps... if I click on a link to something in my browser, not so much. TBH, if a page/app takes more than a second or two to load, I assume there's something wrong with it (or my net connection).
For SPAs, something like this can be quite useful for a few reasons: branding (see Slack's and Asana's cool examples), having in-app authentication on any page (see the login form example on the demo page), and yes, showing some sort of notification while a good bit of data loads in the background. For the majority of sites, I agree this may be overkill, but if you have a SPA that needs to load a good bit of data on…
You missed the point. If you "need to load a good bit of data on the user's first use" you've already failed. I've been coding professionally for about 20 years now and the only reason i've ever seen for loading a bit of data on the initial hit, is that the developer didn't spend the time to think about how to load the necessary pieces incrementally, as they were needed by the user. Instead they designed a system that needed a whole pile of crap on startup even if the user didn't.