I'd bet the double page turn bug would be tough to beat unless they limited the minimum time between page turns... or figured out where the ereader was getting bogged down.
I think what is actually happening is that for some reason the ereader is delayed in responding to the first touch causing the user to assume the initial touch didn't register and to then touch it a second time and cause the double page turn when the ereader catches up. Effectively, the only thing the ereader is doing wrong is delaying it's response to the first touch and the user is doing the rest.
|