If a SideDrawer has gestures enabled, you cannot scroll DrawerContent in the same direction as the drawer. For example a ListView in DrawerContent when DrawerLocation="Bottom"

If the SideDrawer only uses gestures that begin outside the drawer, then this would prevent the conflict.

On UWP this can be achieved if you set double.NaN as a value of the DrawerLength property and on Android this achieved by setting 0 as a value of the DrawerLength property. On iOS is not supported at all.

We should consider exposing a property that will leave the side drawer opened even when you click on the main content. 

Exception stack trace: java.lang.ClassCastException: android.view.AbsSavedState$1 cannot be cast to java.lang.Boolean. Reported on Sony and Meizu devices

Edit: Avalable in R3 2017 SP release.

Available in minor release 2017.2.0721. It will also be available in the R3 2017 release.

If the MainContent of the RadSideDrawer contains a Xamarin Forms Entry control, and the user enters a space into theEntry with the spacebar, the RadSideDrawer's Drawer will open unintentionally.

Code to reproduce:

<telerikPrimitives:RadSideDrawer DrawerLength="200">
        <telerikPrimitives:RadSideDrawer.MainContent>
            <Grid>
                <Entry VerticalOptions="Center" HorizontalOptions="FillAndExpand"/>
            </Grid>
        </telerikPrimitives:RadSideDrawer.MainContent>
        <telerikPrimitives:RadSideDrawer.DrawerContent>
            <StackLayout VerticalOptions="Start">
                <Button Text="A button" />
            </StackLayout>
        </telerikPrimitives:RadSideDrawer.DrawerContent>
</telerikPrimitives:RadSideDrawer>

Available in minor release 2017.3.927. It will also be available in the R3 2017 SP release.

Currently only Views can be hosted in the MainContent. If users can host Pages the RadSideDrawer could be used as root navigation component. This will allow customers to define the RadSideDrawer once throughout the application.