Here’s round two in the HTML5 battle. Really, it needs to be a battle? How about just choosing the technology that works best for the job at hand. Some people want the data and others just want to argue. This stuff intrigues me but I guess those Flash haters (commenter’s) on 9to5mac just want to live in their wall garden. Only experiencing life on one device makes you ignorant, Michael Jackson wouldn’t approve of that ;-) (see video at the bottom of the post). I was told by a wise man that I needed to experience life on an iOS device. As a result, I bought an iPod Touch to work towards building mobile content across platforms. With no further delay let’s check out how CSS3 performs along side Flash on mobile devices.

You’ll notice how we need two technologies to make this work. CSS3 performs great on my iPod Touch but doesn’t work correctly on the Android. Want to view the Apple HTML5 demos? You’ll need an iOS device. Android doesn’t render any of the 3D transformations, typography or actually most of CSS3 in general. Will they fix this in the future? They better. Can you rely on CSS3 today? Not unless you’re targeting iOS devices. When targeting Android for interactive content on the web, Flash still excels. Prove me wrong, build an HTML5 demo that works great on my iOS and Android device. I’ll gladly share it with the world. For now, we have to put up with these ridiculous ‘browser wars.’

Conclusion:
Use the best tool for the job. Don’t make recommendations to clients without appropriate testing. If the project team is testing on an iOS device and the client has an Android who will suffer? My recommendation at this point is to code in Flash with a CSS3 fall back. Why not the other way around? Because Android technically ‘supports’ it and will render junk instead of correct content.

Link to the banner ads:
http://dev.sencha.com/deploy/css3-ads/

Lest We Forget, Ignorance:

Stay tuned for more comparisons on use of technology on mobile devices. I’ve found some very interesting data revolved around canvas performance on mobile devices. If you’d believe it, size does matter. Quantity of pixels that is. Check back tomorrow to find out more!

3 thoughts on “CSS3 Excels on iOS but Lacks on Android

  1. I guess it has to be a battle because it is being made into one. I agree that one should use the best tool for the job at hand, but then for this match up the platform was chosen specifically because it only supports one of the two technologies.

    If you call someone out don’t be surprised if it turns into a fight.

  2. Yes, CSS3 isn’t working well on Android today. I suspect they just have an older version of Webkit, but it might be an actual bug in how Webkit is interacting with their GPU.

    So, submit a bug to Google about that and a bug to Apple about how Flash isn’t rendering. Which one do you think will be acted upon?

    Yes, it sucks that Apple’s not supporting Flash, but from a realist perspective, I’d put my development time into HTML5/CSS3, perhaps not pushing the bounds too much if I really need to serve to the Android user base today, perhaps deciding that I’ll get the Android user base with Android 3 at least (unless a build of Android gets distributed with a newer Webkit before then) and live with an iOS customer base for today.

Comments are closed.