4 ms·
> From now on, I won’t be building any more native apps It looks like the author blogs exclusively about JavaScript. What native apps has this author built?
by millstone 10y ago
> From now on, I won’t be building any more native apps
It looks like the author blogs exclusively about JavaScript. What native apps has this author built?
- on_and_off 10y agoWell, at least it won't be too difficult for him to commit to this. More seriously, this kind of comment seems to almost entirely come from javascript devs.
- sotojuan 10y agoThe article is by probably the worst blogger in the JS community. Full of hyperbole, biased if any research, always trying to sell his courses, and strange sources (dude quotes himself fairly often).
- ericelliott 10y agoIf everybody likes you, you're not being honest enough.
- ericelliott 10y agoI admit, I don't do a lot of native mobile development, but of course I have participated in the production of many mobile apps, mostly servicing middle and back-end tiers using JavaScript and Node (because I specialize in JavaScript). For instance, I wrote a bunch of the code the powers mobile notifications for mobile apps connected to the Adobe Creative Cloud. One of the biggest problems I saw with maintaining separate apps was that we struggled to keep feature parity across the products, and that would frustrate our users when they switched back and forth between the web app and the mobile apps. Features they depended on in the web app didn't exist in the native app or vice verse. Yet another compelling reason to choose the universal web platform technology.