The following is the first few sections of a chapter from The Busy Coder's Guide to Android Development, plus headings for the remaining major sections, to give you an idea about the content of the chapter.
Users like things that move. Or fade, spin, or otherwise offer a dynamic experience.
Much of the time, such animations are handled for us by the framework. We do not have
to worry about sliding rows in a
ListView when the user scrolls, or as the user pans
ViewPager, and so forth.
However, sometimes, we will need to add our own animations, where we want effects that either are not provided by the framework innately or are simply different (e.g., want something to slide off the bottom of the screen, rather than off the left edge).
Android had an animation framework back in the beginning, one that is still available for you today. However, Android 3.0 introduced a new animator framework that is going to be Android’s primary focus for animated effects going forward. Many, but not all, of the animator framework capabilities are available to us as developers via a backport.
Understanding this chapter requires that you have read the core chapters of this book. Also, you should read the chapter on custom views, to be able to make sense of one of the samples.
The preview of this section is [REDACTED].
The preview of this section was eaten by a grue.
The preview of this section is in the process of being translated from its native Klingon.
The preview of this section was fed to a gremlin, after midnight.
The preview of this section did not survive Thanos's finger snap.