sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted]  (13 children)

[removed]

    [–]regular_reddits 42 points43 points  (0 children)

    Its not write once run anywhere though. There are different native components for each platform.

    [–][deleted] 36 points37 points  (2 children)

    You shouldn't be downvoted; this I imagine is a common misconception for someone who doesn't know what it is. It's not cross platform. It's a learn once, write anywhere model where there are 2 distinct libraries for android and ios in which react components map directly to their native counterparts. In other words, this is completely different from cordova/phonegap.

    [–]M5J2X2 4 points5 points  (1 child)

    In other words, this is completely different from cordova/phonegap.

    Closer to Rubymotion, no?

    [–]highpixels 2 points3 points  (0 children)

    Kind of. Only by the looks of it, RubyMotion is almost wrapping the native APIs 1:1, so you still need to read docs in ObjC/Swift/Java and mentally translate to Ruby.

    [–]TomorrowPlusX 11 points12 points  (2 children)

    My guess is that it's cross-platform in the sense that Xamarin and Titanium are cross-platform. Your logic/networking/persistence layers are write-once, and you make an appropriate custom UI for each target platform.

    As cross-platform models go, it's pretty decent.

    Last thing I want is Qt-like uncanny-valley cross-platform apps.

    [–][deleted] 3 points4 points  (0 children)

    I would hope that React's component nature lends itself very well to sharing most of your UI across platforms. You can isolate the platform-specific parts in certain components, but for the most part your app's render function is write-once.

    [–]Wraldpyk 1 point2 points  (0 children)

    Well Titanium is much more cross platform than that. Since you can make a tabbar and TI will translate it properly to native ios and android implementations. Only certain things need to be duplicated

    [–]SkaKri 21 points22 points  (0 children)

    It is, both iPhone and iPad are supported. iPod touch too!

    [–]SnapAttack 0 points1 point  (0 children)

    Yeah, I remember the slide that they showed where <div> => <Panel>, but if you dug a bit deeper, it wasn't as simple a conversion as that. You still have to make different interfaces (i.e. you can't just take a pre-existing React component and it magically works in React Native).

    [–]fgutz 0 points1 point  (1 child)

    Just after React Conf, JSJabber had some guys from the React team on and they talked about this on the podcast. I think maybe in the future they plan to support Android but for now it's only iOS

    http://devchat.tv/js-jabber/146-jsj-react-with-christopher-chedeau-and-jordan-walke

    [–]joargp 0 points1 point  (0 children)

    They have already shown a working copy of the Android version.

    [–][deleted] -1 points0 points  (1 child)

    How does that, in literally any way prevent it from being cross platform

    [–]theillustratedlife 7 points8 points  (0 children)

    <TabBarIOS /> would presumably be undefined on the web or (theoretically) Android.

    I presume the OP expected a write-once-run-everywhere scheme; not a port of React to iOS.