Linked by Thom Holwerda on Mon 19th Dec 2011 20:11 UTC
Google Once upon a time, in a land, far, far away, there were two mobile operating systems. One of them was designed for mobile from the ground up; the other was trying really hard to copy its older, desktop brother. One was limited in functionality, inflexible and lacked multitasking, but was very efficient, fast, and easy to use. The other had everything and the kitchen sink, was very flexible and could multitask, but had a steep learning curve, was inconsistent, and not particularly pretty.
Permalink for comment 500558
To read all comments associated with this story, please click here.
by kllrnohj on Mon 19th Dec 2011 20:44 UTC
Member since:

"As a final example: some applications use proper bounce-back when scrolling, while others just come to a dead stop. I have no idea why some applications decide this is a good idea; heck, even several Google applications do not implement bounce-back! There's no excuse for not implementing bounce-back scrolling in your Android application when Android itself clearly supports it. The fact that Android even gives you the option is bad enough as it is."

This is actually not true. Bounce-back scrolling is not in Android, which instead uses an edge glow. That is something Samsung bolted on, which is why it doesn't work everywhere. The inconsistency you are seeing is the result of TouchWiz.

Reply Score: 6