The truth is, that you have to be absolutely positively sure that you need a HTML5 engine and not something else.
All the 'apps' that we publish to iOS and Android are wrapped HTML5. Not native. This is enough for a lot of things, but brings along some special circumstances. If this is good enough for your use case is something that only you can answer I'm afraid.
The exports are relying on 3rd party tools and wrappers, and monetization (iAP, ads) do so, too.
So you have to ask yourself the following questions:
- Is HTML5 good enough for your purposes? (to find that out test your apps within browsers on the phones, the results are comparable to what you might get once they are wrapped/exported/packaged). Without these tests no one can know. This can be done with the free edition.
- Are you comfortable keeping up with a 3rd party environment of plugins and build tools? This changes often. One week it works, the next week it's all broken, the week after it works again but with a different workflow and all tutorials are invalid. This is especially true for ads and iap. This is also something that the C2 vendors cannot really fix. You have to do a lot of research yourself.
I found that 90% of the problems people rant about on the forum can be traced back to the fact that a HTML5 engine was a suboptimal way to go for what they had in mind.