React-native: some context and a few wrinkles

React native is a way to build iOS applications using Javascript. The idea is not radically new, since you are probably aware of PhoneGap/Cordova and others like that. I myself played with something similar long time ago.

The interesting thing is that React native follows the steps on ReactJS, a Javascript library that provides wonderful performance in updating the DOM.

It also moves towards CSS into Javascript. You may think “What a crap idea moving CSS into JS?”. At least I thought that myself, until I watched the below slides.

Besides, one of my colleagues have recently developed a wonderful SPA using React, so I wanted to give a test to get the idea.

So OK, I followed the instructions, installed the dependencies, created the project and launched it.

It fails with a red screen showing a lot of errors related to flow. It turns out the version you get by default when following the instructions is flow 0.10.0. And there is some kind of incompatibility. So you need to install flow 0.9.2

$ brew unlink flow
$ brew install

So now you relaunch and you get a wonderful iOS emulator. Hurray!!! Let’s tweak. The screen tells you that you should tweak the file index.ios.js.

You go to your XCode project and you can’t find the file anywhere. Where the heck is it?

It turns out you have to edit the file OUTSIDE of XCode. Which for me is madness.

Apart from that, the experience is being quite interesting. On thing I like AND dislike is that the components that React Native tells you to use are direct mapping of the iOS ones. Which means there is a full translation from JS to native code.

Lots of things to learn. But very good performance (it is not a WebView at all).

So good idea, but some wrinkles pending.

First published here