<story><title>A Deep Dive on React Native [video]</title><url>https://www.youtube.com/watch?v=7rDsRXj9-cU</url><text></text></story><parent_chain></parent_chain><comment><author>joemaller1</author><text>I&amp;#x27;m very excited about this, but can someone &lt;i&gt;please&lt;/i&gt; write something down? The videos are nice an all, but information-wise they&amp;#x27;re incredibly low-density. If I have an hour to spend on React Native, I&amp;#x27;d rather read for 10 minutes and experiment for the remaining 50...</text></comment>
<story><title>A Deep Dive on React Native [video]</title><url>https://www.youtube.com/watch?v=7rDsRXj9-cU</url><text></text></story><parent_chain></parent_chain><comment><author>pavlov</author><text>React Native is a cool project, but the deafening hype is slightly puzzling.&lt;p&gt;Creating and calling native UI components from JavaScript is nothing special in itself. It&amp;#x27;s obviously possible to do it from JS just as well as from any other language -- you just need to provide the API. There you have two choices: either a bridge that translates the native API directly, or a wrapper class hierarchy.&lt;p&gt;Examples of bridges include Xamarin&amp;#x27;s Mono that lets you build iOS user interfaces in C# code, and RubyMotion that lets you build Mac UIs in Ruby. Because these are bridges, the entire Cocoa API is exposed. The downside is that the bridge does nothing to smooth over platform differences: you can write in C# on all platforms, but you still have to learn Cocoa.&lt;p&gt;A prominent example of a wrapper API is Titanium Appcelerator that lets you build cross-platform mobile apps. Another good example is GTK+ for desktop apps: it&amp;#x27;s smart enough to leverage native Windows components where possible, but the GTK+ API is higher level than that of native Win32.&lt;p&gt;React Native is primarily in the latter category. Based on jordwalke&amp;#x27;s comment in another HN thread, they currently have cross-platform wrappers for View and Image:&lt;p&gt;&lt;a href=&quot;https://news.ycombinator.com/item?id=8965044&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=8965044&lt;/a&gt;&lt;p&gt;But it appears you can also create platform-specific views, and for that they presumably have some kind of bridge. (It could also be that they provide manually written wrappers for platform-specific views, e.g. UIMapView becomes a &amp;lt;Map&amp;gt; and so on.)&lt;p&gt;In sum: React Native doesn&amp;#x27;t magically translate your JS+HTML app into a cross-platform native app. They&amp;#x27;re a long way off from having a full cross-platform API (unless your app is so simple that it can be described in terms of &amp;lt;View&amp;gt; and &amp;lt;Image&amp;gt;). And, like all wrapper APIs, there is a degree of impedance mismatch between the underlying platform implementation and the cross-platform interface on top.&lt;p&gt;There&amp;#x27;s a lot to like about React Native, though. The layout model and binding logic seems cool. The React team&amp;#x27;s accomplishments in the browser environment are impressive. With time, React Native could become for mobile what Qt is on the desktop -- and that&amp;#x27;s high praise in my books.</text></comment>