Spearfish

thank you for that fix... I was using... -webkit-transform: translateZ(0.1px); but for some reason this did not yield the same result as yours did. Anyway, that fix made a huge difference. When doing full page fade-ins there is some stuttering. I likely attribute that to the DOM still loading while fading at the same time; however this stuttering does not occur with CSS3. So because of this I was wondering about the technological differences between using Greensock opacity manipulation and using CSS3 animation. I appreciate your support with these issues cause they make a huge difference in performance and will likely help a lot people out there experiencing the same problems. I have seen similar issues addressed in these forums but have seen little help in actually addressing the issues so thank you for addressing these issues directly.

that was the magic bullet! animating x and y instead of top and left offered a much smoother animation. The only difference there is when the animation is run the first time from a browser refresh, there is a jump. but subsequent animations after that were smooth.... I have the following css on the container but still has the jump.... -webkit-transform: translateZ(0.1px); So any insight there would be great. But it certainly seems using x,y yields smoother performance on mobile over top, left. Lastly, if you don't mind. I know the issue of opacity has been raised but using greensock for opacity on mobile is extremely choppy and using ... -webkit-animation is far smoother. Is there a possible workaround to that? I appreciate you time. thank you.

I'll work on getting the headed to head example but the comparison was not so much GSAP vs CSS transitions (these seem to perform on mobile about the same), the but rather GSAP vs CSS Transforms. Simply moving an object from A to B. Transforms is much smoother than GSAP on Android and Mobile iOS. I admit there are HUGE limitations in using Transforms; however I am only trying to get down to how to output the smoothest performances to the user. I have tried using the Z value fix. but had little affect (however it made a huge difference with Greensock when animating a video container).

I've been using Greensock animations since its inception with AS and I've been using it for years with the JS version. Its a great library and will continue to use it.So thank you for that. Regarding desktop browser I have no issues here; however regarding mobile devices. I am seeing animation stuttering on both Android and iOS devices. I want to reiterate that this was also seen on Android devices as well because I know there have been some mention of issues on iOS. However I never saw any real solutions to this stuttering. I wrote a few examples animating with greensock and CSS3. actually the performance was a about the same same. both had some stuttering. The big difference was demonstrated when I introduced CSS3 Transform. This by far outperformed both Greensock and CSS3 Transitions. So I wanted to know if there was something that I'm missing... I do see that in the 'CSS3 Transitions vs GSAP: Cage Match' it specifically targets Transitions and not Transforms. I am simply looking for the best results to present to my clients. But I'm wondering if for mobile devices CSS3 Transforms are the way to go over Greensock or if there is a technique in Greensock to match the performance that I am overlooking.. thank you product and for your time.