Unified way to address a view Being able to deeplink to a view Being able to change the view on the fly (gatekeeping, A/B testing, …) Integrate well in to the framework(s)
Uri("/Pages/AlbumsPage.xaml", UriKind.Relative)); ×Views should not navigate to views ×Unified way to address a view ×Being able to deeplink to a view ×Being able to change the view on the fly (gatekeeping, A/B testing, …) √ Integrate well in to the framework(s)
Controller is responsible to construct all the navigation URIs • A User control gets this URI and perform navigation on tap • We implement an UriMapper ! dz://mylibrary/albums => /Pages/AlbumsPage.xaml The Windows Phone Frame accepts an UriMapper
views √ Unified way to address a view × Being able to deeplink to a view √ Being able to change the view on the fly (gatekeeping, A/B testing, …) √ Integrate well in to the framework(s)
typeof(AlbumPage) ); ×Views should not navigate to views (WE NAVIGATE TO VIEW CLASS !!) ×Unified way to address a view ×Being able to deeplink to a view ×Being able to change the view on the fly (gatekeeping, A/B testing, …) √ Integrate well in to the framework(s)
views √ Unified way to address a view × Being able to deeplink to a view √ Being able to change the view on the fly (gatekeeping, A/B testing, …) √ Integrate well in to the framework(s)
navigation Framework • Causes random crashes • Several months of investigation • => WP Nav. Fw. Does not support Absolute URIs navigations within the app… • Dz://mylibrary/albums replaced by /MyLibrary/Albums
to views √ Unified way to address a view √ Being able to deeplink to a view √ Being able to change the view on the fly (gatekeeping, A/B testing, …) √ Integrate well in to the framework(s) Pass object instances between views
/ an URI _navigationService.Navigate(protocolArgs.Uri.Origina lString, null); I want to navigate to a view, but I already have this object _navigationService.Navigate(PageTokens.AlbumPage, currentAlbum);