![]() Yeah, I think the one of the other cool things about it is that you don't have to write your entire app in React Native like you can write parts of it. You're not having to write views for both a lot of the code you're writing once and actually getting iOS and Android, which is pretty amazing. I think to the one of the biggest benefits is the fact that you're getting a lot of iOS and Android together. You're just interfacing with it using JavaScript, and something called the Bridge, which we'll probably talk about later. And so that's why you're able to achieve or to write an application that feels fully native because it is needed. Writing JavaScript code that controls your native components, your native modules. What's worth clarifying, though, is that React Native is not, you're not loading a website within a WebView.Ĭheers can run away from, you're actually So if you have a JavaScript team, then you're now magically able to start, you know, writing mobile apps, both iOS and Android apps. Um, the main benefit, I would say, especially, would depend on the team that you have. So what are some benefits to leveraging React Native, So that's why I never used Chrome on iOS, because it was, you know, you, you still you had your bookmarks and your history, but you had this watered down version of a WebView. So what's what's so Statius point? I know before like, a couple years ago, they didn't something like the web, you didn't even have access to the same JavaScriptĮngine. Because you can't build a browser on iOS. I mean, technically, actually, what's interesting is even on iOS, Chrome is nothing but a WebView. But it's still not native, which React Native is a lot closer to a full native experience. But yes, you you're able to do some extra hookup to like a bridge to the actual native layer that allows you to do a lot with it. It's still lacking a lot of features, or certain things that you just won't be able to do. Yeah, it's basically like an iframe in a native app.Īnd it used to not be like full capable, like it wasn't as capable is like the the native browser on the phone. And you know, hopefully, you're gonna stay inside your app. So the advantages, you're not sending the user out to the browser. ![]() Like Facebook is alive, right? When you ever you tap on something on the feed, you enter into their web view. And it's a native view that's basically holding the web code, So yeah, it's it's I guess, in I guess it's a similar concept in Android, iOS, I know from iOS, it's what it's called, but basically just a way to implement browser inside of a native app. React Native is a way to build mobile applications using JavaScript.Įxplain what a WebView is? I think that that's a good point. All right, well, let's get started then, like what is React Native? Anyone want to give a little bit of a definition of what React Native is? So if anyone says the word web view, we'll all take a drink. So what do we decide today's keyword is web view? Web View. In each episode of the front end happier podcast, we like to choose a keyword that if it's mentioned at all, in the episode, we will all take a drink. I'm a software engineering manager at Netflix. Stacy London, I'm a front end engineer at Atlassian. I'm a software engineer at Evernote or front end engineer. I'm Brian Holt, and I'm not already drunk. I'm a senior software engineer at LinkedIn. Let's also go around the table and give brief introduction of today's panelists. And my favorite happier beverage is probably gin and tonic, or scratch that gin soda to soda is what I do. ![]() Well, as you just said, Ryan, I do a lot of React Native, my name is Naoufal and I work at Netflix as a senior software engineer. ![]() Can you give us a brief introduction of who you are, what you do and what your favorite Happy Hour beverages? No foul is a software engineer from Netflix. And we are joined by Naoufal Kadhom to talk to us about React Native. Welcome to a brand new episode of Front End happy hour.
0 Comments
Leave a Reply. |