HTML and CSS Reference
FIGURE 8-3 Fundamental aspects of snapped and filled applications.
Any application can experience both view states during its lifecycle. It's up to the user, not the
application, to decide about the display mode. From the application's perspective, support for view
states (including snapped and filled view states) is all about being ready to render any content in a
screen of different sizes.
The behavior of a Windows Store application is not supposed to change when running in a view
state different from full-screen. There's a specific guideline that strongly recommends this. It is
reasonable to expect that very little changes in the application's behavior and user interface when the
application is run in landscape, portrait, or filled mode. At the same time, not all applications can be
resized to a sliver of the original screen and still maintain 100 percent of their functionality.
You'll see in a moment how to detect view state changes in a Windows Store application and what
it possibly means for your application to support well different resolutions. Before going any further,
look at Figure 8-4.
The figure doesn't show a screenshot but it rather contains a diagram that seeks to illustrate the
difficulty of (some) applications to adapt to different resolutions.
FIGURE 8-4 From full-screen view to snapped view: how to adjust the user interface?