My gripe is the disappearing header that reappears at the slightest twitch of reverse scrolling. The behavior needs to work more like drag down to refresh: only reappear with a deliberate and significant scroll "up" (a drag down with the finger) or just stay at the very top where it belongs (it only takes one tap on mobile to get back there).
With most of them if you need to backtrack and read a few lines up, you have to scroll well past the point or the exact text you want to read gets covered by the header.
My theory is that analytics is to blame for all of this. You can track how many people clicked the button in your share header. You can't reliably track how many people left because of it (there could be a million reasons for leaving the page).
So your analytics shows an uptick in engagement by X%, and no clearly discernable downtick. So the header stays.
All it would need is an A/B test or two, but easier said than done...
The native iOS behaviour is to only do that when flicking (ie. scrolling and letting go). Didn't see anybody copying that yet. However, it makes a huge difference in usability.
I agree... I always move the current line to the top of the page for some reason. that's actually why I don't like most ebook readers because they are paginated.
interesting... most of my ebooks that I have opened in iBooks on the iPad are pdfs which don't have that option so I assumed they didn't have the scrolling option but I was able to do it with an actual ebook. It would sure be nice to have continuous scrolling on pdfs as well.
edit: iBooks on mac os doesn't have a continuous option.
With most of them if you need to backtrack and read a few lines up, you have to scroll well past the point or the exact text you want to read gets covered by the header.