Check out our blog post on Cross-Platform Native App Development - Life Before and After Flutter: www.crema.us/blog/cross-platform-native-app-development-life-before-and-after-flutter
Oh man, where to start...? So many core code and implementation probs in flutter and Dart. We gave circled back around like 4 time now. We really want to like it... we really want to use it. Also, we keep hearing that Google is stepping back again and has constrained resources on it now. Is that true? One of the sources works closely with them. So, it makes me think it is true. Sure explains the increased probs. I guess if you are ready and able to code around the problems then sure, it could be really good for some UC’s.
"You'lll never have to learn another framework again. Angular.js will forever be backwards compatible" - Google 9 months later... "This is Anuglar 2 and it's nothing like Angular and we're killing Angular.js" - Also Google
Agreed - there's always a little bit of trepidation around a new offering from them. Excited to see the community continue to support the framework as a whole!
Yup. Now they are considering “setting it free”. Great timing Google- especially with all the new bugs they added. “Clutter” has become the new name fast gaining in popularity. GOOGLE- COME ON AND MAKE UP YOUR MIND. Fix the huge base of problems and the stupid choice of Dart, or spin it off and sell it. It has huge potential, but right now it is more of a cautionary tale than a viable solution for many.
Also Google: We'll make it the hardest to learn, the most cumbersome and least efficient web framework. Also have our boi Evan You beat us with a completely open-source project
I'm working on our first Flutter/Dart app, and while the initial learning curve was steep, it is making a lot of sense, and it is so fast. Hot reload is so useful, I cannot imagine going back to something that requires build/run/compile times... loving the UI and the smooth native flows.
We're all about the fast user feedback while developing! Definitely a lot to learn but the tooling is amazing once you get up and running. Best of luck and thanks for stopping by!
Here are the issues I have with Flutter so far: 1- Material everything. The “Flutter way” of doing things just assumes you’re using Material design and then maybe overriding for your app’s brand. I much prefer RN’s minimalist approach to theming, which adopts each OS’s design language and then allows you to override from there. 2- Dart is a post-apocalyptic wasteland. Have you tried searching for Dart packages for specific functions? There’s one solution, if any, for a given common problem. The Dart ecosystem is so tiny and seems to be moving at a snail’s pace compared to JavaScript. This leads me to my next point. 3 - Flutter is its own world. You can bridge Obj C and Java to Flutter/Dart and I’ve worked on projects where we have done so. But you’re still compiling a unique Flutter stack. For example if you want to have a brownfield app that mixes Flutter and existing native code you’re in for a bumpy ride. In fact I don’t think it’s possible. That worries me because I’m always dependent on the Flutter architecture for my app. With RN I can just go pure native and build on Android and iOS SDKs if I want. I think the main criticisms given to RN are performance for things like animation and library availability/ stability. Performance is already being addressed by Facebook, and the RN team is working on a JS-to-native messaging system that is much faster than the current bridge. As for library availability/stability, I’m constantly seeing updates to existing libraries and discovering new ones. An entire open source community has emerged around RN and we’re learning and developing a rich ecosystem around the library. I think Flutter is a contender. It’s just way too dependent on Google and Dart, and so the overall ecosystem is small and slow, which is worrisome atm. This may change and I’m rooting for Flutter. I think it’s an otherwise beautiful framework. UPDATE: It looks like the Flutter team have addressed the brownfield app issue recently, so I think if you want to incorporate Flutter into an existing app you have better options now.
Excellent points. Material overrides (or replacements) are going to be interesting to track going forward - do you think most people will want to roll their own styles most of the time? Like you, we've been thinking a lot about the difference between having the flexibility to go full native vs being siloed in a framework for 90% of the architecture. React Native's recent push for, "Lean Core" is a really, really interesting development from that perspective. Thanks for the great thoughts! We're excited to see how things look in another six months or so as the communities continue to grow and change.
Crema With how crowded the App and Play Stores are, and with the need to make our products engaging and to stand out, absolutely yes. The Hamilton Broadway musical app that has been one of the Flutter success stories presented by Google is one example of a completey branded experience. That's one of the marketing lines of Flutter (and I'm paraphrasing): No more cookie-cutter apps. The closeness to the metal allows fluid animations that are themselves often used to delivery a delightful UX and to differentiate an app's brand.
React Native said: I will replace the native app in the future, hug me quickly. Flutter said: I will replace native app soon, don't learn RN, just study me. Native: Well... Both of you are right, I'm just waiting the third guy who claims to replace me in a day.
Everyone is talking about FLUTTER vs REACT NATIVE and here I am studying JAVASCRIPT and now confused what to do because everyone is killing each other.
@@chriscorrigan14 PHP is like the predecessor for woke script kiddies nowadays (before they became "woke" to using javascript for everything... stupid idea, by the way)
@@Cremalab I'm currently learning reactjs(web), I hope to build mobile versions of my webapps. The easiest transition is reactNative, but I didn't see a RN demo app that would match the demo app for flutter shown here: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-kpcjBD1XDwU.html
I've been buildiing react native apps for two years and I just started flutter a couple weeks ago and while I think flutter is a better solution, it will not "kill" react native.
coming from native android develpment, i started learning react native and boy has it been one bumpy ride! flutter looks more promising, the plugins are a one up for me. i'm gonna start learning flutter.
Any update on the learning experience? I'm divided about which is one is good. Have dabbled a bit in RN and also felt it was a bit of a bumpy ride, also the documentation doesn't feel that great. Was flutter better in these aspects?
@@chrheca hi, I'm currently using flutter for a project I just embarked on, so far its been great. Once you learn the basics of dart and understand flutter is "all widgets" then you're good to go. Flutter's documentation(you should check it out) is simply awesome unlike RN's. My first RN app didn't have that native feel at all, one could tell it was hybrid easily, so many lines of code was required to get the android ripple effect but with flutter your apps get the native look and feel with little effort be it android or iOS. I suggest you go with flutter.
@@izzy-cs6fu I am a RN developer and I can confirm what you said. Flutter has a far better developer experience. From now on I will only use Flutter for my side projects.
@@JonesDTaylor As mainly a web developer I think the opposite, Flutter is more verbose and has too much nesting and you really need to know well the widgets and his relationship to do a decent project. I think RN brings a better user experience
I had built an app with flutter and it is pretty good, Im a iOS Swift developer and I think as a native developer on iOS and I think it is good to have a skill in hybrid apps and for me I'll choose flutter for that one because the code syntaxes are not that far from swift.
I’ve built a couple of apps with react native and I found it quite easy to jump into considering I had prior experience with react. I was using expo, which seemed to make the whole experience pretty smooth
We have found that to be true as well! There's definitely more of a learning curve with Flutter when you're coming from React - Expo makes a big difference there as well. Thanks for the input!
Flutter and dart feel very natural for me. So glad it eliminated the xml need for android. I cringe if i had to go back to java/xml for android now. Flutter for web is very usable but still not there so I'm interested to see how long that takes
It took me a week to finally start with React Native to start my mobile development career, everything was setup and then I came here, saw the video, read the comments and all of sudden, I believe its better to start learning Flutter now!
started flutter in a month, and i can't stop learn it because it was sooo addicting. hot reload features and soo many ready to use widgets. flutter is fun
Same here, actually. We're excited to see where the road leads but aren't really into the turf wars that often result from these framework comparisons. Use the best tool for the job, eh?
I have been working on an enterprise Flutter app for the past 6 months. I really love Flutter and them taking inspiration from React helped me immensely in creating the UIs. The tough part though was making the BLoCs work. At its most basic, BLoCs work nice and make a lot of sense (using Rx streams to flow data and events). To help me learn it, I even tried implementing it using RxJS with React and it worked. My issue was that RxDart was a pain to work with especially coming from RxJS. It works quite differently in Dart than in JS. Plus being the team lead with junior developers under me, Rx seemed to be such a huge learning curve for them so I had to use a simpler approach to managing state. I still like the BLoC pattern but there needs to be more official information about it. Overall though, Flutter is an excellent choice for cross-platform development. It is simply the closest thing to "native" you are going to get it being implemented as a custom Skia renderer on a native view. The performance is great and the tools are excellent (I am exclusively using VSCode).
Flutter won't kill react-native-web because there are so many developers who prefer writing just JavaScript. Also, React is backed by Facebook so Flutter being backed by Google doesn't mean anything.
As of now I think React Native still rules, But in future, I guess flutter will win because Google will soon release fushia OS and flutter being a Google technology will move to it leaving react native behind.
"Google will soon release fushia OS"... Well Hi! Google will not be releasing Fuchsia for mobile in the short term. It will initially be rolled out to Chromebooks as a replacement for Chrome OS. You can most probably expect your phone to run Fuchsia in no less than 3 years (and another 2 for vendors to release phones running it). On the other hand, Fuchsia WILL support Android apps as first class citizens (just check the repo, ART has been commited a month or two ago, and Magenta interops with it just fine), therefore you can keep coding native apps, Ionic apps, Flutter apps, RN apps, etc, given that all compile to APK's ergo all will run. I invite you to read more about the topic. Cheers!
It will be super interesting to see what happens with the ecosystem as a whole - here's hoping that everyone continues to play nice together! Thanks for the thoughts.
Honestly I've worked extensively with both frameworks, Flutter and React Native. But I am going to have to choose Flutter as the most promising for future mobile development. Also with Google working to bring out Hummingbird for web development that's built on top of Flutter framework and Dart programming language, It will end up being a complete game changer and will overtake everything in the industry! Mark my words, Flutter and Humming bird are the future. At the moment i'm going through a flutter course on Udemy with this guy Maximilian Schwarzmüller, hes honestly the best teacher I've ever had hands down.
Very interesting talk! I really like that you build some apps at least and talk about real experience and feelings, the majority of comparison I see only reads the description of the web site of each framework. Very nice!
We have worked in a bunch of the major UX, and rapid hybrid and full stack tools over the past decade. From some of the most expensive tools that were mandated by corp and government projects like Outsystems, to Wakanda, React, Figma, Flutter and several others. But one thing in common is that they all have their own problems and best use cases. We work pretty darn close with some of the teams at Google, Apple and Facebook, and got some worrisome news of late about Google stepping away from some of its Flutter plans, to the chagrin on some close to the project. They were told by leads that the idea behind the shift discussed is have the market pick up more of the project. But based on similar past Google statements, we know what that means, and it is generally not good. It may not mean major problems for the platform, but I know that at least one of the core team members is weighing his options, and another blasted them a bit last week. But, we like Flutter a lot still, although Dart freaking blows on so many levels. Especially bad given all the bugs. As time is money, we currently do about 50% in Figma. We use it together with on of a few other animation tools. We hope to do more with Flutter, but it has the most ntove bugs of any environment we work with, so we keep stepping away each time we have tried. It always takes lots longer to do solidly in Flutter. We move to our own customized Webviews plus NodeJS in place for speed and stability. React Native is a bit more mature and stable in terms of those types of bugs. Really, it is a use case thing for the most part. However, I wish Google had gone the other way. They really need to squash a lot of aborted Hummingbird and other bugs that are causing lots of frustration. Unlike a 4 month project in Flutter that was supposed to be 4 weeks, we have not had to rewrite around major sections of React Native code like we recently did again in Flutter. One of our team members who pushed the team and client to have us do it in Flutter was almost fired. He wound up writing 10K lines of workaround replacement code to save his job. Given another year, we will revisit Flutter for Hybrid native dev, but right now... no way. It has just been too painful, and that continues to be Google’s fault.
We use React and Flutter for a lot of projects- over 2 dozen with React Native this year and 8 with Flutter. We still use Figma together Principle whenever possible- like any advanced UI/UX and mockup work and all of our complex protos where we need full animation, flat or other full concept interactivity. Figma plus Principle is 100% solid and stable every time and by far the best solution we have found for UX mockup and related design work. Saves us a lot of time and makes everyone really happy. That combo saves us days to weeks compared to trying to use a full RAD stack environment that uses reactive animation UX and responsive designs. It is sad that Google is stepping back from lead work on Flutter branches. Seeing them losing and moving project devs and relared engineers does not bode well.
Dart is so ugly to look at. Jsx is no the best, but is way more simple to understand what is going on.Wrap ten thousand function inside another function just to get some padding is ridiculous.
It will kill electron as well, as soon it comes to desktop, for one week I've had enough. Dart is pretty easy to learn especially if you used typescript before.
6 months ago, some of my colleagues were excited about flutter and now i dont hear anything about flutter from them. Run from the problem itself is smart
I’m currently studying flutter at my University, and so far it’s been an awesome experience. The professor pushes us to hack up professional and elegant apps in the span of a couple days. With flutter mobile development time is cut in half.
I think an important detail that this video missed is the way that flutter goes "straight to the metal" in a way that react native doesn't. While react native is designed to compile down to native framework code eg swift, flutter is more like a video game, controlling the GPU directly. This is arguably the killer feature here, because it means that flutter can be ported to create UIs on literally any device. Fridge screens, car dashboards, ATMs, whatever. This is why the framework is built on top of dart and not some other more popular, more established language: dart is optimised for GPU control and performance. Hence the beautiful 60fps rendering. PS I don't know a lot about this so if anything isn't right then please correct me :)
Hey Andrew, thanks for the great feedback! We know there are probably some things we didn't mention in this first impressions video -- we don't know much about Flutter ourselves. Scotty did mention something similar to your "video game" reference about Flutter in our latest video talking about React Native, though! We're definitely excited to see what the future of Flutter looks like, and a few of us have started dabbling in it here and there. We hope to make a video in the future about what we've learned and revisit the topic. Thanks again for your comment, we'll definitely reference back to it in the process of making our future videos (:
I come from native iOS development and React Native was so overwhelming, I got frustrated by the errors when I tried to run a simple app. Then I looked at Flutter, and oh boy, it feels so much better for me. I think RN is preferred by those who come from web dev background, while native mobile developers might prefer to use Flutter instead. I've only worked on both for a week, and I chose to work with Flutter finally. Dart language is just like Java or any other OO languages, so it's easier to learn for me.
I've had a little time to think about this video and I think there are two main issues with it 1) Some of the statements about React Native are just plain wrong. You can use one small team to build both native and mobile apps with React and React native and you can share code across web and mobile. The main limitations to the sharing are limitations that you would experience in any multi-targeted approach. I literally laughed out loud when the guy with the plugs said "that'd be crazy if you could do everything in one code base". I'm really surprised you all didn't edit that comment out as you are an agency and it shows a lot of naivety about the current state of affairs. 2) You are talking about "Will Flutter kill React Native" and I get it, it's a click bait kind of title in a marketing video. But I feel that not including any context about what you are currently recommending to your clients leaves out the most useful and interesting aspects of the conversation for most folks. You all did touch on what would be needed to make Flutter dominate and I agree with your wish list there but you left out what you would use now to address the problem space that your wish list is aiming at in the future. And really if your answer isn't React Native for current recommendations then me and most others would be interested to hear what your current recommendation is.
Hey Ryan, thanks for both of your comments here - valid feedback and really good talking points. Couple thoughts to keep the conversation going: 1) Sharing code between React and React Native has been difficult unless you use some of the web extension frameworks for RN. We write almost all of our projects in React, but choose to keep product logic specific to the platform, at least so far. You're definitely right that any multi-targeted approach has risks! I think that's why it feels, "crazy" that we could actually accomplish that with Flutter/Dart. Pretty interesting to consider and will differ from most of the product development we've done in the past. 2) Sorry for not being more clear about our current stack: React Native has been our go-to for client apps for quite a while now. We don't see that changing unless another framework like Flutter can be tested, battle-hardened, and shows health and adoption within the dev community. Your point about addressing what we could use NOW to address the problem space is really good - good note for us in future content. We're actually making some React Native videos in the near future and would love to hear your thoughts if you have something you'd specifically like to see covered. One final thought: This is primarily a first-look-at-a-new-framework video so we didn't want to speak too objectively about the future of either React Native or Flutter. We love to learn and try new things so we're moving fast to form initial opinions, but you know just like we do that the landscape can change very quickly, so we're watching to see what happens! Again, really appreciate your thoughts and feedback. Thanks!
Super cool from our point of view as well! Do you use React Primitives or keep the front-end separate once you get down to the platform level? We use React Native for all of our mobile development at present and are always looking for better ways to manage our workflows.
@@EgidioCaprino We are getting the same kind of value and it's not only a huge value add for React Native but just for React in general. We also do a lot of node so we area able to give our clients so much value with a small team.
Great talk guys, I want to add something that I think it’s real important in this conversation and that’s Flutter is the SDK for building Fuchsia (the replacement of android in my opinion) apps, so every time you build a Flutter app you are actually building something that will work in that particular platform and that’s a huge deal!
There is a big difference between a product being backed by Google and an open source developer library / toolkit being backed by Google. The latter tend to have much more staying power.
so it is a problem now? isn't divide and conquer make thing more focused and managed? sometimes one party control everything is so risky you know. The finally fact that, google can shutdown flutter tomorrow who knows, so people really afraid using flutter in production
@@alooooooola true, but I like how everything is ready out of the box in flutter - saves so much time in development especially if you're just one person. Also I really don't think you need to worry about Google shutting down Flutter I think they have bigger issues to deal with at the moment 🤣
@@Zentamusic google biggest issue is their strange behaviour in close and open a project xD. I wont supprise if suddenly flutter page shut down tomorow
Flutter is extraordinary. I just want to keep learning more about it and using it. I can't wait to be able to use it to embed plugins into existing Android/iOS apps for such things as paid content in mobile apps.
I've been doing React Native for a couple of years now. I'd love to hear your take on Flutter if you get a chance. So far it seems extremely stable and fast. I really like what I see so far!
Flutter still doesn't have RN's codepush feature, which allows you to remotely update mobile app, just by updating js bundle, without the need to update from playstore. This is the single biggest reason why we are still using RN. Waiting for flutter to catch up.
Flutter will not kill react native, the JavaScript ecosystem will, adding/upgrading routing on react native should be a 5 min stuff not a 3 hour research
Me, honestly, don't know if Flutter can kill React Native for this time and in the future, but based on my personal opinion, Flutter can be a hard competitor to React Native. Currently, I am learning Flutter and at the same time Dart as well. Just like Rails, you need to know at least Ruby's OOP, enum, inheritance and so on. I have developed a few web app using React and React Native, but to be honest, JavaScript is not my favorite anymore since there is a lot of framework and library of JavaScript and sometimes, I feel like I lost when thinking of JavaScript. Back to the track, Flutter is still young than React Native. Every programmer and web developer knows more React Native than Flutter. But who knows, if in this year, Flutter can overcome than React Native
Really good call to point out the difference between "kill" and being a "hard competitor" between languages. We'll be watching to see how both of them continue to evolve!
I only started using flutter and it already looks so amazing and lightning fast comparing to java android. I definitely will continue this journey, but the community still looks empty. Dart is not a really big problem for Android developers, it's something between java and kotlin. But I still don't get this language decision. If google only did Flutter on kotlin, they would conquer all android developer hearts in a few weeks.
That's right. Do you think the reason is that Google wants to own most components of Flutter? I thought it's just an aggressive attempt to popularise dart in cost of community preferences. But who knows =) In all cases it is not important anymore. Decision is made =)
@@silvershadow13 IMO, thats whats google doing. They dont want to share the 🥧. IMO That is why they build flutter. Remember when did kotlin become popular?
from pakistan: i have been a native developer of ios and andorid for years! then i found React Native is a nice experience! but i don't like the using flutter as its farely new! i coded an application in it! and i love the simplicity! but its not yet mature that much! and support is pretty low!
Agreed! We like to keep an eye on new tech but not switch before really learning about the tool and the support behind it. Thanks for sharing your experience!
The topic you guys are talking is great and good But after 4 minutes of watching video i get bored I think you should change the way you make this kind of shows But i thank you for good topic
Flutter has really caught my eye because I was told there is much more of an ease of use and the widgets are excellent! Question? Has the flutter team fixed the stutter issues? I think I won't touch this peace of tech unless those issues have been resolved.
The stutter issues is the only reason I’m still on the fence about flutter. The fact it is still an issue in 2023 means to me they are not able to fix it.
@@iykazorji8171 Wow, that is disappointing. I hadn't touched the technology yet. Been working on Django with Python and some JavaScript. I always wanted to try out flutter. I hear your able to deploy your product quickly. But if this issue still exists then I won't even consider it, thanks for sharing.
I'm just about to finish a simple app at work in Flutter. My experience so far is good though I wish they have something similar to Boorstrap CSS styles esp. for different viewports. Running Media Queries everywhere is not a nice option unless I've not understood the Material UI concept. Even for Orientation changes from Portrait to Landscape, as a developer you have to take care of changing smaller to bigger fonts, icon sizes etc. Still I like the speed of development due to rapidly growing plugins and overall developer community. As far as I can see, Flutter will be a BIG player in cross platform mobile apps market. Also love the VS Code plugins for Dart and Flutter, makes life so much easier to code.
We really love the IDE support so far as well, it makes jumping in a lot faster. Lots to learn and try with the new toys and tools! Excited to see what the community can build.
Hi, please suggest whether I should choose to Learn react native or flutter or native android development through java . I am complete beginner(as I only know C programming) and which of those 3 has greater scope for freelancing ? .
I agree with you guys that react is more close to web based development than flutter enabling web developers like us easier to learn and adopt. Flutter is more like something new.
Flutter all the way. Google played the wait and watch game, really well. After seeing many frameworks come and go, syntaxes and semantics come and go, learnt a lot from others successes and failures, they had a very good and strong starting point to head in the right direction compared to others, AND SO yeah flutter is here to stay and will eventually edge out all the other mobile development technologies and frameworks (for other platforms like the desktop and web, I'm not that positive as the canvas isn't ready yet for the web for text and other stuff that can replicate the SKIA magic). You guys have missed out on highlighting the prowess of the tooling which is crucial, like, the fast debugging, widget inspector that outlines and shows the widgets in a page, the hot pushes and quick boot up time, the debugging capabilities with state being retained right into a nested page, the performance snapshots right into the application, etc., I had my own skepticism around the early adoption and the risks, after using it for a few months on complex projects and ease with which it works, and addresses the complex requirements is awesome, commendable and liberating. Flutter is developers' frenzy!
Definitely smart by Google to wait and polish this library before releasing it. Good point on the tooling being such a huge draw - we're looking forward to more practice there as well!
Absolutely! I agree that tooling, CI and CD are really really awesome. I look forward to when I can write, test, deploy and publish to the app stores automagically.
Hi, did you publish your flutter app???we are planning to switch from ionic to flutter but we are little bit afraid b/c flutter is fairly new...how was your overall development experience and will it be a safe bet to migrate our app to flutter right now???
@@zafarali3817 Flutter new or not, can't be worst than Ionic lol. Seriously, every time I see an Ionic app I try staying away from it. Switch to Flutter, even at 1.0 is much more stable and enjoyable for users than Ionic.
Yeah,you are right we've been using Ionic for 2 years and we have created alot of custom plugins to meet our requirements.we worked very hard to make our app stable and it is now stable ....but our team has decided to switch now....we are currently doing R&D to switch either to react-native or to flutter...so it isn't Ionic vs flutter rather I was asking how stable the Flutter is,compare to react-native...I forgot to mention it though...
"its just flutter update" ... easy said, but you have to keep in mind, the credit goes also to Dart, with a stable release dating to 2013 which now is 7 years. There have been a lot of changes until first release an solved a lot of design issues until now. So... when Java conquered the world it was only 4 years old but enterprise and taken seriously like 6 years old. Understanding, that there have been a lot of licensing issues with java and a demand on solving problems with the Javascript engine, I recommend to take Dart more serious than ever. Its by far the best thought through language that I know, from an OOP standpoint. People comming from a VB or python kind of language, may need some time to get familiar with it, but for a Java Developer not having to deal with swift, kotlin, Objective C, in particular with framework/styleguide definitions, flutter essentially being a Dart UseCase is a good deed. Workarounds like React Native, Cordoba, PhoneGap aim on helping Javascript Developers getting hands on some native development, but in my opinion is rather an inferior choice due to the fact, it never became a mature language. The initial idea about Javascript was engenious! thats why it became popular in the first place, Dart outgrew Javascript in a short time and was already by far superior in 2013.
The only huge difference between RN and Flutter is that Flutter is faster, however that will be over pretty soon, and Flutter will have nothing to offer over React Native.
@@Cremalab Its very hard to predict how communities will evolve and go from now, but JavaScript is definately bigger than Dart, and you can virtually find any type of lib for JS.
Sorry, but receive feedback about Mobile Development from web devs is not trustworthy. I worked react native about 8 months with a React JS team and I practically spent my time arguing with them (memory leaks everywhere) and at the end the project was a mess and the company lost the client. I think Flutter is the future but if not ruled by web devs.
Hardcore native android developer. And for likes of me react was a little unfriendly maybe because of my background as a developer. Flutter was definitely my choice because they provided nicely written docs!
I'm electrical technician I don't have any background about any development stuff, but to be honest, I fucked up with my supervisor he so much crazy so that's why I want to learn how to create mobile apps and web apps. One of my friends he software engineer and he is really really good, he suggested me to start from react-native so I did and I'm going deep in navigation and I'm trying to master it, I found it little easy if you understand it, but the real problem is when I hear too many people told me to leave it and learn bla bla I feel like I'm really confused about what I learned and asking myself should I keep moving with RN or I have to learn something else like Flutter. I'm sorry about my bad English
Sorry to hear you got in over your head! If it helps: we all feel that way from time to time doing development work. It's a constant game of what to learn, what to master, and what to ignore. Keep at it and thanks for sharing!
What I would suggest is learn computer science fundamentals, you don't have to struggle to decide mobile app or web app or cross-platform. Trust me most of the software engineers don't know the core basic skills, But Once to practice and master Fundamentals and problem-solving, You don't need to ask/listen, anyone, you will make your own decision.
I have been learning NativeScript, Vue Native (React Native for Vue), and Flutter. Although I have a strong web development background which makes learning NativeScript and Vue Native easier to adjust than Flutter, there is not a strong enough community behind NativeScript and Vue Native and it's not a smooth transition learning those frameworks over Flutter. What I mean is, with Vue Native, for instance, if you follow their documentation to set up a project, you are met with a lot of errors that you will have to debug because that issue has not been resolved on their Github issues. With NativeScript, their Slack channel is very active and their documentation is decent but beyond that everything is outdated. NativeScript also has cloud build support which is great for building iOS apps on Windows and Linux machines but creating a project on SideKick are met with errors. Flutter is super easy to set up and get going and seems to be on the right track at "killing" it's competitors.
A couple of our team members have tried those frameworks as well and we definitely agree that Flutter seems like a solid long-term option. Thanks for sharing your feedback!
Doubt it will kill React Native, but if React Native doesn't really develop faster and grow it might. Flutter is so much better on the UI side though. No doubt about that.
can someone tell why is xamarin not liked by the hybird community ?? i think it's great and the most mature of all of them also UI building is very easy compared to the other hybird frameworks
Xamarin definitely has the edge on most frameworks due to its age, but it doesn't seem to have the traction that React Native, Ionic, Flutter, or other frameworks do, at least not right now. A big blocker for us is having to write everything in .NET since we're mainly a React & JS shop. Any thoughts on other reasons Xamarin doesn't really share the limelight?
Have you ever tried xamarin on a Mac? I used to try working on a xamarin project. One developer was using windows while I’m on a mac. It was mostly a pain for me because the project wont even build without errors everywhere whenever I pulled new commits from my friend. The errors come from the IDE, because things should’ve worked okay. He ended up working on it alone. Then after flutter came, my boss told me to recreate it using flutter. So much easier.
The learning curve is definitely there when switching stacks or learning a new framework. That's one interesting idea behind a single toolkit to approach all platforms, but time will tell whether that works in everyone's favor! Thanks for sharing.
JavaScript hands down. It has a much more broad application. But the jump to dart for flutter isn’t too far. But the internet runs in JavaScript so you probably start there.
I am wondering after 20 months of this video, what is happening to flutter. I personally LOVE flutter, but it seems not that popular as expected and RN is still strong. At least in job market.
Definitely something that will affect developers, tooling, and overall adoption! We're taking it slow to see how things shape up as well - hope you get to jump in and play around soon!
@@Cremalab i said that cause flutter is not ready for industry level development. currently we are on rn. but as a developer i am so siked about flutter.
java script was ha hard to understand for beginners' language harder than c or c++. then all other languages I pretty easy to get it. so the principal factor I guess is workflow performance different metrics. have to have good productivity, have to be able to have good compatibility with any technology or development and creativity to extend new ideas of apps and able to perform it pretty fast nad low issues. for example, I want to put 3d web unity level o special effect in flutter is it possible? if not why not back to c++ an create a good framework. maybe unty additional app will eat them all.
I would like to use flutter I am having a lot of issues with installing. I have watched many videos. Still no success I would still like to use it. Android studio is the problem I believe, I start a new application and it won’t allow me to hit the next but I can name the project then go on to the next page I can’t get any further than that. Can you point me in the right direction please. Thank you Chris C.
Hi Chris, The android studio installation documentation is actually pretty good if you make sure to follow all the steps (developer.android.com/studio/install). Apart from that, I would recommend a course from the London App Brewery (they worked with Google to develop the course) www.appbrewery.co/p/flutter-development-bootcamp-with-dart. - Scotty
I love the discussion, from my experience it takes time for a library/FW to mature in a way that it can hold a product lifecycle. Angular was very promising at the beginning and a lot of companies used it, if you recall, upgrading Angular versions at the beginning was A nightmare. I personally think that peaking the "Right" technology is really based on your need and product scale and lifetime. thinking forward, what is going to happen if the technology you are using is going to fade out and in order to support your product you need to change a lot. there are also ways to design and architect your code in a way that moving from technology to technology will be easier although that will involve more code and skilled developers. long story short, this is a moving target and it is hard to decide if it is there yet or not. so think about your product / solution lifetime and scale and based on that make your decision... :)
We're on the same page - these things take time to settle and mature! Definitely appreciate you calling out the importance of building something that fits the client needs over and above cool toys.
Really nice! However, I think you didn't tackle the biggest selling points for RN, for instance community support. I would have preferred more of a round up of the things that React Native does badly and how Flutter solves those problems. Good job tho, keep up the good work!
Thank you, Francesco! We actually just wrapped up a video about React Native a few days ago, so keep an eye out for that one. We're still pretty new to Flutter, Andrew and Scotty are exploring it more and more so we'll be able to make a more in-depth comparison video in the future!
Rolling your own is still so important though! Tbh I don’t need presumptive DX being forced fed material design modules from the get go. Ripple effect everywhere?
We've been thinking on this a lot as well - it will be interesting to see what the Flutter community does when a clean slate is needed. Thanks for the input!
