This is cool and I don't mean to disparage the work that went into it, but at the same time I hope nobody actually uses it because just plain old vertical scrolling web pages are way more practically usable.
I think so to, but usability research done by a partner company of ours showed, to their and our surprise, that "ordinary users" prefer this page turning effect.
Turn.js - The page flip effect for HTML5
71–80 of 82 posts
Re: Turn.js - The page flip effect for HTML5
#72Earlier quoted context omitted.
> There are some specific cases where it might make sense to do it Like when your client demands it and you give in? I've used pageflip in the past and grew to abhor it. It's only quality is the cool factor, which we got over 6 years ago. I hate magazines that use it for their "digital" version.
Yeah, this script reminded me of an old photo-flipbook program that wasy available a long time ago (I think for Windows 3.1x). At first the effect seemed "neat", but after browsing hundreds of photos with the same effect the novelty weared out and it became cumbersome.
I find the same with virtually all animations on phones and other UIs. If it can show me what I want a smidgen quicker by not animating then it gets disabled.
Re: Turn.js - The page flip effect for HTML5
#73Earlier quoted context omitted.
Doesn't happen here; the page doesn't change when I move the mouse over the "next page" corner, other than the folding up of that corner. Everything remains crisp. What browser did you use?
The blurring happens in Firefox 10. It also makes the whole 'page' shift a couple pixels. It's really disruptive and ruins the whole effect.
Re: Turn.js - The page flip effect for HTML5
#74Earlier quoted context omitted.
> There are some specific cases where it might make sense to do it Like when your client demands it and you give in? I've used pageflip in the past and grew to abhor it. It's only quality is the cool factor, which we got over 6 years ago. I hate magazines that use it for their "digital" version.
There's also a reason it is used. A typical magazine layout does not translate well on an vertical scrolling page. This is one solution to a conversion problem. There's not always a "BEST" solution to that kind of thing. There are trade-offs no matter what you choose to do. However, providing different ways to view the same information is usually a good practice. I wonder what is the "user" perspective on this. I am…
Re: Turn.js - The page flip effect for HTML5
#75Earlier quoted context omitted.
> There are some specific cases where it might make sense to do it Like when your client demands it and you give in? I've used pageflip in the past and grew to abhor it. It's only quality is the cool factor, which we got over 6 years ago. I hate magazines that use it for their "digital" version.
>Like when your client demands it and you give in? Someone in this thread gave a great example: their company makes "photobooks" and this effect is used in the preview before you order to make it feel more "real". I think that's a legitimate use. Obviously, magazines that just plaster pieces of the PDF on and then demand the page flip are not usable or accessible, but there are other uses for something like this.
My comment was related to the (common) case where someone thinks this is the best way to adapt printed content to the web, and that people actually want virtual magazines instead of something suited to screen reading/interaction. Fortunately that appears to be a dying mindset.
Re: Turn.js - The page flip effect for HTML5
#76Solid effect but not a fan of how it breaks the back button.
Re: Turn.js - The page flip effect for HTML5
#77Earlier quoted context omitted.
>Like when your client demands it and you give in? Someone in this thread gave a great example: their company makes "photobooks" and this effect is used in the preview before you order to make it feel more "real". I think that's a legitimate use. Obviously, magazines that just plaster pieces of the PDF on and then demand the page flip are not usable or accessible, but there are other uses for something like this.
Of course, using a paper simulator to showcase printed material makes complete sense :) My comment was related to the (common) case where someone thinks this is the best way to adapt printed content to the web, and that people actually want virtual magazines instead of something suited to screen reading/interaction. Fortunately that appears to be a dying mindset.
Re: Turn.js - The page flip effect for HTML5
#78This is cool and I don't mean to disparage the work that went into it, but at the same time I hope nobody actually uses it because just plain old vertical scrolling web pages are way more practically usable.
I think so to, but usability research done by a partner company of ours showed, to their and our surprise, that "ordinary users" prefer this page turning effect.
Case in point: touchscreens replacing dials and switches in cars -- cool right? So flexible! But no, in reality they suck and you can't use them at all without becoming a danger to yourself and everyone else on the road. Physical dials and switches are way better because they can be controlled without actually looking at them. But this is something that takes a while to become obvious to people (in fact, car makers are still fucking this up).
Re: Turn.js - The page flip effect for HTML5
#79Earlier quoted context omitted.
There's also a reason it is used. A typical magazine layout does not translate well on an vertical scrolling page. This is one solution to a conversion problem. There's not always a "BEST" solution to that kind of thing. There are trade-offs no matter what you choose to do. However, providing different ways to view the same information is usually a good practice. I wonder what is the "user" perspective on this. I am…
I agree, but the trade-offs depend on your goals, and for each of those there is a best solution. If you want to provide a good reading experience on the web, you have to use appropriate layouts.
This isn't necessarily true. For instance, if A and B are each measurable characteristics of potential solutions and your goal values A and B equally, if all other characteristics of solutions X and Y are equal, but X={A:2, B:7, ...} and Y={A:7, B:2, ...}, then X and Y are equally "good" solutions according to your goal.