I think it's eventually been acknowledged that the phonegap approach only really works for a certain subset of apps - those where information display is the pri

I think it's eventually been acknowledged that the phonegap approach only really works for a certain subset of apps - those where information display is the primary goal, and UX and interaction aren't more important than fast development and just getting your app on as many devices as possible. However if you're really aiming for the smoothest UX, there's still just a bit too much delay and kludginess with HTML5 controls in the browser/webview, and nothing will beat native application controls. I think that difference is pretty small now, for the vast majority of apps and what they need to do, but it definitely still exists. Recent cross-platform frameworks like React native certainly seem to buy into the 'native is king' mindset by focusing on allowing you to write as much cross-platform shared code as possible, in a single language/framework, but accepting that you must, with some abstractions, write the final UI layer with the target device/platform in mind. I.e. more learn once, write for every platform, run on every platform than learn once, write once, run everywhere, which seems just as much a pipe dream on mobile devices as it ever was!