About performance optimization on mobile devices~？

[ice-frog]

I found on some low-end Android devices, when an element first animation, performance is not good, it will Caton.

But when the second run was repeated on more fluent. is this the reason GSAP cached animation data it?

If so, whether at the outset it first animation data cache, the cache if the device itself, have any better suggestions,

let me in the first run of the animation is relatively smooth some

[GreenSock]

The first time any tween renders, it has to grab the current values, record the start/end values, and basically get things ready to be super-efficient during the course of the animation. So yes, the very first render is more expensive (there's no way around that...in any engine). You can, however, choose when you take that hit by pre-rendering up front. You could do that by just forcing the tween/timeline forward and then back again (just to trigger that first render):

var tl = new TimelineLite();
tl.to(...).to(...); //add your animations
tl.progress(1).progress(0); //jump forward and then immediately back to force initialization

That's no less costly, of course - it's just that you're taking the hit up front so that when things do start, they're as smooth as possible for the end user. 

 

Does that answer your question?