HTML5 문제있어?
Many developers consider performance as HTML5’s main problem, but interviewing a number experts in the field the authors of the report consider it as a false target because performance is automatically improving by new generations of hardware, better JavaScript compilers, the option of using Asm.js, etc.. The main culprit in their opinion has to do with politics, more exactly the fact that the major browser vendors are also mobile OS vendors, interested in channeling applications through their respective app stores. Google encourages native Chrome apps, Apple seems to be implementing the latest HTML5 standards but “leaves out performance related APIs, e.g. WebGL.” Also, according to the report, one of the HTML5 myths is that development is easy, but actually development is pretty hard because of missing adequate debugging and profiling tools.
The most used APIs by US Google Play apps are:
The current HTML5 APIs standardization status and browser adoption is depicted in the following graphic:
The next table indicates the APIs that would make the most difference if implemented for their respective route to market, showing how many more apps could be implemented in HTML5 if that happens:
Route to market | API | % of apps |
| Mobile Browser | Power management | 13% |
| Native Wrapper | Power management | 12% |
| Web-to-native Converter | WiFi | 21% |
| Native JavaScript API | Calendar | 1.4% |



