In November of 2015, the Visual Layer was introduced as a series of new APIs in the Windows.UI.Composition namespace. These new APIs marked the first opportunity for app developers to get direct access to many of the capabilities that have underpinned the UI Frameworks since Windows 8 (e.g., IE/Edge, XAML, & the Windows Shell). One key aspect of the new Visual Layer is its new animation engine. But after spending a bunch of time talking to developers at //build this year, it became clear that devs are still not clear on how the pieces of the animation system fit together. To shed some light on what you can do with the animation system let’s walk through two questions:
- Who’s responsible for starting animations?
- What drives the animation to change values?