I like the presentation and I understand the reason why people would want to use this thing.<p>That said: Please.. Show static content first. Don't do the Blogger thing. That looks<p>- ridiculous<p>- stupid<p>- like Geocities did<p>In other words: For 'apps', games etc. this looks really neat. But a website, say a blog..., shouldn't need to show a progress indicator before any content shows up.
No, please, stop, don't do this.<p>This is a terrible UI experience. Note: I have been living and working with iOS 7 since the first beta. I know it's new and shiny to everyone else, but this is absolutely the worst thing to add to your site. It serves no functional purpose and just clashes with devices that do this natively.
Or you could just speed your site up so you don't need to show someone a progress bar.<p>Or use Angular or Backbone and then you really don't need a progress bar.
This is fantastic, and surprisingly worked perfectly with my own super complicated browser-side AMD style module loader. I'm very impressed that it "just works" and seems like magic. Thank you so much for making this! (seems like everybody else is complaining, HNers are so ungrateful)
Good God, why would I ever want to see Loading Bars on a website.<p>If you can't front-load enough to give 100 bytes of text to read, don't bother answering my http request.
A team related to mine released a new UI for their software. It included a loading bar, of sorts, while it was loading a new page on the tool.<p>Users complained it was too slow.
They removed the loading bar.
Users stopped complaining it was slow.<p>I've since stopped trying to find new ways to add loading bars, and just focused on making my software faster.
It looks very pretty, but sadly my Macbook Air couldn't quite keep up with everything happening on the page. My ability to even scroll kind of stuttered to a stop.<p>Not sure why a loading bar needs to be so resource-intensive.<p>(Granted, I'm plugged into a high resolution display, but even so most sites I visit don't have issues like this.)
Here's my take: this is very valuable on sites that dynamically load new pages without an actual browser navigation (read: pjax).<p>It is not useful (and indeed it is an anti-pattern) for static sites in which case you'd want to just use the browser loading mechanism, that the user (hopefully) understands and is used to.
This is just like NProgress except even better and easier to use - thank you for sharing this!<p>The only caveat I encountered with this was that I had to update the z-index in the generated css file to "999999" for it to work with bootstrap. Notable, NProgress has the same incompatibility with bootstrap.
Strange enough, codrops recently published an article with very similar effects and styling: <a href="http://tympanus.net/codrops/2013/09/18/creative-loading-effects/" rel="nofollow">http://tympanus.net/codrops/2013/09/18/creative-loading-effe...</a><p>I see the article was published on the 18th, and hubspot created the repo on the 11th, so I wonder if this was just a coincidence. Either way, nice work
Those interested might also be interested in a previous discussion on a similar progress bar.<p><a href="https://news.ycombinator.com/item?id=6246183" rel="nofollow">https://news.ycombinator.com/item?id=6246183</a>
Looks great - works great! Thank-you!<p>Notes...
To get it over the bootstrap navbar I z-indexed to a million.
The ajax calls on my site seem to happen too fast to invoke. Fast pageloads are the benefit of no traffic!
It doesn't seem to work with Firefox 25 + Ghostery, I don't see a loading bar and all the examples are empty white boxes. Disabling Ghostery it works properly.
I'm actually very curious on how they build in the color picker into the site to designate the site's colors. Anyone have any knowledge on this?