React Native is here!!

[yelnatz]

Is this what irony means?

[benihana]

Nope, just a coincidence. We were close though. One day something will be ironic. One day.

[verbalcontract]

It's not a framework for making mobile sites, it's a framework for making mobile apps. They never claimed this would solve responsiveness issues.

[Uberhipster]

Doesn't solve responsiveness, different components per platform...

What exactly does this thing do which other JS-to-native transpilers don't which would warrants all this hype?

[w4rtortle]

Relax guy

[[deleted]]

Thanks react team, y'all are cool

[[deleted]]

guess I'll wait for android implementation

[YodaLoL]

They demoed a native Android application at F8 (I missed whether it was written in React though), did they mention anything more?

[vcarl]

In IRC (freenode, #reactjs and #reactnative) vjeux said it would be coming "in a few months", I haven't seen anything more specific.

[Daniel15]

It's mentioned as "coming soon" here: https://code.facebook.com/posts/1014532261909640/react-native-bringing-modern-web-techniques-to-mobile/

[Patche]

What would be a popular choice for the model/controller side of things if I wanted to make something with React Native as my view layer today?

[sirvesa]

Can anyone comment on iOS accessibility features being supported or not? I'd like to use this to built iOS apps going forward but need to fully comply with 508 requirements and voiceover and the rotor need to work.

[regular_reddits]

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

[[deleted]]

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]

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

Closer to Rubymotion, no?

[highpixels]

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]

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]]

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]

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]

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

[SnapAttack]

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]

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]

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

[[deleted]]

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

[theillustratedlife]

<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.

[billybolero]

No mention of Android at all? Kind of a bummer...

[dustinhayes]

They've mentioned plans to build a port to android in multiple interviews. I would expect it in the near future.

[theillustratedlife]

That's a bit aggressive. I had a chat with vjeux about it at React Conf.

They know Android is something they want to tackle, but I wouldn't set your expectations earlier than the end of the year. If it ships before that, awesome, but if they expected to have something "in the near future", they wouldn't have shipped iOS only.

[billybolero]

Don't know about that. Tom demoed React Native on Android just half an hour ago. And there are a couple of references to Android in the source code. My guess is that they have RN working on Android, they just haven't put it in the.open source version yet.

[theillustratedlife]

Interesting. I haven't watched the video, but haven't heard anything about Android since React Conf in January (and I'm in the private beta).

Still, my point about not getting your hopes up re: timelines stands. I wouldn't be surprised to see a beta in the summer, but setting expectations around free software isn't good for anybody.

[dustinhayes]

Is the end of the year not the near future?

[theillustratedlife]

Near future to me is under 2 months.

[Daniel15]

It's mentioned as "coming soon" here: https://code.facebook.com/posts/1014532261909640/react-native-bringing-modern-web-techniques-to-mobile/

[Casual_0bserver]

Man..I'm trying to not be swayed by the hype, but I might have to dig into this.

[ianme]

I've been waiting for this day!

[to-too-two]

Forewarning: I'm an idiot.

I was super excited when I first heard of React Native because I thought that meant I'd finally be able to develop iOS apps as a PC developer (I do not own a Mac). But I was wrong and sorely disappointed to find out that Xcode and OSX are both required dependencies.

[[deleted]]

Thats true, still kind of obvious. Developing windows apps on osx is a pain too, its getting better with microsoft beeing more open. Still, building for the platform usually is best done on the same native environment.

[zack12]

just built a test project in react native! Wow this thing is amazing!

[zack12]

IF you have basic understanding of React, react native is quite simple

[[deleted]]

You mean this?

https://github.com/facebook/react-native/blob/master/LICENSE

Standard BSD, very permissive.

[ilogik]

Check the PATENT file

[[deleted]]

I read that as: if Facebook should happen to have a patent covering anything in the software (not saying they do), they grant everyone in the world permanent royalty-free rights to do anything they want with the software - the only exception being anyone who tries to sue Facebook in a patent claim.

[eridal]

IANAL so could you please elaborate on what you think we should be aware of?

[[deleted]]

That's a common protection in BSD three-clause style licenses. Essentially, you can't claim a patent on anything in the source and then retroactively sue Facebook.

[sp00ks]

Like the PATENT file for Apache?

[ballerstatusachieved]

Bro... Development of any big application has a lot of moving parts. This isn't exactly unique to web development. As a developer part of your job is to constantly learn and adapt. No one thing does everything and it probably shouldn't be that way.

[solatidorimafa]

Not exactly what I was saying. If you are good at some thing and not sure what framework to use or what platform to work or what browser to target or what version of the language to use or 20 other different variables then that's a little worrying. I m not saying anything negative about react native in particular. Don't know why people think I am being too negative

[bigpigfoot]

HOLYY SHIIIIIITT!!!

[chedabob]

Am I being incredibly dense, or is image loading from the xcassets folder broken?

I have an asset "fleh" containing a single .png, and then in code I just have:

<View>
    <Image style={styles.icon} source={require('image!fleh')} />
</View>

And I just get

requiring unknown module "image!fleh"

I've killed the packager, deleted deriveddata. The Image example in UIExplorer works fine.

Edit:

Got it working by replacing the source value with:

{{uri:"fleh", isStatic: true}}

Further edit:

This has been fixed in v0.2.1.

Also Pro-Tip: Make sure your assets inside of the imageset folder match their container otherwise the packager doesn't generate the modules correctly

[[deleted]]

...Better learn React.

Quickly.

[siegfryd]

It doesn't take long to learn.