Having done both, this is laughable, native is always the correct way, you may get away with HTML5 for a few months but it will not scale, ask Facebook. I can'

Having done both, this is laughable, native is always the correct way, you may get away with HTML5 for a few months but it will not scale, ask Facebook. I can't be bothered to go into a full reply but... Continuous deployment: No, your users don't want their apps changing on their phones without any interaction. "Why did app XYZ just look totally different, I didn't update it" ? They are used to an update strategy and they might not want your amazing feature you just wrote. One code base: I get this, but this is not the way you do it, you should create a library and your applications are thin views of this, using cross platform tools like Mono-esq. Design advantage: Meh, you have design patterns you must follow on each platform, the amount of HTML5 + Phonegap applications that look like iOS on Android on Windows phones is laughable. You can do exciting things on the platforms without thinking that CSS3 is the only way to do it. Speed and user experience: Never in a million years, I'm not a purist, I tried using Phonegap for projects, but it always came down to speed on all devices being less than native, so why would they use ours?