Differences between property animation and view animation
View animation provides the ability to only make the View object have an animation effect. Therefore, if you want a non-View object to have an animation effect, you must implement the animation effect code on your own. In fact, the View animation system is also limited. It only exposes the features of a few View objects to the animation effect, such as scaling and rotating a View object, but there is no background color, and so on.
Another disadvantage of View animation is that it can only be modified when the View object is drawn and is not the actual View object itself. For example, if you want a button to traverse the screen in an animation, the button is correctly drawn, but the actual position of the button is not changed. Therefore, you must implement this processing logic by yourself.
In the Property animation system, these are now completely deleted, and can make any attribute of any object animated (View object and non-View object), and can actually modify the object itself. Property animation is also more robust in animation execution. At a high level, you can assign animation actuators to the attributes you want to animation effects, such as colors, positions, sizes, and animation features that can be defined (such as interpolation and synchronization of multiple animations ).
However, the view animation system requires less time to create and write less code. If the view animation can meet your needs, or the existing Code has already done the animation effect you want to complete, you do not need to use the attribute animation effect. Choose to use these two different animation systems for different situations.
By FireOfStar