11–20 of 47 posts
I feel so totally out of the loop when I don't even understand what it is a hybrid of ?! I really think the landing page could be more clear, perhaps there's more backwards people like me.
Hybrid in this instance means HTML wrapped in an iOS wrapper ala Phonegap.
I can't view this website on my phone. I can only surmise that I am not worthy.
EDIT: It works fine in Chrome with iPhone emulation. What's up on mobile?
I'm really interested in this and am keen to try it out at the weekend! How is this going to play with react-native though? My thoughts are it may be a bit late to the party. I'm happy to see more options available to developers, Ionic looks like a great framework but I won't use it as its built on Angular.
You may want to reuse UI between platforms for more simple apps, and Reapp lets you do that. Not all apps are fit to be hybrid but some are.
Earlier quoted context omitted.
Hybrid in this instance means HTML wrapped in an iOS wrapper ala Phonegap.
So why doesn't the website say anything about the part of wrapping it for Android/iOS? I'm just as confused as unwind.
Everything is hidden behind a thick layer of abstraction and you have to trust that things will be wired up properly on the other side of the fence and continue to be wired up properly as native UI components and APIs evolve. The React team has famously stated that they don't believe in "write once read everywhere" and instead are proponents of a "learn once write everywhere" strategy, which is a clever twist on a controversial topic, but ignores the fact that web developers have been practicing "write once read everywhere" for a very long time now and have gotten pretty good at it (fighting with IE over the years tends to sharpen one's senses).
I believe that the negative feedback on their original hybrid mobile app deeply affected Facebook as an organization and as a result they have swung so far in the opposite direction they are in denial about any possibility that the web may be a viable target for mobile experiences. They've gone so far as to abstract away the entire DOM and ignore coming standards like Web Components. To Facebook, the web browser is nothing more than a render target. It's a clever short term hack to get back to the good ol' days of server side templating (like they used to do with PHP) and get around poor browser reflow/repaint performance. But it's a long term bet against the web as an application runtime and it's sad to think what gains we might be seeing toward that dream if Facebook wasn't so opposed to that goal.
Earlier quoted context omitted.
Hybrid in this instance means HTML wrapped in an iOS wrapper ala Phonegap.
So why doesn't the website say anything about the part of wrapping it for Android/iOS? I'm just as confused as unwind.
I personnaly prefer projects like Titanium(or React native), instead of using a webview and styled webpages(that will never feel native), it just uses javascript to call native phone apis,GUI included, so no HTML or CSS that looks like IOS on Android phones,but only native widgets.
I'm really interested in this and am keen to try it out at the weekend! How is this going to play with react-native though? My thoughts are it may be a bit late to the party. I'm happy to see more options available to developers, Ionic looks like a great framework but I won't use it as its built on Angular.
I was actually at React conf and was initially a little deflated because it was announced with a lot of hype about how "hybrid doesn't cut it". But, after talking with FB folks I came away very happy. I think they will complement and gain from each other immensely.
A few notes on Native vs Hybrid:
1. Facebook is a big company with complex apps. They care very much about speed in their experience and can afford three development teams.
2. You can use Reapp today on all platforms, including web. Native is still unreleased. Outside of Facebook no once can use it, and it hasn't shipped any code for Android.
3. Native will feed back into hybrid well! They told me they wrote a much nicer touch library for it that could be ported back to JS, which I'm excited to do.
4. The dev experience with Reapp is still ahead big time. One codebase, hot reloading of components, and lots more, but you really can go from 0 to app in less time than any other way in my opinion.
In fact I think Reapp is a great way to get into React in general. With the CLI you have all the glue for a great React app in place. You can write your mobile website, and deploy to all platforms. Feel free to ask me any questions!
I far prefer the hybrid approach to the js-to-native approach Facebook and Appcelerator are taking. If you go fully native, you get the complete benefit of the SDK, Native API's, and performance that comes along with it. If you go hybrid native/html5 you get the flexibility, productivity, and reusability of js/html/css with the option to write custom native components as needed. With React Native (AFAIK) and Appceler…
Web Components don't solve the problems React is solving. They are completely different (and sometimes complementary tools).
>I believe that the negative feedback on their original hybrid mobile app deeply affected Facebook as an organization and as a result they have swung so far in the opposite direction they are in denial about any possibility that the web may be a viable target for mobile experiences
I can't speak for Facebook but I think you're missing the point of React Native. It's not a solution to run webapps on native platforms.
React Native is a solution to write native UI code with declarative paradigm. That it runs in JS is an implementation detail. If you look at it from that point of view, hybrid vs native doesn't even come into equation. "Native" is the original requirement here, as far as I understand it. Unless you propose to not write native apps at all.
I far prefer the hybrid approach to the js-to-native approach Facebook and Appcelerator are taking. If you go fully native, you get the complete benefit of the SDK, Native API's, and performance that comes along with it. If you go hybrid native/html5 you get the flexibility, productivity, and reusability of js/html/css with the option to write custom native components as needed. With React Native (AFAIK) and Appceler…
I also would like to see Facebook come back to the middle on this, a company that big could put a lot of resources into making those web to native APIs evolve and bridging the performance / feature gap of JS, an effort they are currently putting into bridging JS to C with mass amounts of developers.
I can't view this website on my phone. I can only surmise that I am not worthy.