It depends on how many target systems you have and the abundance of resources?
If you're targeting iOS only type devices, I'd say go the native route, or native with UIWebView mixed together. If you however have multiple devices such as iOS/Android/Windows, Blackberry, I'd go with Cordova/PhoneGap. The seamless integration with these systems are nice, and plus you maintain a single codebase.
However when you use the Cordova/PhoneGap route, the native devices functions aren't directly channeled, and there is a lag between various transitions, not to mention overhead with the codebases.
If you have unlimited resources and time constraints, and employee resources, develop native iOS, and native Android, with their WebKit as the primary interface control, and utilize each respective operating system's features available.
I do have to say Cordova, in terms of utlizing Android, and iOS's builtin function has gotten drastically better. They've tapped into the Multimedia Components, the gyroscope, the MAP Kits, Accelerometers, and GPS's of the respective devices to say the list. And as I understand they are continuing to expand. Single code base is nice! But that's if you have tight
resources. If you have a big company with numerous programmers with numerous disciplines, go Native 100%.