Audio is one of the domains where developers try to get every bit of performance out of the device. On the other hand, the Web Audio API looks like an high-level API with a lot of constraints for developers. What does the web platform need for the Web Audio API to be competitive with native audio? What problems does the platform have that can be solved today ?

Paul is an audio developer at Mozilla, working on the Firefox web browser. He works on the Firefox Web Audio implementation, as well as the platform-specific audio code on all platforms, and WebRTC. He also co-edits the Web Audio API specification at the W3C, and is a long time guitar player.