An example that has widespread application in business data is the master-detail page relationship. A master page provides summary level information on the customer, account, product, or whatever category of information is represented. From this master page, the user can drill down and see the detail level of information for a selected entry on the master page. In desktop applications, the detail page may be displayed in a special area at the bottom of the master page; in mobile applications, the detail page typically has to be a completely separate page, and therefore you have to maintain the application state as the user switches between the master and detail pages.

The text that follows focuses on how the Master-Detail Page example uses the PODSPrefs object to maintain the application state. For additional information on this M-Business Anywhere sample code, see Master-Detail page.

An accounts master page, also commonly referred to as the list view, displays just enough information in each account's row to allow the user to identify the account. The master page would look something like the figure below.

When the user taps a name in the Customer column, a detail page, also commonly referred to as the detail view, appears for that account. The detail page might look something like the figure below.