I’m really afraid people will stop using ObjectAnimators for “performance” reasons after this article. Reflection to lookup a setter is used only once, then the setter is cached in a static Map. Impact on performance is really negligible.
I agree that choreographing a complex animation of several views may be much simpler with a ValueAnimator, but in most cases I would go with ObjectAnimator (or ViewPropertyAnimator for the simplest cases without AnimatorSets).
Also, I’m not sure what you meant by:
ObjectAnimator doesn’t support simultaneous changes
If this was about animating several properties, ObjectAnimator supports simultaneous animation of any number of properties via ObjectAnimator.ofPropertyValuesHolder.
And thanks for the article. Its like a breath of fresh air after the flow of “Getting started with Kotlin / Architecture Components” gushed on us.
