@bntzio Great question. So far I think there hasn't been enough such features that React Native hasn't supported after a new iOS version (I think there has only been one major bump since RN is out). Force touch didn't work out of the box, but it took around 2-3 weeks to get supported I think.
On the flip side, and this is true to all frameworks such as React Native - when a new iOS is released you don't have to go and refactor your code due to language changes, IDE changes, or Cocoa API changes because you're not dealing with that API directly. That's an amazing (and surprising) thing to have on your side.
Traditionally, before every major iOS release our company went into "Red Alert Mode", but with React Native - you just sail through, since your codebase is mostly Javascript.
So to sum up - you don't have 0-day support for completely new iOS features (you can support these yourself if you can, since RN has a very open structure for that), but you do get bubblewrapped and protected from API and language changes that happen between major iOS bumps.
I just started with React and find the whole ecosystem extremely confusing, considering all the different building blocks you can choose from. I will definitely have a good look at this book when I start on React Native. Resources like these are very helpful to me! Thanks!
I will take a deeper look at the book, but I think some of the assumptions made in the introduction are a bit premature. React-Native is new and we will look back in a couple of years and see where it fits in the long line of cross-platform solutions. The developers of the solution have had the ability to learn from the platforms that came before so therein lies an advantage but only time will tell if it will really be the "silver bullet" or any better than those solutions that have come before it.
The Little Metrics Book
GOT Spoilers 2.0
The Little Metrics Book
Achieved
The Little Metrics Book