Either cross platform standards are a good thing, or platform specific features are a good thing.This is the classic fallacy of exhaustive hypotheses of the 2nd order, a.k.a. "a false dichotomy" or "the fallacy of the excluded middle".
There is a third possibilty: that both are good, and that which is better depends upon the nature of the app one wants to create. This third missing case also happens to be the reality of the situation — there are tradeoffs, and one selects which is better according to the upsides that one desires versus the downsides one is willing to abide.
(Surely you're not claiming that there are no tradeoffs between the native API and web technologies! I can think of several, not the least of which is the limited rate at which innovation can be brought to the web API.)