You know what's even better? Having server-side rendering that delegates to the client on load so you can avoid this kind of thing all-together. Looking at you react, stay awesome!
PleaseWait.js – Show your users a beautiful loading page while your app loads
61–70 of 82 posts
Re: PleaseWait.js – Show your users a beautiful loading page while your app loads
#62Why 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…
> by simply updating the loading HTML to show a number percentage
Note, this isn't always easy to do. If you use on-the-fly gzip compression (which is how most people set their nginx or whatever up), you won't get a Content-Length, so you can't show progress.
Re: PleaseWait.js – Show your users a beautiful loading page while your app loads
#63I used to be a Flash developer, now a Javascript developer. Everything that was raised as an issue with flash (except web's open nature) is now an issue with Javascript development today. Preloaders, skip intros, single page apps, browser back button issues, SEO incompatibility. all of it. loving this.
Re: PleaseWait.js – Show your users a beautiful loading page while your app loads
#64This pattern really ruins the experience for me. I know of a few apps that while loading will show an inspirational quote or some other distraction. For me it cheapens the experience. I understand scaling is #hard but there are better experiences than a loading screen that can make the end user experience much better.
Re: PleaseWait.js – Show your users a beautiful loading page while your app loads
#65Earlier quoted context omitted.
So you don't think UI/UX design can be beautiful? I Agree that it takes alot for me to use the word "Beautiful" in the context of software aka Code. But design isn't code. And although I do think this library is supporting the case of being lazy and not optimizing your code and load times. I do think its beautiful. Just my 2 ¢
Can UI/UX be beautiful? Sure. Are things that self-proclaim to be beautiful actually beautiful? Very rarely. The term is wildly overused.
Agreed. Beauty is in the eye of the beholder of course, but the word (along with "passion") is almost always gratuitous when used in the context of software or software development.
Do we have "How to be passionate about beautiful UI in 7 days, for dummies" yet?
Re: PleaseWait.js – Show your users a beautiful loading page while your app loads
#66Jesus, we've sure defined down "beautiful" haven't we.
Re: PleaseWait.js – Show your users a beautiful loading page while your app loads
#67"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.
I've participated in internet communities where people say these things to each other, and while it seemed insincere to me, I didn't worry about it much. It wasn't until I saw little fights and disagreements erupt that I really solidified my distaste for it; these people were just as nasty as anyone else on the internet, they just happened to cover themselves with a paper-thin veneer of sweetness.
Re: PleaseWait.js – Show your users a beautiful loading page while your app loads
#68Earlier quoted context omitted.
Wow, I never looked at that page before. It's creepy from the top: you look lovely today, btw. to the bottom: you need help Well, which is it? Do I look lovely, or do I need help? What possible business is it of yours, dear npm? And what about the person who just suffered a facial injury and is very aware of how unlovely they look at the moment? At least Slack rotates through a few different sayings that tend to be g…
> Was the more likely outcome that I would fail to install it? Hilarious. Well, I think all these things are suspicious and maybe (I don't know) even bad in nature, but they have levels of badness, "you look lovely today, btw" is considerably worse than any form of birthday congratulations -- although I'm also suspicious of the second, which, here in Brazil, is a little more common thing to say than "happy birthday"…
http://en.wikipedia.org/wiki/Uncanny_valley
It'll get good and comforting soon enough..
Re: PleaseWait.js – Show your users a beautiful loading page while your app loads
#69Very nice and exactly what I needed.
Re: PleaseWait.js – Show your users a beautiful loading page while your app loads
#70Earlier quoted context omitted.
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…
I agree with you on this. There's a large subset of the web development community who are shifting towards building desktop applications with web technology (atom-shell, node-webkit, brackets-shell, etc.). In a lot of these cases, the app bootstrap process is actually loading data/content that is required for proper app functionality. Desktop apps commonly use loading screens on boot to indicate this process (Photosh…
The point is: most of these applications (say, Photoshop, Gimp, Eclipse, OpenOffice, probably others) are things that you load once to work with them for a couple hours, and don't mind when they consume a lot of your system resources.
If you look at web applications, Google's music app ("My Music" in Google Play) uses a load screen (complete with progress bar) because it's seriously bloated, while Amazon's Cloudplayer just loads and does its thing (which is, playing music).
Needing a load screen is a sign that your app is not, or aims at not being, a Web app anymore - in the sense that you'd also want to loosen the other restrictions - give it its own window, possibly have local file storage or FS caching, etc.; In that case, something like TideSDK ( http://www.tidesdk.org/ ) may come in handy to deliver a desktop app to power users that is based on the same codebase. And, maybe you'd still want a web app that is functional and lean. (As an example for two apps with non-identical possibilities, Google's My Music allows you to change song metadata on desktop browsers but not in the Android app - yet another sign that My Music is meant as a desktop-y app).
In many cases it can be a sign of hubris or lazyness that you cannot get rid of the bloat. Be real and think whether your users actually enjoy waiting that time, since they'll be doing it more often, on machines with less resources and/or slower connection, than yours.