@aceguy2017: I think the video explains this pretty well.
The desktop bridge allows you to run mixed components. You can write your UI in a UWP executable, couple it with a desktop executable for anything that UWP doesn't allow, and package all that up as one application. As more and more Win32 APIs are ported to UWP, the amount of code in the desktop executable can decrease (perhaps even go away at some point).
For cases where the application needs more power/trust than even a Centennial app would allow (such as a driver or system service), you could make that part available as a separate download and let the Store app communicate with it when necessary.
I was about to make the same comment as contextfree`. I might go one step further and automatically save as I go.
I also feel that JamesB's comment was insightful. I think your data entry forms have the appropriate information density, but that the "summary" views and other read-only views should be more information rich. The result is more clicks and more pages, which in medium or large LOB apps would cause the user to lose context and get lost. It's almost too much even in this small app.
The app is boring. I feel that many Windows 8 apps are this way. I suppose that developers fear what Microsoft would think if they used more than two colors. And I don't like the inconsistency in the color scheme. The summary screens use a light overall background, and dark tiles with light text. Then, data entry screens use a light background with dark text. I would make the summary screens have a darker background, and then use that with light text for data entry. (Or, do the inverse if you would rather have dark text on light backgrounds.)
I may have missed something at some point, but when did the ability to hook into another IoC container get added? This has been a hot topic for MEF, and I didn't see anything about it in the release notes.
Regardless, does this mean that I can use (for instance) Windsor as the back-end container for MEF, and it would give Windsor the ability to discover plugins and compose based on the Import and Export attributes in MEF? If so, this is great news! We had
just decided to drop MEF in favor of rolling our own plugin discovery with Windsor... maybe we don't have to anymore.