View Single Post
Old 07-22-2012, 11:42 AM   #3
MisterMax
Enthusiast
MisterMax is a jewel in the roughMisterMax is a jewel in the roughMisterMax is a jewel in the roughMisterMax is a jewel in the roughMisterMax is a jewel in the roughMisterMax is a jewel in the roughMisterMax is a jewel in the roughMisterMax is a jewel in the roughMisterMax is a jewel in the roughMisterMax is a jewel in the roughMisterMax is a jewel in the rough
 
Posts: 25
Karma: 7365
Join Date: Jul 2012
Location: Italy
Device: 2 Kobo Touch
Quote:
Originally Posted by murg View Post
Why they aren't using the time when you are reading a page to pre-process the most likely next event (page forward) is a mystery to me.
I'm totally with you. Thit is the first thing i thought when I saw this slow page turn bug.
They should simply pre-render the next/previous page in a buffer, and show it when the user turn page (and then prerender the next page...)
This will make for near-instantaneous page turn, without any added cost.

I'm a software dev, so I know that prerender a page is not something you can implement in some hours of work... but the benefit for the user experience will be huge!
MisterMax is offline   Reply With Quote