I worked with the guys who built this (we're a DC design studio) and can tell you that it doesn't gracefully degrade simply because it's not supposed to. As some people grasped, this was for a frontend conference where everyone would be expected to be running the latest and greatest browser. There's no guarantee it will work on your setup but when it does, it's a cool experience.
While the overall graphics and the general mechanism looks decent, the actual action of turning a page if very kludgy and glitchy. I found it difficult to get the pages completely turned since the book kept rotating a bit.
Another tiny nit: They don't need those "+" icon interactions. They could've just used the book rotation controls as-is. Popup books usually don't have buttons, at least not from my generation /getoffmylawn.
So I'll get down voted for this but it needs to be said: this is very cool and is a great proof of concept for the direction things are going. However, if you're promoting a commercial product, event, etc., you could have just used flash--it would be trivialish to implement, perform better, and have no cross browser issues--although no iOS to be fair...
As it stands, how many people will hit the site, see it's not working because they have the wrong browser version, and leave?
I can also confirm works on iOS (using iPad), has a couple of spacing glitches, however page turning animation is extremely smooth, an the actual pop-ups are exact same as on desktop, no problem and performs like a champ.
One thing to consider is that their target audience is attendees of the Front-trends conference, a conference specifically for front end developers. I think it's a safe bet that a majority of the traffic will have a compatible browser.
Ha, excellent point. Judging by some of the comments here, much of their traffic may not have a compatible browser version after all, but I'd imagine that they still have a higher tolerance for that sort of thing in the name of advancing the field.
This is a terrible attitude. Among the other things that have been pointed out, not all desktop browsers have Flash. For example, no computer I own has Flash installed on the system. If I need Flash for some reason, I keep Chrome around, but it has to be a damn good reason to bother with.
Obviously they didn't apply it here fully, but it would have been possible for them to reuse their text divs on text-only browsers, drop their svgs for some prerendered raster graphics on SVG-less browsers, use their SVGs but have them render flat on 3d-transform-less browsers, have static 3d copies of each page if JS isn't available but 3d was, etc., etc.
It's even possible for established sites to collect statistics on combinations of available browser features, estimate ROI vs. development effort and decide which combinations beyond the least-common-denominator are worth coding for and slowly roll them out one at a time.
That's not the point of the site. It's an annual meetup where people push the limits of the latest and greatest web technologies. The people visiting it will be web designers/developers, not Jane Doe who only visits facebook.
works "meh" in firefox 14.01. You can browser, but it stutters and you don't see the nice pop-up effect. It just appears when the page is turned far enough.
Seems like they should have some sort of fallback to users of IE can at least get some information about the conference
Very neat effect though. Is this based on actual folding math or is it just a series of neat animations? Like could this be built into a sort of popup book framework?
I'm on chromium 22 on linux. Maybe you need to go to the about:flags page and enable "override software rendering list" for your browser to use the proper acceleration on the page. That's what I had to do for my old Inspiron 1545.
I find it interesting that this works, or doesn't. Based on these "Micro-Version" differences as well as whole version differences. What are the key differences? Is it actually chrome or some other system level difference?
3D transforms is nearly completely dependent on the GPU of your machine. about:gpu in Chrome will give you more information about the differences and capabilities of your machine. In some cases, old drivers are too unstable to support and so they're blacklisted by Chrome.
Gah this helped me a lot, thanks. about:gpu told me my WebGL was disabled in about:flags... which it was. Not sure how that happened as that's been annoying me forever.
Followup on how it was built here: http://coding.smashingmagazine.com/2012/04/17/beercamp-an-ex...
Full repo here: https://github.com/nclud/2012.beercamp.com