Tooling is not the problem, the problem is the browsers themselves. On the desktop browsers are updated very frequently, on mobile up until very frequently once-a-year updates were the norm. That's changing on the Android side. So far Chrome for Android hasn't shown to be disruption it was on the desktop, and I'm not sure Google is giving the team the same level of importance as they are on desktop (and Chrome OS).<p>Firefox has the best chance of being the disruptor, and they seem committed, but it's much harder to do it as a 3rd party browser on mobile for a couple of reasons 1) There is not, yet, consumer demand for 3rd party browsers. The default is accepted as the gateway to the web. 2) It's much harder to make a competitive 3rd party browser due to the APIs that are available. Firefox OS is a better experience than Firefox for Android for this reason.<p>The wildcard is still Chrome, in my opinion. It seems to me, as a 3rd party observer, that Chrome for Android is still a side-project for the Chrome team who are more focused on their own OS (can't blame them there) and their own app store. If Chrome, which is updated more frequently Android Browser ever did, starts to gain momentum it could be the push that is needed to bring mobile browsers to a place where they are an acceptable "native platform". Chrome still doesn't have a version of "home screen apps" like Mobile Safari has had forever and Firefox for Android now has, so it remains to be seen if that is even a goal of Chrome for Android.