Favorites Integration Guidelines
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
10/16/2008
This topic provides user-interface (UI) guidelines for user interaction between Favorites and the Live Search application on a Windows Embedded NavReady powered device.
Guidelines
In a Live Search application, a user should be able to save Point of Interest (POI) data retrieved from the Live Search Engine by selecting the POI and tapping a Save to Favorites button. When a POI is saved to Favorites, Favorites should display the Live Search logo next to the POI in the list view.
The default user interaction between Favorites and Live Search should occur approximately as follows:
- The user chooses Live Search.
- The user chooses Favorites.
- In the Favorites menu, the user is presented with a list of all search-result collections and all single locations that have been retrieved from the Live Search Engine. Note that single locations are not part of a collection, meaning that the Collection Name is undefined.
- Live Search application provides default sort order:
1. The application displays collections first, alphabetically
2. The application displays single locations, in order of closeness to the current GPS location - Live Search application enables searching by name
- Live Search application provides default sort order:
- The Collection displays a list view that shows all locations contained in that Collection.
- Collection is sorted by closeness to the current GPS location
- Collection enables searching by name
- The user selects a location, either from the primary list view or from a Collection list view, to display the basic metadata available for this location. If values are not available for any field, the application must not display "unknown". The application just should not display the value. The screen should also give the user the ability to navigate to the location.
- Any additional metadata that exists can be displayed in a More Info screen. If no such additional metadata exists, the More Info button should not be displayed.
The following illustration shows the preferred user-interaction flow, as described in the previous steps:
.gif "Local Search User Interaction Flow")