131–140 of 193 posts
I'm Jordan and I'm on the React (and React Native) team. There's been some great questions and insight on this thread. React Native offers a ton of benefits around productivity (and ability to use React of course), but since there are many questions about performance, I thought I'd share some of my own personal perspective on the matter. React Native is very different than other approaches because: 1. We're not promi…
Having a brief look over the ReactJS webpage, it seems like it would replace view controllers and perhaps Storyboards?
Or are we talking about writing the entire application in Javascript, declaratively?
Wow. I've been struggling to teach myself objective-c, never getting beyond the simple tutorials. So I'm happy to try this out. I currently have an MVP in ionic framework and would love to port this over to react. Though I should say that Ionic is amazing in its own right. Also, I tend to agree with some of the comments in this thread -- regular Joe user can't really tell the difference. Ionic on an iPhone looks damn…
I'm Jordan and I'm on the React (and React Native) team. There's been some great questions and insight on this thread. React Native offers a ton of benefits around productivity (and ability to use React of course), but since there are many questions about performance, I thought I'd share some of my own personal perspective on the matter. React Native is very different than other approaches because: 1. We're not promi…
Can someone elaborate on how React Native would fit into the app development workflow (iOS)? Having a brief look over the ReactJS webpage, it seems like it would replace view controllers and perhaps Storyboards? Or are we talking about writing the entire application in Javascript, declaratively?
Currently there is no details on React Native, however, I don't believe it would replace the Storyboard as views are still necessary for the React code to interact with the components.
What you would be doing is coding in JS and behind the scenes your app would interact with the views and do the necessarily updates. I'm guessing it'll be a hybrid approach. While you'll most likely still need to know Obj-C or Swift, you can probably get away with a lot of boiler plate code with React.
I think this can be really amazing as is react js now. -- I had to build a simple at first but very complex under the hood. I wrote that app in a weekend with react and was a ton fun and most important worked well since day one. I have been out from the web development since like 1.5 year, but yeah IMO react is the best thing happened to javascript since ... ever. Thanks again guys!
Why?
Earlier quoted context omitted.
There's quite a bit of hyperbole in this talk. Some web apps do in fact come close to native, but to the trained eye of a Facebook software engineer it will feel miles behind. Your average Joe doesn't give a shit, as long as they can use the app. If they did, Facebook's Paper wouldn't have been such a flop.
This is absolutely a great point, and honestly, I used this exact argument early on in the development of React Native to convince folks that cared a ton about craft and were super worried about performance, that it's more important to make sure you have a reliable application that adds value to peoples' lives, before you even earn the right to start thinking about craft. My phrasing was somewhat hyperbolic, but I ba…
I think the poor reviews of Facebook's HTML5 mobile app shook the company to the core and they swung a bit far in the other direction, abandoning the possibility that the web will ever be mobile ready. I think the truth lies somewhere in the middle; no, you can't get native performance from the web, but you can get close. And every year it gets a little closer because phones are getting ridiculously powerful.
All this said, I think Facebook's approach to the platform fragmentation problem is clever and worth checking out, but I'd still bet on HTML5 over the long term.