Learn how to support navigation between pages and content within your app.
In contrast, a single-page navigation model uses a single page to maintain app context and to load additional data and content as needed. You still split your app into multiple files, but instead of moving from page to page, your app loads other documents into the main page. Because your app's main page is never unloaded, your scripts are never unloaded and so it's easier to manage state, transitions, or animations. We recommend that apps use the single-page navigation model.
For help choosing the best navigation pattern for your app, see Navigation patterns.
Learn how to use a WinJS.UI.Pivot control for layout and navigation in your Windows Phone 8.1 app.
Learn how to link to external web pages and display them in your app.
- For developers
- Your first app - Part 3: PageControl objects and navigation
- Adding app bars
- Quickstart: Using single-page navigation
- Quickstart: Adding a nav bar (NavBar)
- Quickstart: Using a hub control for layout and navigation
- WinJS.Navigation Namespace
- WinJS.UI.Hub object
- WinJS.UI.AppBar object
- WinJS.UI.NavBar object
- WinJS.UI.BackButton object
- HTML Hub control sample
- HTML AppBar control sample
- HTML NavBar control sample
- Navigation and navigation history sample
- For designers
- Navigation patterns
- Command patterns
- Back button
- Guidelines for the hub control
- Guidelines for app bars
- Making the app bar accessible