What to expect from React Native

Two weeks have gone by since the React.js Conf and the announcement of React Native that left all of us lined up, eagerly waiting to build our next apps with JavaScript.

What we saw demoed at the Conference was a demo of what engineers at Facebook proved to be possible with the kind of abstraction offered with the View Layer offered by React.

Even if what we saw was very convincing must be remembered that the project wasn't really ready for prime time, meaning it wasn't really ready to be Open Sourced yet.
Android version of React Native has been spoilered but never shown. iOS version was really a barebone, preassembled project, that the lucky guys attending the event were left tinkering with.

In the meantime we can imagine (hope) that Facebook is unloading more resources to the project to speed it up and keep it with the momentum and the hype created with the announcement.

So what to expect in the coming days (or weeks)?

Some sort of generator is needed to spawn new projects, both iOS and Android, but we cannot possibly know until it's released.
APIs are going to change both on the markup (JSX) side than on the native bridge side. But, again, we cannot know this until everything is official.

Even if, being Open Source, there could be other implementations, it doesn't seem possible that the actual JavaScript implementation of the CSS Flexbox is ever going to go away. So, again, if something, bid on it and learn Flexbox.
It will look something like:

If you're already experienced with these concept then consider investigating on the Flux Architecture.
React is a View Layer and you're left to figure out how to assemble the rest of your code.
Well, Facebook did the homework for us, but turns out different people (and companies) figured out a Flux implementation that best suited their needs.