When using a NestedViewList and letting go of a view it will slide back according to how reapp-scroller works (which is basically just Zynga scroller).
But, on iOS when you "let go" of a View that is mid-swipe, it snaps back much more quickly. This is doable, but would require for the scroller to support dynamically settable speeds for "paging". So once a drag starts we could set "pagingAcceleration" to a fast value. Or just have that set in general.
Another piece it needs (should be another ticket on reapp-scroller) is dynamic animationduration in general, because back animations on iOS are 450ms and forwards are 550 (or so).
When using a NestedViewList and letting go of a view it will slide back according to how reapp-scroller works (which is basically just Zynga scroller).
But, on iOS when you "let go" of a View that is mid-swipe, it snaps back much more quickly. This is doable, but would require for the scroller to support dynamically settable speeds for "paging". So once a drag starts we could set "pagingAcceleration" to a fast value. Or just have that set in general.
Another piece it needs (should be another ticket on reapp-scroller) is dynamic animationduration in general, because back animations on iOS are 450ms and forwards are 550 (or so).