[mattezell]

Thanks for the writeup, @EO-IO. As other have said, it's a 'skeezy model', but as you've said, you know this and were sharing for the lessons learned more than to promote this model - which I can certainly appreciate. All in all, I found it to be a pretty good read - and a peak into a world of generating revenue that I may have not otherwise been as aware of.

I do have a question. As I read, it does seem that you're driving the point of 'native app' pretty heavily without substantiating the emphasis; as if it's a large feature/benefit/sales-point. So, "Why native?" As primarily a hybrid developer currently (Angular 4 + Cordova / some Ionic), there have been leaps and bounds made in the arena of hybrid dev - and arguably the entry point for hybrid dev is much lower than it is for native. Of course you could still have created the same business with either stack, but since the article seems to be promoting 'native', I was hoping you could share some insight into what made native superior to hybrid here?

Thanks!

[EO-IO]

Thank you for the kind words. I took that decision years ago, when hybrid dev was still struggling. If you're asking why I'm not switching now, I just don't have it in me to invest more time in the tool, even though it would significantly cut costs.

[mattezell]

Got ya... As someone who's worked in hybrid since ~2014, I completely understand where you're coming from - we've come a long way. Hybrid is an interesting dev space currently - so much tooling (Ionic's Creator, View, Deploy products, for example), flexibility and near-native experience in most applications. Anywhos. Thanks again!