martin_bigio
Re:React Native at Instagram
on Tuesday February 07, 2017 @07:49AM (#13588980)
Packager has gotten pretty stable lately, you shouldn't need to restart it anymore. In regards npm modules, you only need to do so when upgrading dependencies which doesn't happen that often.
We also use yarn, an npm client FB built from the ground up to removes some of the pain with npm's one: https://code.facebook.com/posts/1840075619545360
Re:React Native at Instagram
on Tuesday February 07, 2017 @07:46AM (#13588959)
couldn't agree more with @realharo. IMHO C++ step learning curve is a no-go for product dev.
Re:React Native at Instagram
on Tuesday February 07, 2017 @07:44AM (#13588956)
what's the problem? If it's a generic error message that's s server-side issue unrelated to RN the team is working on fixing.
Re:React Native at Instagram
on Tuesday February 07, 2017 @07:42AM (#13588946)
I've only seen such thing on infinite non-optimized listviews on old Android crappy phones, but, new listview infra that solves this is coming up soon :)
Re:React Native at Instagram
on Tuesday February 07, 2017 @07:38AM (#13588934)
JS code run on JSC, bridge modules are implemented on objc/java
Re:React Native at Instagram
on Monday February 06, 2017 @08:43PM (#13586212)
Although the Instagram website is a React App we are not reusing any code atm. This is something I personally want to explore at some point though.
Re:React Native at Instagram
on Monday February 06, 2017 @08:42PM (#13586208)
Great Q. React and React Native use difference "renderers". I believe that with the right pattern to use a different set of low level components you could manage to reuse a big chunk, but this isn't something we have tried so I'm not that sure.
Re:React Native at Instagram
on Monday February 06, 2017 @05:44PM (#13585015)
Brace yourself, FlatList is coming :)
Re:React Native at Instagram
on Monday February 06, 2017 @05:42PM (#13584998)
No, we didn't use any of those. For unit testing we used Jest <3 and for e2e an internal library developed by FB
Re:React Native at Instagram
on Monday February 06, 2017 @05:08PM (#13584708)
Great question. First off, worth mentioning there are many performance metrics you might want to measure. On one hand start up times, but since you specifically mentioned Save, I assume you want to learn more about scroll perf (i.e.: dropped frames, memory usage, time to render next pages, etc).
We don't have numbers we can share but but the React Native team is working on further improving this. Check out Spencer's commit (https://github.com/facebook/react-native/commit/a3457486e39d...) for a sneak peek of what's coming up :).
Re:React Native at Instagram
on Monday February 06, 2017 @05:00PM (#13584617)
Oops, that was an internal link - fixing now.
Re:React Native at Instagram
on Monday February 06, 2017 @04:58PM (#13584592)
No plans for powering camera using React Native for now. We already have great native infra for that and regardless, IMHO RN might not be the best technology to implement those kind of immersive ultra-performant flows.
We see space for React Native to grow inside of Instagram on flows similar to the ones mentioned on the blog post.
Re:React Native at Instagram
on Monday February 06, 2017 @04:37PM (#13584356)
@martinbigio here in case anyone has questions