[Macsenour]

Actually, as a game producer for over 20 years, I'd say the biggest problem with HTML5 games is audio. There isn't a solution that is universally adopted at the moment.

The article basically says, make good games, which really has nothing to do with the tech of HTML5. I've had a few of my titles featured by Apple and I am often asked what I did to get them to notice my title. The answer is extremely simple: "make good games".

[kevingadd]

The Firefox devs are at least working on adding in Chrome's audio API, so once that's out you'll finally be able to use one codebase for all your audio, as long as you don't care about IE or desktop Safari...

But yeah, audio is a big problem. I'd argue that caching and content distribution in general are probably the other big problem. Having to roll your own complete solution for downloading and caching assets for every game is a pretty big problem, in part because the available options for storing assets on a client are pretty miserable in HTML5.