Flutter vs React Native vs. Swift/Kotlin In 5 Minutes

in this video I'm going to be going over building a mobile application in react native versus flutter versus natively with swift or kotlin I'm not going to be giving some passionate like monologue about which framework has the most logical it has the best implementation these really nitty-gritty technical details because quite frankly I don't think that they matter that much because in my opinion you can learn any new language you can learn any new framework eventually with enough practice you may not like it a lot but you can use it to build any type of application so in my opinion that is an implementation detail that's not that important so don't think I'm gonna go talking about how much I love typescript and how I think it's the greatest language in the world I don't care about that we're going to be talking about the other parts of the developer experience outside of the syntax and outside of the framework so the very first thing that I want to talk about in terms of this whole app development ecosystem is performance and by performance I mean how well does the app run on a device technically speaking you're gonna get the best performance with Native developments so Swift for iOS or kotlin for Android can't beat it they are going to provide the smoothest most buttery experience you can imagine but next up after that is is going to flutter and the reason for that is because flutter is actually compiled into machine code and flutter has a dedicated graphic rendering engine called skia that makes sure everything runs super smooth super buttery and the least performant of these three Frameworks is going to be reaction native and the reason for that is because react native doesn't compile into very specific and machine readable code and instead it's more of a wrapper around the native mobile development platforms of Android and iOS react native uses this JavaScript bridge to translate JavaScript into what would be iOS or Android code down below under the hood and because react native acts as a wrapper it'll lead to the worst performance out of the three but you have to ask yourself how important is performance really does it really matter that much because if you look at some of the apps that are built using react native you can see a lot of really big name companies that are using react native to build their apps stuff like Discord coinbase Tesla mercari even parts of the Facebook app use react native to build their apps and I've personally never thought that they were super slow honestly as a small developer team you're probably better off learning flutter or react native to build your mobile applications because they let you build applications for both IOS and Android at the same time whereas if you wanted to write everything natively you have to then build a separate app using kotlin for Android and then a separate app for Swift using iOS and while you may get the best performance is that engineering overhead really worth it and that's really only something that you can answer because everything is different on a case-by-case basis the second thing I want to talk about when considering what platform to use to build your mobile applications is community support because look you're going to run into some bugs you're going to want to use some third-party packages and those two things only comes with really strong community support and I will say at least anecdotally this is not something that I'm like getting numbers for and like pulling all the GitHub repo data but I have found building apps using all three of these platforms is the fact that you will always get the best community support building with Native languages either Swift or kotlin or react native I have found in my experience for flutter if not have as much Community Support as react native or the native languages as well and I think it's just because flutter hasn't really gained as much mainstream popularity as the other two Frameworks don't get me wrong it's definitely growing in popularity a lot but I have found that when I run into some issue and I looked up like stack Overflow or GitHub issues sometimes I don't really find anyone else that's run into it because it's just not as popular or if I'm trying to use a third-party provider oftentimes I find like a lot of these third-party plugins or applications that I want to integrate into my application they always have a native support and react native support but it's often Hit or Miss whether or not flutter is supported but the only exception to that rule of flutter not always having developer support for third-party packages is if you are going to be developing using Google products whenever you're using some type of google-based software product like Firebase for example flutter is almost always supported because flutter is owned by Google so it's treated as a first-class citizen so that's something you want to keep in mind if you have certain libraries or certain functionalities you have in mind that you want to use in your application you might want to do a little bit of research beforehand to see do they have flutter support or not an example that I personally run into when building my most recent app which is an app called to doing which is a to-do list app where instead of checking off the task you actually take a picture to complete that task instead and you can also follow your friends to see what tasks that they're completing as well which by the way if you want to download it I'll include a link to it down below in the description but the issue that I ran into when building to Dewey which is built on top of flutter is I wanted to use this tool called post hoc it is a products Analytics tool which lets me track events do feature Flags a B test post hog does not have an official flutter library that they themselves support and create it they have a community library which is good enough to a certain extent but it's just not officially supported by the post hog team and as a result there are certain features that the community library does not have that the official libraries do so once again do a little bit of pre-research into certain tools that you're looking for to make sure that they support flutter or that there is some type of Community Library support as well alright so that is in my opinion the two most important things that you want to consider when figuring out what technology you want to use to build your mobile applications in the end I really don't think it matters that much because I'm my opinion you can learn any language or any framework relatively quickly as long as you get enough practice under your belt and what's really more important when figuring out what stack that you want to use to build your application is the performance aspect of it as well as the community support as well let me know in the comments down below which framer you like to use when building out your mobile applications once again thanks for watching today's video and I'll see you in the next one

Channel: Your Average Tech Bro

Views: 109,812

Keywords:

Id: 8yImX_v8f-k

Length: 5min 20sec (320 seconds)

Published: Mon Jul 24 2023