Binding the widget to remote dataSource will not resolve the issues you encountered. As my colleague Petyo explained they are caused by a combination
of currently not supported scenarios, e.g. the reason for the issues is not only the type of data that you work with.
At present I can suggest a workaround only for the 3rd problem:
3. The bottom scrollview isn't visible initial until the user starts to interact.
To fix that, you should make the scrollview widget element relatively positioned with CSS. Just add the following to the style sheet of your project (we will include this fix in the next release).
Regarding 4th issue:
4. For the bottom scrollview. With 3 data items, I'd expect to be able to page swipe to the 2nd page. That doesn't seem to work. The 3rd item doesn't appear to have been created.
Currently the widget renders only pages that have full set of items per page. In your case, in the DataSource there is only one record left while the widget has to render 3 items. We consider this as a bug and will fix it for the next official release. Unfortunately I cannot suggest an easy workaround since the fix requires changes in the source code of the framework.
The same applies for issue #5. We will investigate further the behavior in cases #1 and #2.
Once again, please accept my apology for the inconvenience caused.
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI