Android SDK emulator is nowhere comparable to the real device so it’s not really an option. We do test on android 4.x phone and tablet and ensure everything works as expected (layout/functions)
However, most of the times there’s not much you can do to optimize a plugin/template/theme for this platform when it comes to transition/scroll smoothness and touch events handling.
Truth is (omg i hate myself for saying this), apple mobile safari is still way ahead its competitor stock browser so you just end up optimizing for ios and to accept compromises on android.
@PixelEntity – I totally agree with the Safari comment with regards to the Stock browser (even with the improvements in 4.2). While I’d like to see Google completely remove / replace the stock browser with Chrome across the board, it’s easier said than done. The additional choice that Android provides is my favorite feature even if does make testing as difficult as on Windows sometimes.
Do you also feel similarly about the mobile Chrome / Firefox apps optionally installable from the Play Store? Do you have them installed and use them in your testing somewhat like you would on a computer?
I need my sites to support Windows / Mac OS / Android / iOS and anyone who helps with that gets my business. I try not to let my personal preferences affect the standard of my work when I’m doing my own testing. Android certainly is not alone in being difficult to work with though from my own experience.
Saw this article in my news feed today, thought of this thread. Do you agree / disagree?
Android’s F-Word mostly irrelevant, but affects Apple similarly – http://phandroid.com/2013/02/27/android-ios-fragmentation/