News for hackers. Stuff that matters.

A comment on IDE for building React Native apps is now free and open source. Parent comment

Re:IDE for building React Native apps is now free and open s... by pbreit on Thursday May 26, 2016 @12:27PM (#11779243)
Yeah, I'm trying to figure out how React and React Native relate. Are they similar enough that a React app can be modified to "go native" fairly easily? Like let's say you were building Slack which has web and desktop apps that appear identical. Could/would you use React/React-Native and this IDE?
[ Parent | on HN ]
Re:IDE for building React Native apps is now free and open s... by afontaine on Thursday May 26, 2016 @12:32PM (#11779288)
From what I understand, you can't just "go native" from ReactJS because React Native uses specific components for mobile.

While you can't just port over, the way you think about components and your API endpoints can be re-used. It's also nice that they both work with components which allows for less "context switching."

[ Parent | on HN ]
Re:IDE for building React Native apps is now free and open s... by grayrest on Thursday May 26, 2016 @12:40PM (#11779357)
They're using the same core library and conceptually work the same way but there's no no out-of-the-box unified widgets allowing you to share view code between both. So you can share your controllers, model, viewmodel, and higher order data binding components but you'll be rewriting your views.
[ Parent | on HN ]
Re:IDE for building React Native apps is now free and open s... by leoalves on Thursday May 26, 2016 @12:35PM (#11779310)
Most of the logic can be the same. But the UI is different. For the web it uses html elements and for native uses native ios/android elements. Even android and ios are different. That's the biggest advantage if compared to Adobe Cordova. A lot more performant
[ Parent | on HN ]
Re:IDE for building React Native apps is now free and open s... by jjnoakes on Thursday May 26, 2016 @01:40PM (#11779934)
It isn't about whether the underlying ui is different or not. Of course it is.

It is about whether the source application code can be the same. Today it isn't. But why not create a set of source compatible components that render to Android, iOS, and HTML?

I've seen projects approach this and I think it is a good idea. You get the typical lowest-common-denominator problem but if you have a decent way to mix in platform-specific elements where required, what is the downside?

[ Parent | on HN ]