As we've already discussed, the model for FMX animations relies on the presence of a global timer that periodically pings active animations to solicit each to perform the next step (providing a delta amount of time to cover in the animation).
This timer is usually created using the IFMXTimerService provider, which is platform-specific and built into the FMX framework. You can query an IFMXTimerService reference through TPlatformServices.Current in the FMX.Platform unit. For the Android platform, a different, more thread-oriented, path has been chosen for implementing the timer. Apart from this small detail, animations will be consistent across all supported platforms (a huge advantage for the developer) and will follow the model we've described so far.
A reference to the global timer is available through the TAnimation.AniThread property (an instance is created on-demand, generally at the start of the first animation). Its...
