This article is intended to collect and summarize the topic of Animations in Android. In order to reach an excellent UX design, it is necessary to employ Android’s animation API to improve the details of the UI.
Before the details of the Android Animation, I want to recollect the history of Android’s evolvement in Animation API. Before the Android 3.0, it is a wild time, the uncivilized Animation packages dominate the wild field, it is the android.view.animation package. Then the property animator appears at Android 3.0 release, the property Animator is much advanced than Animation, it can animate not only the visible view properties but also any values by ValueAnimator, it is the android.animation.Animator package, much more details can be read from the following sections.
Besides the universal Animator, another ViewGroup animation API appeared at Android 3.0, it is the LayoutTransition which was used to animate the layout change event.
Then, at Android 3.2, we can animate Fragment transaction by the new setCustomAnimations method.
I consider the development from Android 3.0 to 4.4 as the first evolution. The brilliant improvement from Android 5.0 is the second evolution.
The Android’s new design language, material design, appeared at Android 5.0, which was an evolution. there are three parts related to Animation. First, windows transition appeared to improve the animations between activities; second, vector drawable was used to do material animation inside an ImageView; third, it is the touch feedback effect.