3 ms·
come the f-- on. ionic is using css transforms on a good day. At least famo.us is trying harder and react.js is going native. I'm still on the fence if the extr
by sebringj 12y ago
come the f-- on. ionic is using css transforms on a good day. At least famo.us is trying harder and react.js is going native. I'm still on the fence if the extra effort is worth it but have been dabbling in java and objective c/swift. Worst case, I'll have a lot more to offer than just being a JavaScripter even if its damn hard.
- ericmsimons 12y agoI think the other comment thread on this post (https://news.ycombinator.com/item?id=9070906 https://news.ycombinator.com/item?id=9070906) addresses your points here. Not that you're wrong, but just that the experience for the user is identical in most cases.
- sebringj 12y agoIf you are only doing a-z sure. Its native speed just sitting there too. But doing anything interesting is going to take some chops. You could write a native plugin for phonegap twice, true dat and you're still in js mostly but you still had to do something custom to really get something worth doing that stands out if you are needing to integrate with native functionality.
- ericmsimons 12y agoDefinitely, if you're building something with complex UI requirements (aka "interesting" :) hybrid apps probably aren't the right choice. However, most apps typically don't fall into that category - so if you know angular/frontend, there's now virtually no incentive to go native (again, unless you're making a complex UI).
- sebringj 12y agoabsolutely agree on that one, I'm still learning ios/android native anyway, already have famo.us down pretty decently, going to try the create plugin route because i feel the gains on UI are surpassing doing it all native for both but just doing famo.us vanilla rather than angular because not convinced perf is great on that
- deleted 12y ago[deleted]