React Native for Android

Post by squints » Mon, Sep 14, 2015, 8:53 PM UTC

aianus wrote: post #57

jbigelow76 wrote: post #46

Earlier quoted context omitted.

Apple probably doesn't concern itself with any developers that don't want to be on their platform. In fact they probably find the notion so inconceivable that they wouldn't see any value in that developer's app. Are there any "unicorn" apps that are Android only and intend to stay that way?

> Are there any "unicorn" apps that are Android only and intend to stay that way? Chrome? Also Gmail, Google Now, and Facebook Messenger on iOS are garbage compared to Android.

Post by mirkoadari » Mon, Sep 14, 2015, 8:58 PM UTC

lewisl9029 wrote: post #117

pjmlp wrote: post #108

Earlier quoted context omitted.

I don't believe it. As someone with lots of native UI experience, that has to occasionally support web projects, the web is just plain clunky and playing catch up with the RAD tooling we enjoy since the mid-90 on native platforms.

I was mostly referring to development paradigms and methodology in my original post, but in terms of tooling, I personally haven't see any tooling on the native side even approach the increased productivity provided by the instantaneous feedback loops that countless hot-reload implementations can offer for the web. https://github.com/gaearon/babel-plugin-react-transform/ http://gaearon.github.io/react-hot-loader/ htt…

Post by mirkoadari » Mon, Sep 14, 2015, 9:02 PM UTC

vickychijwani wrote: post #127

jbigelow76 wrote: post #113

Earlier quoted context omitted.

the key is to know in detail the limitations of this approach There's the rub. If you don't know anything about the native platform then you "don't know what you don't know". The NativeScript demo shows how to pull in a native ObjC function (a string related method I think), but if you start with no background in the native libraries how would you even know when you could be leveraging a native library function inste…

> But if you have the foundation and know the native platform, why jump ship to JS at all? I'm a (native) Android and JS developer. The primary reason I'm excited about React Native is that I don't have to go through the tedious compile-install cycle for every little UI change. React Native will make prototyping/iterating on Android as easy as it is on the web. However my reasoning assumes that there will be almost n…

Post by swhipple » Mon, Sep 14, 2015, 9:02 PM UTC

vjeux wrote: post #38

ahupp wrote: post #4

When porting a React Native app to android 85% of the iOS version was reused: "At the time of shipping Ads Manager for Android, that approach yielded around 85 percent reuse of app code."

One realization I had when designing the API of React Native is that if you want to be able to share any component you need to have the lower level primitives to be shared. So I went on making them: View, Text and Image. I also realized that the same layout engine was required so implemented a shared layout which ended up being flexbox. What amazed me the most during this journey is that most platforms have actually…

Post by squints » Mon, Sep 14, 2015, 9:09 PM UTC

rhodysurf wrote: post #71

jbob2000 wrote: post #9

Yes! I've been working with React-Native on a side project for a few weeks now. WHAT A GODSEND! Before this, I was using Titanium, which is heavy, slow, and difficult to integrate with. React-Native felt like home. On a related note; Why is it up to Facebook to develop something like this? Why aren't Apple and Google making it this easy to develop apps? ObjC is a nightmare, 90% of apps out there don't need that level…

It really isnt hard to write iOS or Android apps. I think you just like Javascript.