I've been looking at this also, in part because I have a subscription to Adobe Creative Cloud which includes PhoneGap.
The word on the street is that PhoneGap is okay for simple stuff, but isn't really aimed at gaming.
The crux of the problem is what HTML5 browser bits are available on a particular phone. Nobody seems to be getting this right 100%. Right now Construct 2 is recommending Ejecta for iOS and Crosswalk for Android, but CocoonJS is hanging in the background.
I'm more interested in Android and my impression is that Ashley likes to export for Crosswalk because it has more HTML5 bits than Cocoon. But there's the tradeoff of a big company like Intel (Crosswalk) supporting something small, vs. Cocoon, which sounds like a small company with their developers in Spain, but their company is one the line if they can't do it well, whereas Intel has many other things on its mind.
My own experience is that Construct 2 exports flawlessly to Firefox OS, pretty well to Windows, and only sometimes if you're lucky to Android and iOS.
And I have to compare that to GameMaker, which is you pay them lots of money, will export to native iOS and Android. But I find GameMaker hard to wrap my head about and the people running it seem not very responsive. I like Construct 2 because the people here will answer questions and the developers seem to be really on top of things and communicate well. Ashley's blog is an education in itself. Of course the main issue is where does HTML5 fit in, and I think we're still moving toward HTML5 as a universal platform, but a little too slowly.
When browsers are good and standard on phones, that will be the day that everything just works. If it wasn't such a quagmire, I'd be more interested in Windows because at least they use a standard browser. Now that IE 11 supports WebGL, I have more hope for them, but it sounds like no one is using their phones anyway. (Although hiring 25,000 people from Nokia may change things.)
So the answer is nothing is working perfectly and that the answers seem to vary for iOS and Android. But both iOS and Android are pushing out new versions every day and they seem to be committed to HTML5, so I'm still hoping that Construct 2 will meet them somewhere in the middle.
I keep coming back to Construct 2 because they are improving by leaps and bounds and the communication here is very good, both among the users, and the devs!