With the current implementation of the control, if you have events later in the day - the user needs to scroll down so that they are shown. We can consider adding a mechanism to show the first available event or expose methods to bring a specific event into view.

Add a Map control to the product suite.

Currently, all groups are expanded by default. We should expose methods to collapse/expand certain groups. Furthermore, CollapseAll, ExpandAll groups should be considered as well.

The Android and iOS versions of the control support multiple and range selections. We should consider embedding such features in the Xamarin.Forms control as well.

Links to the features in iOS and Android:

- Android Range Selection: https://docs.telerik.com/devtools/xamarin/nativecontrols/android/calendar/calendar-selection

- iOS Range Selection: https://docs.telerik.com/devtools/xamarin/nativecontrols/ios/calendar/selection

As of 2018.2.620, UI for Xamarin will invoke approximate 600 warnings when compiling an Android project that uses SDK later than 23.

This is due to the fact that the UI for Xamarin.Android controls are built on API 23, which will surface warnings at compile time if the project consuming them is using a later version.

Although UI for Xamarin is compatible with newer version, and causes no impact on the outcome, these warnings obscure any meaningful warnings the user might have. 

This is a problem when projects are built in a CI/Cd pipeline and warnings are treated as important/significant for enterprise CD deployment (i.e. scrolling through 600 warnings to find any legitimate warnings is not practical).

Available in R3 2018 release.

Allow binding of complex objects to RadDataGrid.

Add localization for DisplayOptions data annotation.