As you can see on Sencha site, Sencha Touch (ST) was developed to take advantage of hardware acceleration. In case you don’t know what hardware acceleration means and if you are starting to work on your first ST application then you should be informed about it as it might affect your app performance and responsiveness. Particularly when using PhoneGap 2.6(2.x) to deploy natively for Android 4.x, because Android default browser still has performance problems with 3D CSS transforms.
To find more about the meaning of hardware acceleration in mobile technology you can visit these blogs:
- About hardware acceleration: http://www.sencha.com/blog/understanding-hardware-acceleration-on-mobile-browsers/
- And what means to have it in your app: http://www.tricedesigns.com/2013/03/11/performance-ux-considerations-for-successful-phonegap-apps
Also I recommend a very good post about GPU accelerated compositing in Chrome.
Where hardware acceleration is used in ST? You can see it almost everywhere, in some layouts, scroller, list and in animations. As example, the Card layout, basically it works on translate3d. You must be careful with your DOM size, where and how you use the elements which trigger hardware acceleration. And if you deployed your hybrid Android app and you feel low performance and responsiveness then you might check if you disabled hardware acceleration in PhoneGap’s Android Manifest. By disabling, paradoxically it will boost your application to an acceptable level. Note that once is disabled then you will have to stick with flat effects because the 3D transforms, more exactly the Z axe won’t work – a needed CSS for such component like the Coverflow.