How to reduce AnimationController boilerplate code: Flutter Hooks vs extending the State class

How to use Flutter Hooks or State subclassing to reduce your AnimationController boilerplate code.
Written tutorial: 👇👇
codewithandrea...
Join my FREE email course to become a Flutter expert with the best resources, at your own pace: codewithandrea...
Want to master animations in Flutter? Check out my full animations course: 👇👇
codewithandrea...
Happy coding!

[@crazy-man]

yes cool, just wanted to get rid of these long constructs for creating animation

[@theGoldyMan]

That's all cool if you have one Animation controller, what if you have several. This pattern becomes unusable.

[@CodeWithAndrea]

How often does that happen? I have apps with many animation controllers, but all in separate widgets.

[@theGoldyMan]

@@CodeWithAndrea as soon as you have 2 things to animate that have different timings. For example, I'm making an audio player that looks like magnetophon. I want the 2 reels to turn with a different speed and I want to update that speeds depending on the elapsed / remaining time. Or I have a button that on click have to scale down and up and at the same time to fire a water ripple like effect( not like inkwell, but the ripple is outside the button). Sometimes you can get away with Interval but not always, and that's when you need to add more controllers. I actually remember that when i was working on the flutter clock challenge, I had 3 controlers, one for hours, one for minutes and one for seconds. On second though I could move the animation controller for each reel indside another widget. But then the controlling of when to start when to stop, when to pause when to reverse with a certain speed (timing change) becomes very troublesome.

[@CodeWithAndrea]

@@theGoldyMan Maybe I don't understand this fully, but I would still opt for creating separate widgets for parts of the UI that depend on a single AnimationController, and use a parent widget to control those widgets via GlobalKey. Or if you really need multiple controllers inside a single widgets, maybe do it with flutter_hooks? The state subclassing approach works for simplifying the boilerplate with a single AnimationController, which should be the majority of cases.