3 ms·
Ok, thanks. I'm wondering how users on mobile browsers which aren't iPhones would react to that interface...? (And also, how well it would render.)
by csbrooks 17y ago
Ok, thanks.
I'm wondering how users on mobile browsers which aren't iPhones would react to that interface...? (And also, how well it would render.)
- rufo 17y agoIt works well enough on Android and Palm Pre, although without the fancy OpenGL-accelerated CSS transforms (it gracefully degrades to more traditional CSS animations if WebKit transitions are not available). The underlying HTML is just a bunch of unordered lists and divs, and all the advanced behavior is via CSS and Javascript - if you want to make sure it'll work on less-capable browsers it's doable, but you'll need to keep an eye on how you're loading things. You may wind up needing to to browser sniffing on the server and serving up different HTML if you see various browsers; we didn't get that far in the project we worked on.
- seiji 17y agoNot sure about iUI, but jQTouch uses webkit-enhanced markup so any webkit engine will read it correctly. jQTouch apps look great in desktop Safari, iPhones, and Android devices. It's even marginally passable in firefox. Though, Android is very late getting some features (HTML5 manifests, local storage, and navigator.geolocation) and I'm still not sure if it supports support CSS animations.