First, thank you for the compliments!
To answer your question:
Android 2.x browser is based on webkit, just like safari and chrome, so in theory it should render everything the same as those 2 browsers, but in practice, there are some differences. One of the differences is that Android supports smaller set of CSS3 properties. Transformations in particular are troublesome in Android, as they are not fully supported Checking the 'Android 2.x' option when you create a new project in Animator will therefore limit the available properties to ones that are supported properly by Android - it is a way of making sure that anything you make will render correctly on Android.
However, since Android browser uses the same CSS3 '-webkit' prefix as Chrome and Safari, any project that has been exported without 'Android 2.x' option enabled, should also render and animate when viewed on Android. So, if you have a way to tweak the code to create a workaround for Android after you include rotate/scale/translate, you can just create a regular Animator project and work from that.
Do note though, that normally regular projects, when exported, if they include transformations, will probably not render correctly when viewed on Android.
I hope this answers your question. Good luck with your project!
Thank you for your reply!
Yes we are aware of the issues with Android, in particular rotate/scale transforms.
I bring up the issue only because our designers created some complex animations and of course failed to render properly in Android 2.x
With regards to those issues, we've decided to create animations using the 2.x in Sencha Animator and then tweak them by hand because we find this faster than creating a regular project and then going back to retweak the transformations we're interested in.
Anyways, thanks for the heads up and we wish you guys continued success