Some mobile native features are not yet available in the Cordova Apache libraries, if your project does not make use of any background. Super recommend!
With regard to performance, I have nothing to complain about!
There is a crosswalk library that promises to improve performance of android phones from 4 to 4.4 I make use of them.
An important piece of information is that some libraries have different implementations for each platform so you might have heard that someone had a problem with this or that Mobile OS, but in terms of rules, see the documentation that is not wrong.
Good luck!
And for more robust applications that consume most of the device’s native features, such as GPS, push, contacts, audio capture and etc... Do you think it pays to use the framework or go native? And our biggest problem would be to use a SOAP+XML webservice, and I saw that for that I would have to do an xml to json conversion. @Fabio Nobre
– rodrigo.oliveira
This depends a lot, I particularly prefer native, as it has more control over the code and novelties released in the device’s SDK, has more libraries and your application will be lighter.. But of course this should be taking into account the complexity of the project, if it is something simple I see no problem when using the software cross Platform
– Marco Giovanni
Thank you @Marcogiovanni for clarifying, what project we will develop it is very complex, and I was to do tests on native resources using Ionic. But yet we are coming to the conclusion that the best option will be to go native.
– rodrigo.oliveira