When a product needs to go mobile for the first time on two platforms you have to make a business decision:
1) You can grow the team to tackle both platforms in parallel. 2) You can have the team do it one platform at a time. 3) You can have the team do it one time.
Every option has big trade offs in either cost, time or user experience. There's somewhat of a gradient there as well in terms of code reuse giving the options avaiable right now.
React Native sits somewhere between 2 and 3.
It's really a matter of context for the business. How much time you have? Resources? What does your target user expect?
For a lot of B2B companies, there's just not enough value added to choose between 1 and 2 since you either take more cost or more time to market and your user just needs the feature not the best possible experience.
For a lot of B2C, your product may already be born mobile and you need the best possible experience to compete.
I'm not scared of Swift or Java, But I am frigthened of their ux. Even big apps like eclipse put me off, due to their bloat.
Also frameworks like QT don't offer the same ease of development.
Remember React-Native is currently on version 0.22, and over a year old. IMO it currently offers much better ux than TK/Swing/Qt/...
The day it offers something like Expression Blend, Qt Creator, Netbeans Matisse, Scene Builder, Storyboards ... I will believe it.