News for hackers. Stuff that matters.
Re:React Native: A year in review by wentoodeep on Monday April 18, 2016 @05:38AM (#11518682)
4 months with react-native, pretty unstable environment, lots of headache. Went back to native and happy.
Re:React Native: A year in review by martinkonicek on Monday April 18, 2016 @11:59AM (#11520935)
What was unstable about it and when did you try it? Was it iOS or Android? Curious about the details so we can fix that (I work on React Native).
Re:React Native: A year in review by kyriakos on Monday April 18, 2016 @05:51AM (#11518715)
I guess you just saved me a headache. thanks.

It sounded too good to be true. I'll give it more time to mature.

Re:React Native: A year in review by agnivade on Monday April 18, 2016 @07:27AM (#11519040)
Thanks. That cleared up a lot of doubts for me. I was in 2 minds, trying to start app development with native android or react-native.

I guess reading this thread makes me choose native android.

Re:React Native: A year in review by vbezhenar on Monday April 18, 2016 @10:13AM (#11519992)
IMO if you can afford to spend double time rewriting your app for another platform, just use native and don't think twice. But if you are constrained, react native might be a good choice among current cross-platform solutions.
Re:React Native: A year in review by smrtinsert on Monday April 18, 2016 @02:54PM (#11522260)
There is enough to learn in native mobile before jumping into a wrapper for it. You read the RN docs and you'll see you still need to know the underlying tech pretty well.
Re:React Native: A year in review by whatever_dude on Monday April 18, 2016 @10:31AM (#11520158)
But do you think that's because of its current state, or because the foundation behind it is not solid?

In other words, do you think it'll be in a usable state once it's polished and matured?