News for hackers. Stuff that matters.
Re:Introducing Create React Native App by fatbird on Monday March 13, 2017 @06:15PM (#13862991)
At my employer I can easily imagine deploying react native apps for a variety of uses, especially as we do service design : being able to run real experiments with, say, gov't services with real apps or companies looking for mobile assist on new service offerings is a huge win.

At the same time, I'm sceptical that RN has escaped the earlier performance ghettos of Appcelerator, Phonegap et al., which aren't just in games, but also in complicated UIs with a lot of elements. On building a simple sudoku app, I ran into noticeable micro-lag that seems to come from overuse of Views to structure the grid--and noticeably, the performance was better on a non-retina device, causing me to remember the swamp that Java's AWT got caught in with its 'native peering' arrangement, namely that cumulative overhead killed performance in virtually all non-toy cases. React's virtual DOM is an obvious plus in the browser; I'm not so sure where native apps are concerned.

Re:Introducing Create React Native App by intrasight on Tuesday March 14, 2017 @12:04AM (#13864899)
>complicated UIs with a lot of elements

That's a problem for your designer to solve

Re:Introducing Create React Native App by fatbird on Tuesday March 14, 2017 @12:11AM (#13864927)
Not when it's a limitation of one toolkit that another toolkit doesn't have. Then it's just a reason to choose on over the other.
Re:Introducing Create React Native App by intrasight on Tuesday March 14, 2017 @12:29AM (#13865005)
By all means, if one toolkit is more powerful and more productive, then us it. But good design is much about working with constraints.