4 ms·

> 1 iOS dev > 2 Android devs > 1 PM > 1 Designer They didn't have a single JS/Web developer at the start. > There was also an issue that caused a crash bec

by voidr 8y ago

> 1 iOS dev > 2 Android devs > 1 PM > 1 Designer They didn't have a single JS/Web developer at the start. > There was also an issue that caused a crash because one version of npm had a `package.lock` and the other didn’t which caused us to install incorrect versions of a dependency across a React Native upgrade. This issue I would attribute to their lack of experience or knowledge of how NPM works, not to ReactNative. > Lastly, CI for the iOS project was a pain point as well. We now had to add an npm dependency layer and make sure those were being updated properly before continuing the install. This added nontrivial amounts of time to our build step. The same way if I would add Java to my JavaScript project, my build time would increase. There are a lot of legitimate complaints in the article, but a lot of their issues stem from their lack of web experience.

emilioicai 8y ago
They state the iOS dev had some experience with JavaScript and web. I wonder how much and how old that experience was.
akura 8y ago
Yeah, the team makeup is the interesting aspect for me. It seems they took an existing mobile engineering team and had them integrate react native. Our experience was opposite in that we had a web/js team and decided to go to react native as a way to deal with a mobile app that we couldn't maintain well (and couldn't justify the hiring of dedicated devs for). React native gave us an avenue to utilise existing skills and overall we found it pretty positive.