Firefox will deliver the best native SVG experience (including animations), whereas Opera Mobile will properly render SVG, but won't preserve SVG scripting or animation. Two popular choices to consider if you want native SVG support on Android 2.x:īoth of these browsers are free, and both natively support SVG. By simply installing one of these more capable mobile browsers, Android 2.x users can quickly gain native access to more HTML5 features (including SVG). Unlike Apple's iOS, there are many different browsers (with different HTML/JS engines) available on Android. There are probably many creative ways you could technically solve the problem of SVG on old Android, but for the sake of this post, our available options are: By the end of this post, I'll show you how you can easily use Kendo UI DataViz (and SVG) on any version of Android, all the way back to Eclair (Android 2.1). Together, we can deliver richly interactive data viz that works just about everywhere.Īs with most things in the modern web, though, there are always creative solutions for older browsers. SVG is a vector-based standard, broadly supported on all modern browsers, especially suited for interactive 2D rendering, and VML is a similar Microsoft technology that we use to support older versions of IE. When we set-out to build our data visualization tools for HTML5, we picked a combination of SVG and VML to power the Kendo UI DataViz rendering. That means we need to work around the problems. Google may be able to make the hard sell and only support Android 4+, but most developers probably prefer to include the 94% of Android 2.x users in their target user base. Target Android 3+ devices (and less than 5% of the Android market).Google seems to know this, and they are actively developing Chrome for Android (yay!), but so far that's an Android 4+ exclusive.Īs a developer targeting mobile HTML5 devices, you have two options for dealing with this Android situation: Newer versions of Android (3+) improve the situation, but even in those cases the default Android browser leaves something to be desired. The default Android 2.x browser lacks device orientation events. With the broad majority (94%) of Android users still using a 2.x version of the platform ( according to Google's own stats), Google has created a huge population of mobile users that have a crippled HTML5 browser. Like it or not, Android version fragmentation is creating the new class of "IE6" browser for mobile development.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |