OOBE version of NavigationView

[Arlodotexe]

After a discussion in the Windows App Community #dev-xaml channel, we've identified the need for a control similar to NavigationView but tailored for building out of box experiences.

Making such a control fully self-contained while remaining flexible and configurable will be important. Rather than building a single unified OutOfBoxExperienceControl, which may require clunky data-based ui abstractions or being restricted to a set of tailored controls (e.g. SettingsExpander can only use SettingsControl), we opt for a different approach.

Examining the baseline functionality needed for an OobeView, we find that most of the pieces are already here: SwitchPresenter, Behaviors, binding, templating, SettingsControls, etc. The issue isn't a lack of "generalized control", but that putting the pieces together isn't obvious.

The only thing we're missing here is a way to move between the different SwitchPresenter views, and some good sample code to combine it all.

Luckily, an established example of what we need to build already exists, NavigationView. You can bind NavigationView.SelectedItem to a SwitchPresenter and bind each item on each case, and you get the type of "view controller" we're looking for here for OOBE.

The idea has solid ground but is missing details about how we implement navigation via the OobeView control. It would be helpful to collect examples of OOBE screens from real programs to give us an idea, everything from apps to app installers to operating systems.

[Lamparter]

Here are some potential design ideas (from RiseMP). If you would like to test these designs out for yourself, please download Rise Media Player.

Designs (truncated to avoid flooding page)

There are also very pretty animations on each page.