It took me > 60 seconds to figure out how to turn the page. My feedback is this: I hate it. When I'm using my ipad, every blog that has onswipe enabled leaves me frustrated. The UX feels slow, choppy, and unnecessary.
I don't understand what problem is trying to be solved. Browsing web pages on the ipad is a pleasant experience. I can scroll with my finger. With onswipe, I can no longer scroll with my finger. Why was that a problem? that's not a problem. It doesn't need solving. Please tell us explicitly the value you are trying to add, because I cannot see it.
While I am glad people are experimenting with new UI metaphors and reading experiences, every product I've seen from Onswipe has been, as you say, slow and choppy. And not just a little slow or a little choppy, I'm talking unusably so, often to the point where it crashes my browser.
I get the impression they aren't testing this stuff at all on the first generation iPad.
Protip: Often on sites using OnSwipe (or similarly intrusive mobile views that don't really help), it's hard to find the option to turn it off, or the option when chosen doesn't persist.
So, I usually switch to browsing such sites inside the excellent iCab Mobile browser, with its User-Agent changed to indicate desktop Safari. Usually works – though there is a report in sibling thread that OnSwipe, in its quest to infuriate, sometimes uses some other iPad-detection mechanism.
I don't understand what problem is trying to be solved. Browsing web pages on the ipad is a pleasant experience. I can scroll with my finger. With onswipe, I can no longer scroll with my finger. Why was that a problem? that's not a problem. It doesn't need solving. Please tell us explicitly the value you are trying to add, because I cannot see it.
reply