On paper hybrid mobile apps let you
1. Write once deploy on multiple platforms (heard that somewhere before in the 90s).
I thought so too when I embarked on my first hybrid app (first mobile app for that matter) for which I was getting paid. After finishing the project, my answer has changed to ‘it depends’. Here’s why.
The other lesser challenge we faced was getting the app to look like a native app. This meant time spent designing and iterating on not only the style sheets, but also the user interactions and app transitions like a native app. For a pure native app, there is no such effort because the styles and transitions come out of the box. The bigger catch being that customising the app for another platform means more work. So much for platform independence.
The Moral of the story:
1. Hybrid apps are not exactly platform independent. It takes some time to port them, depending on the UI complexity.
3. Code Sharing can be done amongst platforms, only if you design your abstractions right.
4. The tools for profiling and debugging hybrid apps are non existent or not good enough (at least for now on iOS)
If you read the previous link on how cool hybrids were at Linkedin last year, then also read why Linkedin dumped Html5 and went native this year. Looks like the guys at Linkedin had similar issues.