Agree with the author. I tried out the game and while it's a fun little game and a neat concept, there were a bunch of small glitches and issues that cause it from feeling -great-, and it doesn't feel native or perhaps the author just didn't bother to add specific support for the iPad.
To me the issue is clear cut -- if you're selling direct to the market and you care about your users at all, UI should always use native components. The choice of language is secondary, but personally I don't see how it would ever be better to deal with differing and inconsistent web view standards -on top of- the differences between OSes and devices. On Android, these alone provide more than plenty of enough grief.
The advantages of coding direct to the platform are many:
- higher efficiency and lower battery consumption,
- smaller downloads,
- better performance, particularly on older devices,
- fewer glitches,
- and finally, an app that just "feels right".
Code reuse can still be achieved by using C++, Rust or another layer to share code. If most logic lies in the UI, writing it twice may be OK along with tailoring the UI more closely to the platform paradigm.
There are different tradeoff so involved here, but to me, the increased user satisfaction is worth the additional effort, and seeing how glitchy these web apps can be, I'm not at all even convinced that it -is- additional effort.
To me the issue is clear cut -- if you're selling direct to the market and you care about your users at all, UI should always use native components. The choice of language is secondary, but personally I don't see how it would ever be better to deal with differing and inconsistent web view standards -on top of- the differences between OSes and devices. On Android, these alone provide more than plenty of enough grief.
The advantages of coding direct to the platform are many:
- higher efficiency and lower battery consumption, - smaller downloads, - better performance, particularly on older devices, - fewer glitches, - and finally, an app that just "feels right".
Code reuse can still be achieved by using C++, Rust or another layer to share code. If most logic lies in the UI, writing it twice may be OK along with tailoring the UI more closely to the platform paradigm.
There are different tradeoff so involved here, but to me, the increased user satisfaction is worth the additional effort, and seeing how glitchy these web apps can be, I'm not at all even convinced that it -is- additional effort.