4 ms·

I just tested. I loaded a web page I'd bookmarked on my home screen. The top part of the screen shows the loading bar. The bookmark button is still a bookmark.

I just tested. I loaded a web page I'd bookmarked on my home screen. The top part of the screen shows the loading bar. The bookmark button is still a bookmark. When I click a link, it doesn't change into a stop button until the actual page has started loading. But it looks like loading the bottom menu shows me stop consistently. The "you're just not used to it" argument constantly rears its head when people criticize usability. That's why I was careful in pointing out the deficiencies. I can understand that the keyboard takes adjustment. Notice I didn't criticize the android "word menu" auto-complete. The poor scrolling is a technical failure. Nobody wants jerky scrolling. And the lack of pinch-and-zoom has repeatedly been covered as a patent issue, not a UI choice. "You're just not used to it" is extremely dangerous reasoning.

crux_ 17y ago
> "You're just not used to it" is extremely dangerous reasoning. I wasn't quite trying to say exactly that, at least not in a blanket manner. But, let's take scrolling as an example: I haven't noticed that the android scrolling is jerky, not even a little bit. This is probably because I've never used something as silky as the iPhone. ((Or, perhaps, if I did try an iPhone, I would find its scrolling too smooth with no satisfying 'thump to a stop' at the end of a scroll or 'jump into motion' at the beginning.)) In other words, it's not "You're just not used to it" -- it's "without the other point of reference, would you even notice it?"
- sandofsky 17y ago
  Your line of reasoning flawed, in that it can be applied to anyplace where one option surpasses the other. Without a car as a point of reference, would you notice a horse and buggy are so bad? Yes, I would live with the scrolling on the Android, because I'd say to myself, "That's pretty good for a mobile phone." However iPhone 1.0's scrolling was vastly superior to today's Android. That's over two years ago. I think it's safe to declare iPhone 1.0 as the bar. And, again, I'm not criticizing the thump-to-a-stop behavior. I'm criticizing the frame rate and responsiveness.
  - crux_ 17y ago
    I'm not going to say you're wrong, because I'm not really in a position to argue that. However, we're talking about Volkswagen vs BMW here, not horse and buggy vs car.

crux_ 17y ago

> "You're just not used to it" is extremely dangerous reasoning. I wasn't quite trying to say exactly that, at least not in a blanket manner. But, let's take scrolling as an example: I haven't noticed that the android scrolling is jerky, not even a little bit. This is probably because I've never used something as silky as the iPhone. ((Or, perhaps, if I did try an iPhone, I would find its scrolling too smooth with no satisfying 'thump to a stop' at the end of a scroll or 'jump into motion' at the beginning.)) In other words, it's not "You're just not used to it" -- it's "without the other point of reference, would you even notice it?"

sandofsky 17y ago
Your line of reasoning flawed, in that it can be applied to anyplace where one option surpasses the other. Without a car as a point of reference, would you notice a horse and buggy are so bad? Yes, I would live with the scrolling on the Android, because I'd say to myself, "That's pretty good for a mobile phone." However iPhone 1.0's scrolling was vastly superior to today's Android. That's over two years ago. I think it's safe to declare iPhone 1.0 as the bar. And, again, I'm not criticizing the thump-to-a-stop behavior. I'm criticizing the frame rate and responsiveness.
- crux_ 17y ago
  I'm not going to say you're wrong, because I'm not really in a position to argue that. However, we're talking about Volkswagen vs BMW here, not horse and buggy vs car.