Would I use PhoneGap again? Maybe. In my experience PhoneGap doesn't bring much to the table. The core UI element (a thin wrapper around the native WebView) is

Would I use PhoneGap again? Maybe. In my experience PhoneGap doesn't bring much to the table. The core UI element (a thin wrapper around the native WebView) is easily replicated in less than 100 lines of code. The plugins I used were very inconsistent between Android and iOS, so in the end I spent a lot of time either wrapping them in JavaScript to make them consistent, or (re)implementing missing plugins on one platform or another (or both where they were substandard). Yeah, it lowers the barrier to entry if you are a web developer looking to wrap your web site up as a native app, but if you have even basic skills in your target platform(s) it's very easy to replicate its functionality and you get finer control over how it starts up (which was an issue for one app I made) and your distribution file will be much smaller. Would I use HTML5 to create hybrid apps again? For the right project, absolutely. I think other people have mentioned that there's currently no "one size fits all" solution on mobile, and JavaScript frameworks, associated tooling, and mobile browsers are definitely still in their infancy when it comes to building full-blown client-side HTML5 applications. This is one space where things are happening incredibly quickly, and even with what's available today(1), you can get acceptable results. For a small-medium sized business that simply doesn't have the money to develop and maintain applications targeting every platform (including web) hybrid development is a very appealing option. (1) disclaimer: after some investigation of Backbone/Angular I was unimpressed with their ASP/JSP on the client model and rolled my own MVC framework, but literally millions would say I was wrong to do so