3 ms·
Android fragmentation is a reason not to use HTML5? That's about as backwards a statement as I can imagine - web apps are the great savior that abstract away a
by notatoad 14y ago
Android fragmentation is a reason not to use HTML5? That's about as backwards a statement as I can imagine - web apps are the great savior that abstract away all the device fragmentation. And windows phone's incompatibility as a sticking point? That's an easy one to overcome: nobody writes windows phone apps either. I don't have any experience with mobile IEs quirks, but if it's as bad as you make it sound, just sniff the UA and tell the user it is not compatible. Until I see a windows phone show up in my server logs, I'm not going to worry about it.
Overall, web apps as a platform have made a lot more growth than native mobile apps have aince the advent of the smartphone. There's no reason to look at the state of html5 now and say "it'll never work". Sure, there are some things that native is better for, but html5 is a very useful tool and can give a great user experience in a lot of cases, and it's only going to get better.
- cek 14y ago> web apps are the great savior that abstract away all the device fragmentation. I'm not sure if you are trying to be serious or not with this. Do you really believe this is true today? That you can build a mobile experience using HTML that compares to that of a native app? Certainly there are SOME cases where it makes sense. But for MOST apps, it simply does not. For example, let's say I wanted to build an app that used location and could run in the background. How, exactly, would I build a "web app" that worked across iPhone, iPad, and say 75% of Android devices? And how is whatever you come up with "HTML5"? WORA has always been, and always will be a pipe dream. HTML5 gets closer but, unfortunately, due to the dynamics of mobile the target is moving further away.
- notatoad 14y agoYou can't build web apps that run in the background and expect any sort of browser compatibility, and you know it. That's why you picked that example, despite the fact that I freely admitted in my original comment that there are use cases for which a native app is a better choice. If you are bound and determined to hate the web, good for you.
- scott_w 14y agoUnfortunately, in practice, the fragmentation extends into browser incompatibilities. I have first-hand knowledge of this, to the extend that a broken WebKit from Android 2.2 had been forward ported to Android 2.3 on one of the mobile devices we tested.
- untog 14y agoAndroid is a good reason to not use HTML5, to be honest. It confuses me deeply that Apple has provided far more HTML5 webapp functionality that Google has- Google ought to be encouraging webapps whenever possible.