you may consider using a single viewmodel and assigning the two models in question to its fields.
The reason why we recommend using data-model instead of kendo.bind is performance. The mobile views do declarative initialization of the widgets (based on the data-role attribute), and kendo.bind does the same + establishing the bindings. The data-model field performs this in a single pass, thus avoiding the costly DOM recursive traversing.
In case you insist on using the kendo.bind approach, you will have to pass multiple namespaces as arguments, as documented and showcased in our API reference.
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI