3 ms·
>I wonder if the issues that they encounter are more a symptom of trying to "bolt on" react-native. I suspect that your experience as a single developer has VE
by on_and_off 8y ago
>I wonder if the issues that they encounter are more a symptom of trying to "bolt on" react-native.
I suspect that your experience as a single developer has VERY little in common with what the 100 people Airbnb team is doing.
I am not trying to say that you or your work are in any way lesser than the one of a big team but it is a very different problem.
I have worked in such an environment and even with native, we had to code a ton of custom Views in order to get exactly the specific behavior we had in mind.
There are tons of little tweaks that demand to exploit the platform to 100% that you can in a very large team and that you would just avoid a single dev because you don't have the time for this kind of stuff at big scale.
- chrisco255 8y agoHe's not wrong though. Other big teams have had success with React Native including Skype and Office teams, as well as Instagram. When I read this article by Udemy, where they started with 1 dev for each platform and had a mere 3 or 4 react Native features and then ended up with 7 or 8 mobile devs split along platform lines, I wondered if 2 or 3 react native devs couldn't achieve the same thing if they actually tried to share 90% of the code across iOS and Android and went all in? The productivity boost is there if you embrace it.
- on_and_off 8y agoRN is a compromise, and a very big one. It might be the right choice for some products but my experience on complex products more closely reflects the Airbnb one than the myth of 'only know js, write once, run everywhere'
- filleduchaos 8y agoI wouldn't exactly call the Skype app a success. Easily the worst communication app on my phone by far. To be fair, a lot of that is in the product vision and design and not entirely React Native's fault.