Flings are definitely quite a bit different from regular scrolling in being much less fine grained. And that’s for good reason: with a high velocity you can go really fast through a scrolling view.

Unless you want to take the approach that any fling should move immediately to the final state of that direction, I think the approach you’ve chosen seems reasonable given the limitations of the API at the moment.

I know improving the behavior of flings is something that the Android framework (and Support Library) team definitely wants to do at some point.

Glad you liked the post and good luck!