Then we're in agreement! There are a TON of features/complexity in Kindle; combine that with e-ink being a clumsy display technology to combine with a touch screen and we find ourselves in the situation that we're in.
(Note that I totally understand why e-ink was combined with a touchscreen for Kindle. Give someone a screen these days and they'll try and touch it, for better or worse)
From some of the discussion here, it looks like the Kindle 3 was a pretty neat idea. (As the author suggests)
+1!
I loved my original non-touch Kindle. Newer paperwhite is nice, but touch screen is a disadvantage for me. I rarely interact with it and older Kindle with buttons was perfectly fine for those tasks. Yet it sucks when pages are scrolled or next is selected if I accidentally touch/hold screen in a wrong way.
I’m seriously considering spending extra $$$ to getter expensive version purely to get away from touch screen. But I’m worried that it wouldn’t allow me to lock the screen while reading with hardware button :(
Yes, the modern Kindle really suffers for this. I originally had a Kindle 3. It did everything I wanted except for the horrible, glaring oversight that the keyboard didn't have numbers, when better than 90% of my interactions with that keyboard were jumps to a numeric location.
I now have a Kindle Oasis, and in most respects other than that one the UI is a big step back. I can no longer remove dust from the screen by touching it. (Actually, I still do this, but it wastes a bunch of my time by unavoidably performing one to four page turns when I do.) Attempts to call up the menu frequently turn the page instead. Jumping to a location is now a ridiculously long workflow involving summoning the menu, selecting "go to", and then selecting "page or location", because the table of contents has been stuffed into the "go to" menu instead of being part of the book.
Normal functions should be easier to reach than rare functions, but not so easy that they happen constantly regardless of whether the user wanted them. The Oasis somehow manages to fail at both of those points.
How often do you struggle with the interface once you've learned it? I agree that the current Kindle interface isn't the most intuitive, but to me that's a non-issue. I've long since learned how to interact with the Kindle, and now that that initial learning is complete, the interface does an excellent job allowing me to do what I want.
Occasionally my Kindle jumps forward or backwards by a large number of pages, and I've yet to figure out why. It happens when I put it down to talk to someone, someone a shortcut of jump around gets activated. I am not sure how to quickly and rapidly jump around the text on purpose, but I do dread it happening by accident far too often.
I pull up the UI with the page preview and skim around using that, but obviously there is another interaction method that allows for the same thing. Rather than learning it, I want to disable it, since it causes me nothing but frustration.
If I were designing the Kindle, I think I would add a button that brings up the UI and have screen swipes turn the page and screen taps bring up something that makes sense for whatever was tapped on (like a dictionary or X-ray feature).
Nope. I hate swiping. I expect my e-ink screens to be free of ugly, distracting fingerprints, and I generally find physical buttons to be more accurate, precise, and intuitive than swiping and other gestures.
You must not be a VIM user. I've been using VIM for about 10 years now and I still make mistakes where I think I'm in one mode, but I'm actually in another. Just because you've "learned" an interface doesn't make it easy to use.
I've been through that cycle personally until I got so annoyed that I either fixed it or stopped using it.
I originally had a huge footnote acknowledging that much of this is obvious and that the Kindle team is full of smart people who have data showing that maybe these aren't the best optimizations. I'm just describing my expectations from having used Kindles for ten (??!) years coupled with having worked on designing digital reading interfaces for a similar amount of time. I'm certainly an edge case user.
Having seen my mother (edit: and, more pertinently: myself) struggle with her Kindle, I do think the interaction model is one-degree unnecessarily complex — all of those hidden spaces.
You could distill my whole piece to: This is a single purpose device that's been designed like a multi-purpose device.
Page turn buttons + menu button would all but eliminate any interaction ambiguity. And could be done quite beautifully.
Although I don't have access to any data, I think there might be a subset of casual users who would prefer the screen to do nothing when touched.