The scrolling issue on iPhone is the worst. The sheer 'slowness' is god awful. It is by far my biggest complaint. I have to swipe 20 times to get to the bottom of a long page. Scroll to top by tapping the status bar is the best feature! Wish they could do it for both top and bottom. Android is the best at scrolling, with Windows Phone in between the two. BTW, the checkerboarding is still there on the iPhone, something I no longger see on the Nexus 5 and Lumia 1520.
Everybody has their preference when it comes to scrolling. I no longer own a single iOS device. Only Nexus devices. And I can still say I prefer iOS scrolling.
A natural flick in iOS takes you the right amount if you are reading an article. The same flick in Android takes you way too far. If you are reading an article, you just scrolled past what you want to read. In Android, I rarely find myself flicking. 90% of the time I am doing the tap, hold, drag, and let go. Doesn't feel as natural as iOS. And the feel of your device is an important thing to consider.
Sure, a single flick in Android takes you further. But so what? What purpose does that serve? If I am reading an article it does me no good. If I need to get to the top of the article, iOS does it quicker with a single tap.
Another thing to consider is that iOS scrolling is actually intelligent. iOS recognizes a long article. If it recognizes a long article and sees you doing multiple flicks, it will dynamically speed up scrolling. Take this video as an example:
(Web page was zoomed in to simulate a longer article)
Now, lets analyze.
The first flicks are pretty slow. I imagine at first, iOS scrolls by a certain amount of lines in relation to force. Android does the same thing. The difference here is that the amount of lines to scroll in relation to force is larger on Android.
However, iOS soon recognizes the fact that I am trying to get to the bottom. So instead of continually scrolling X amount of lines, it begins to scroll by page percentage. The first flick doesn't go very far. The last flick goes nearly 25% of the entire page. What does that tell us? It tells us that iOS dynamically changes scroll speed based on what you are trying to do.
Lets say you come across a super long article on some new scientific discovery with hundreds if not thousands of comments. The page is going to be very long. For the sake of argument, lets say the article is so long that each flick only takes you 2% down he article on Android. That would mean that the first few flicks on iOS only take you like .2% (assuming a 10-1 Android-iOS scrolling ratio) down the page. So the amount of lines covered on Android is much higher than iOS. However, by the 10th flick on Android you would have only gotten 20% of the entire article, requiring 40 more flicks. However, on iOS after about 6-7 flicks it no longer scrolls based on lines, but percentage. In which case, you would be able to reach the end of the article within 10 total flicks on iOS whereas Android requires 50 total.
Basically what I am saying is that iOS can dynamically change scroll speed based on what you are doing. Not only can you get to the bottom of a super long article quicker, you can also get to the top with 1 tap. And a natural flick takes you a better distance for actually reading (IMO).
As for the checkerboard thing on iOS, I can't say. That video was from my iPad 3 and I took that video a while ago. But I can say that on my Nexus 7 (2013) and my Nexus 5, scrolling on pages suffers 2 major downfalls. The first is that scrolling quickly won't cause checkerboards, but will blank out on the content, which is essentially Androids version of the checkerboards. Also, because of Androids touch input lag, when scrolling in rapid succession I notice the content briefly stopping. For example, I will scroll quickly, the content will fly up, and immediately go to do a second flick. In rapid succession, every time I do another flick, I notice all the content stopping for a brief moment in time. It is kind of like SCROLL-stop-SCROLL-stop-SCROLL-stop, but just really fast, if that makes sense. This never happened on iOS.
But again, I don't own any iOS devices anymore. So really, I am comparing current Android with iOS on iPad 3 and iPhone 4S. Now that I think about it, that certainly doesn't help Android's case