Ergonomics of using multiple motion libraries in an app

[jverkoey]

We'll soon have the following motion libraries for iOS:

• core-animation-swift
• transitions-core-animation-swift
• pop-swift
• transitions-pop-swift
• direct-manipulation-swift

This feels like a lot of libraries to manage.

Should we consider providing a meta library that includes all of our "core" motion libs? Might be called MaterialMotionLanguage or something to that effect.

[appsforartists]

I've always expected we'd do something similar to this. Having a batteries-included library that packages all of our recommended components will make it a lot easier for beginners to get started.

I've been imagining that I'd ship something like material-motion that exports the modules that most people will want, and allow people who want more selectivity to import material-motion-runtime, material-motion-gestures, etc. piecemeal.