| author | Description | title | ms.assetid | label | template | ms.author | ms.date | ms.topic | ms.prod | ms.technology | keywords | ms.localizationpriority |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
serenaz |
The master/detail pattern displays a master list and the details for the currently selected item. This pattern is frequently used for email and contact lists/address books. |
Master/details |
45C9FE8B-ECA6-44BF-8DDE-7D12ED34A7F7 |
Master/details |
detail.hbs |
sezhen |
05/19/2017 |
article |
windows |
uwp |
windows 10, uwp |
medium |
The master/details pattern has a master pane (usually with a list view) and a details pane for content. When an item in the master list is selected, the details pane is updated. This pattern is frequently used for email and address books.
Important APIs: ListView class, SplitView class
The master/details pattern works well if you want to:
- Build an email app, address book, or any app that is based on a list-details layout.
- Locate and prioritize a large collection of content.
- Allow the quick addition and removal of items from a list while working back-and-forth between contexts.
When implementing the master/details pattern, we recommend that you use either the stacked style or the side-by-side style, based on the amount of available screen space.
| Available window width | Recommended style |
|---|---|
| 320 epx-640 epx | Stacked |
| 641 epx or wider | Side-by-side |
In the stacked style, only one pane is visible at a time: the master or the details.
The user starts at the master pane and "drills down" to the details pane by selecting an item in the master list. To the user, it appears as though the master and details views exist on two separate pages.
One way to create the stacked master/details pattern is to use separate pages for the master pane and the details pane. Place the master view on one page, and the details pane on a separate page.
For the master view page, a list view control works well for presenting lists that can contain images and text.
For the details view page, use the content element that makes the most sense. If you have a lot of separate fields, consider using a Grid layout to arrange elements into a form.
For navigation between pages, see navigation history and backwards navigation for UWP apps.
In the side-by-side style, the master pane and details pane are visible at the same time.
The list in the master pane has a selection visual to indicate the currently selected item. Selecting a new item in the master list updates the details pane.
One way to create a side-by-side master/details pattern is to use the split view control. Place the master view in the split view pane, and the details view in the split view content.
For the master pane, a list view control works well for presenting lists that can contain images and text.
For the details content, use the content element that makes the most sense. If you have a lot of separate fields, consider using a Grid layout to arrange elements into a form.
To implement a master/details pattern for any screen size, create a responsive UI with an adaptive layout.
To create an adaptive layout, define different VisualStates for your UI, and declare breakpoints for the different states with AdaptiveTriggers.
The following samples implement the master/details pattern with adaptive layouts and demonstrate data binding to static, database, and online resources: