Now that you have the Crosslight project configured and running, the first and most important lesson in the Crosslight application development is to understand how data binding works across various supported platforms.
In essence, Crosslight was built around the MVVM (Model-View-ViewModel) design pattern which has becomes one of the modern design patterns that effectively decouples user interaction logic from the view-specific technology. MVVM was first invented in Microsoft development platforms such as WPF and Silverlight – which was made possible through the XAML markup language and the data binding concept that allows dynamic data context, two-way data binding, and object value conversion.
Crosslight includes its own data binding implementation that is on-par with Microsoft’s implementation which ultimately brings the MVVM design pattern to the iOS and Android world – as well as to the other development platforms that didn’t provide support for data binding mechanism. As the results, Crosslight opens up new kind of possibilities particularly in the cross-platform mobile development such as unifying the application logic layer and maximizing code sharing up to 96% percent across various multiple platforms.
The following illustration shows how Crosslight enables MVVM design pattern to work consistently on iOS, Android, Windows Phone and Windows RT platforms.
With MVVM design pattern thoughtfully applied in the entire Crosslight technology stacks, it creates amazing results in which a single ViewModel codebase can be efficiently consumed and reused across different platforms regardless of the view-specific technologies.
To learn more how MVVM works in Crosslight, please refer to the following topics.
- Crosslight and MVVM at a Glance
- Crosslight Data Binding Features
- Understanding Binding Providers
- Importing Binding Providers to View
- Selecting a ViewModel Base Class to Get Started
- Implementing Custom Bindable Properties