Navigation in MVVM (i.e. a view model class) is usually done via a MVVM framework's navigation classes (e.g. see Prism's NavigationService).
If you are not using an MVVM framework, the most common approach is to just call navigation methods via App.Current.MainPage reference. For example, if MainPage was a NavigationPage, you can do this:
public class MyViewModel
private async Task GoToNextPage()
await (Application.Current.MainPage as NavigationPage).PushAsync(new MySecondPage())
Note: referencing App.Current references the view, thus is not 100% view - view model separation. If you must be 100% MVVM pure, then you'll need to consider other options like using Prism or writing your own interface.
For more assistance on this topic, I recommend visiting the Xamarin, Prism or StackOverflow forums. The Telerik forums primarily focus on using the UI for Xamarin controls and aren't a perfect resource for general Xamarin questions.
Lance | Team Lead - US DevTools Support
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items