[tluyben2]

Clients want apps in stores. It's much easier to promote than mobile web apps. And even though for a nicely looking, nicely working cross platform phonegap app you will be paying a lot of money (the tweaking takes a lot of time between different phones/pads), it is still cheaper and faster than going native.

We advise native for productivity apps and such; day to day use apps should be fast and snappy, while promotional apps / marketing apps should look pretty.

[matwood]

it is still cheaper and faster than going native.

It sounds like you make apps for people. Assuming you have someone on staff who knows iOS and someone who knows Android is it still faster to do it in PhoneGap? We attempted a phonegap app which ended up failing because of performance reasons. We rewrote the app in native iOS and it didn't take nearly as long as the original phonegap did with the constant tweaking in an attempt to get it to look and perform acceptably.

[tluyben2]

It depends definitely on the app; we have been in the 2 camps. The problem is that often we are also asked to make the mobile web site and then you have 3 very similar things in Phonegap while native you need to write 3 different things. I do agree though that for a lot of apps native is faster to write if you target one platform.

And the Phonegap experience isn't really good unless you spend a huge amount of time. Webview is just not very good; you need something which is native but crossplatform to replace it; everything we tried so far (appmobi, appcelerator, rhomobile) actually was worse than Phonegap/jqm to get right. But we keep at it as we know what our clients want.

Often the Phonegap version is treated like a prototype; then the client saw it and knows what they want; after that they have it rewritten to native on the platform which makes them the most/gets the most attention (etc). Which is almost always iOS by the way.