3 ms·
Counter-anecdote from my company, which also ships a RN app on both platforms: > The RN promoters promised all sorts of benefits about sharing code between pla
by brundolf 4y ago
Counter-anecdote from my company, which also ships a RN app on both platforms:
> The RN promoters promised all sorts of benefits about sharing code between platforms and how the performance would be as good as native, and how the UI would look like native, and none of that actually materialized
We've pretty much seen all of this materialize. Our native apps perform great, look great, feel native. There's a tiny bit of platform-specific code around the edges, mostly for integrations with third party libraries. But 90+% of our code is shared, idiomatic React code, and mostly only the team lead ever has to dig beneath that. The whole team for both apps together is around 10 people, and most of them never have to step outside of JS. They also have an easy time making changes in our React web app (and the web team has an easy time making changes in RN) because the skillsets largely overlap.
> RN teams can dynamically push code changes to production apps and we no longer have deterministic, reproducible builds
Ok- but nothing about RN forces you to use the dynamic code push feature. In fact, we just decided as an org that we wanted to reduce our usage of it. This sounds like an organizational issue.
I have to ask, what kind of app were y'all building? I could see this varying widely based on that. Ours is a fairly straightforward finance app