3 ms·
Thank you, this is exactly the kind of insight I was hoping for. My understanding is that RN allows you to fall back to native code wherever necessary. Is tha
by tempestn 10y ago
Thank you, this is exactly the kind of insight I was hoping for. My understanding is that RN allows you to fall back to native code wherever necessary. Is that not as easy in practice as in theory? It just seems like at worst it would allow you to share many parts of your application between iOS and Android, as well as possibly your web app, and then anything else could be built natively as necessary. As someone with no experience using this tech, that seems like it would simplify and save time, both in initial development and future revisions, but avoiding duplication between code bases. I can't help wondering if these teams tried older hybrid app frameworks like PhoneGap, found them lacking, and have written off RN as being basically the same thing, while it's actually considerably more powerful. It's also possible that adding that layer adds more complexity than I'm accounting for, and really isn't worth it for the duplication saved.
- rkho 10y agoI actually haven't used RN with the intention of falling back into native code before. I was working on contributing an RN-built component as a CocoaPod dependency into an existing Obj-C code base but that project ended up not getting very far for reasons beyond my control. Before it was scrapped, we were exploring performance issues in loading up RN in each individual component.