3 ms·
This post hits the nail right on the head. React Native is absolutely a business win, but a developer loss. PM/Manager can advertise shared code base, and eve
by rubicon33 4y ago
This post hits the nail right on the head.
React Native is absolutely a business win, but a developer loss.
PM/Manager can advertise shared code base, and even sometimes hire less, or at least argue that they should be able to hire less, but really it ends up being a nightmare for the teams that have to use RN for all the reasons you've listed.
I work for a company that builds a very advanced mobile application (not your basic CRUD) and unfortunately the previous frontend manager decided on RN. The result is a 50% RN 50% native codebase which is a nightmare to traverse, and impossible to hire for. We need effectively 3 teams, RN / JS / TS, Java, and Swift.
The complexity added is absurd. The tooling, typescript, building, all of it. Going completely native drops all of that and allows developers to focus entirely on their craft - building rather than context switching all day long between JS / TS and Java / Swift.
Hands down the worst part is the performance. There is a very obvious performance hit in nearly all UI interactions.
If you're building out your mobile team and building a complex app, I highly recommend you do not use RN.
- brundolf 4y ago> I work for a company that builds a very advanced mobile application (not your basic CRUD) I think this is your problem right here. By nature, most higher-level abstractions will work better for mainstream/expected use-cases. If you're really pushing the envelope, I can see why an abstracted framework wouldn't work for you. For my company (which does have a straightforward CRUD app), it's worked out great. Very little native code on either platform