Hacker News Reader

Interesting so the idea here is that developers of native apps will use high level ready made widgets/components but on the web they'll more likely try to make them from scratch.

I believe that's what Google has been trying to solve with polymer and web components.

View on HN

It's funny because native developers put more time, effort, and budget into creating rich experiences than web developers do in general, and Ionic doesn't readily enable web developers to create the same caliber work.

You still end up putting in the time, effort, and budget native developers will, so what's the gain?

I think the gain that people are aiming for is "write once, run everywhere."

Especially if you're a lone developer - it's one thing to learn the intricacies of one platform (like web), but learning the ecosystems for Android, iOS (maybe you don't even own a mac to develop with), and native desktop apps... it's just too much work for one person. But if you could just write it once and have a good experience on each platform, wouldn't that be amazing? I guess that's what React Native is trying to solve, too.

Reply on news.ycombinator.com