1. What actually can be coded Hybrid?
Some things can only be done natively while others will always require a hybrid code. Follow a general rule- If it is something you have seen a website do, it can be done entirely within hybrid code and if not, it likely requires native code.
2. Look into the future!
If after reading the above section you found that all the current features of your app can be supported by a hybrid code then do think about any possible future version for your current app, which may require some coding, a hybrid code just can’t provide. The results may be disastrous. You may have to reproduce the whole code natively once again. This will require a whole lot of capital, time and workforce.
3. Know the limitations!
Hybrid Apps have a numerous limitations. Knowing in advance what’s hidden in the ackage is always a plus point. Animations: Hybrid apps don’t handle animations with much fluidity. However this is can be designed around. App fluidity: Hybrid apps often appear sluggish during page and state transitions. For example, the very popular slide tray open animation looks and feels significantly worse in hybrid apps. Memory usage: Memory usage is a real concern when it comes to mobile apps. Hybrid apps do take a lot of space as compared to native mobile app. And if your app has to accommodate into a small memory space, its better not to go for a hybrid app.
Going hybrid may land you in laurels if you make your choices correctly. Just keep in mind, that before making any choices get some proper research done.