I'd say at most that it is not "new user friendly", rather than antagonistic to all users.
I'm only an occasional Kindle user, but I rarely make a wrong action using the hardware interface, and when I do, it's an unintentional long tap, and I have to cancel an unintended highlight.
Oddly, swiping is considerably faster than tapping. When you tap, there’s a brief delay before the screen starts scrolling – which is artificial, not just lag, because a quick swipe gesture (just brushing your finger against the screen) starts the same scrolling animation with no delay. Thus I’ve effectively been trained to always swipe.
As strange as this is, at least I wouldn’t call it antagonistic to new users, since the most efficient page-turning interaction is also the most intuitive one: most users will already be familiar with the swipe gesture from the rest of the OS, and will try to do it even without a visual affordance. (It’s also physically intuitive, even if the physical object being simulated is very different from an actual book.)
Of course, you can’t do fluid scrolling animations on an eInk display, so eInk Kindles lack the swipe gesture, leaving only the relatively-dubious tap regions criticized in the article. I agree that hardware buttons would be better there.
On the other hand, on iOS, Kindle is my favorite reading app for the sole reason that none of the others I’ve tried offer equivalent swiping functionality. Either they only offer a “page curl” transition style (iBooks), which looks cool but is more visually distracting, or they support swipe-to-slide but only as an atomic gesture: you do a complete swipe, and then the screen scrolls, without it letting you actually drag the page around first. (That just feels unnatural.)
My ideal Kindle model is as follows.
Hardware buttons:
Page forward
Page back
Menu
(Power/Sleep)*
>There are no affordances to the taps. No edges to the active areas. Nothing to hint at what might happen. This creates what I call a “brittle” interface — where one wrong tap sends you careening in an unknown direction, without knowing why or how you got there.
When I'm using an e-book reader app, I want the entire screen to be taken up with the text of the book I am reading. I quite like having tap zones to turn the pages and access a menu when I need it. I'd rather a tap than a swipe, actually. Unless I'm completely misunderstanding the quote above, I don't find this to be antagonistic in any way at all.