Guidelines and checklist for content transition animations (Windows Store apps)
This topic describes best practice recommendations that you should apply when you use the content transition animations.
- Use content transitions when there is a set of new items to bring into an empty container. For example, after the initial load of an app, part of the app's content might not be immediately available for display. When that content is ready to be shown, use a content transition animation to bring that late content into the view.
- Use content transitions to replace one set of content with another set of content that already resides in the same container within a view.
- When bringing in new content, slide that content into the view against the general page flow or reading order. For instance, if the animation is to bring new content to a document that flows from left to right, then the incoming content should move in from right to left.
- The recommended offset from which new content enters is 40 pixels.
- If you have more than one container whose content is to be updated, trigger all of the transition animations simultaneously without any staggering or delay.
- Don't use content transition animations when the entire page is changing. In that case, use the page transition animations instead.
- Don't use content transition animations if the content is only refreshing. Content transition animations are meant to show movement. For refreshes, use fade animations.
For general Windows Store requirements, see Certification requirements for Windows apps.
- Using the Animation Library animations sample
- C#/VB/C++ and XAML:
- Animating your UI (Windows Store apps using C#/VB/C++ and XAML)
- Animating content transitions (Windows Store apps using C#/VB/C++ and XAML)
- Quickstart: Animating your UI (Windows Store apps using C#/VB/C++ and XAML)
Build date: 3/5/2013