I think about this article a lot...
Вставка
- Опубліковано 3 жов 2024
- It's no secret that I'm a React Native fan. It's truly a shame that this AirBNB article will be cited as reason to not use it for the rest of time. Mobile devs deserve better.
ALL MY VIDEOS ARE POSTED EARLY ON PATREON / t3dotgg
Everything else (Twitch, Twitter, Discord & my blog): t3.gg/links
S/O Ph4seOne for the awesome edit 🙏
Expo doesn’t get nearly as much recognition as it deserves
Expo has spent so much of its time catching up to the rest of the mobile dev ecosystem. There is nothing expo or react native helps you archive thats makes its better to use expo or react native. React native and react look nothing alike from an advanced point of view. The technology needs a vision for developers to back it
The 25MB Hello World app memes don’t help with that
It got A LOT better over time
Yh
Expo is great 😃😃
@@owenwexler7214 man you gotta be a really shit mobile dev if you take that meme seriously
Expo got a lot of hate, even back in 2018 when I started doing React. Apparently it's always those "native" guys. I love expo, always been an expo fan, always love how they think of their plugins, and how they listen about their users. I'm surprised they don't cost $299 annually to use.
Thanks theo, I really dislike expo haters. This shit is too free.
Why was all the hate?
@@runonce pick one: expo is not as good as react native, you can't do as many things with expo, react native is bad, js is bad
This is a very good rant. Constructive, with actual arguments, critical but to the point. Must be nice to have a voice to put this out and reach the amount of people you do. Thank for sharing!
Amen 🙏 🤓
I Agree++
I used to write apps with Cordova, they had the same idea that Expo+RN does but without assuming a framework and letting the render happen in a webview. Worked fine, and even back like 7-9 years ago it was fast enough that most devices had a native-like experience if you knew how to build a good SPA. React Native as far as I've been playing with is the next level where you are delivering a native experience where your domain logic can remain the good old JS level that pretty much everyone understands.
I've spent the last year ish in React Native/Expo. It is crazy how much it does with what seems like such minimal effort because it usually just works everywhere. Expo is a game changer though, from handling submitting to platforms with EAS to their new Expo Router. Expo Router is still super early but I think it's a really good shift.
The new architecture is awesome.
Turbo Modules, Fabric, and the Codegen.
I hope there is more excitement on react native.
Devs: Don't like a certain piece of software
Theo: Misunderstoooood!
JavaScript or React is not the reason I don't like RN.
I don't like it comparing it with Flutter because of the performance and UI kit isn't as good in RN.
Although I like Expo but the size of the app increases significantly
he is right tho, 80% of those devs liked it and 70% would try RN in other projects
its people who wants to see problem
RN styling sucks so much. Css in js crap. Can’t do it
@@danvilela cant you use modules like React?
@@yt-sh I'm not sure if you can but RN in my opinion should at least provide the basic components like button, drop-down etc etc in material and Cupertino. To have a something as a button wrapping it in TouchableOpacity makes the UX very bad. There are no native components we have to build all of it on our own.
Unlike Flutter that provides all components. Idk about ios but with Android at least we have all the basic components
Having spent the last 2 weeks working on a side project using RN, I can vouch that using it was a really nice and streamlined experience. A pet peeve of mine is the declarative nature of design in native android development. Being able to use tailwind css to design your app is SUCH a underrated benefit. Apart from that the ability to take the majority of stuff you know from React and being able to port it to RN is another plus as well.
The only things I don't like are: poor documentation. Maybe I'm going into it expecting too much after I've used the new React docs, but either way the RN docs, especially the ones on expo router are not good. While the content and details might be there, they are not structed in a good way at all. You continuously have to jump back and forth between 3 to 4 websites to do basic stuff like add a new screen with a tab icon at the bottom.
You should be happy tho, I'm to stupid to even understand the toolchain and actually get a project going. So, even if the docs are bad, at least you're smart enough to work around it!
wait tailwind for RN? didn't know that worked
I am with you the docs are the worst part of using RN
Damn didnt knew we could use tailwind in react native
I was put off from using RN by that Airbnb post, but thanks to a tight deadline, I had to still go with RN as it was using some concepts and tools I’m already familiar with from the web. The DX with bare RN setup was a bit of a headache, but I was able to get through it all, nowadays I’d go with Expo by default as it’s matured a lot! With Flutter, you don’t really know when big G is going to rug pull it, they kind of ditched everything to build a whole new ecosystem for Fuchsia and who knows how that will go? Seems like an unsafe bet.
Fuchsia uses Flutter .. 🤦🏻♂️ And they are investing A LOT in flutter. All their apps are being made with it
you're clearly ignorant to what flutter is doing so I'd recommend you to either look into it or not share wrong information
@@danvilela Yes, Flutter is a first-class citizen on Fuchsia and will benefit from it! But, It doesn't matter unless their new OS ever becomes a reality and gets mass adoption, and given Google's history on how they manage projects, they'll probably not shy away from throwing it all if it doesn't work out. All this seems like an unnecessary reinventing of the wheel by shifting in a new direction with Fuchsia.
@@zeroww7i don't think so. They would sink bmw, at least 5 banks, government apps and thousand other big companies with it. The most probable option when google stop being interested in flutter would be to create flutter foundation and split the bill with other companies.
I would only consider RN or Capacitor for any mobile projects these days.
Expo 49 is already in beta and should come out this week, maybe next week 😊
it is out now
BlueSky is built with React Native, and the pace they're pushing out updates and moving forward is pretty amazing!
I haven’t seen any updates…. It’s same white invite wall 😢
@@hanes2 my friend has the same issue and I have no idea why. I’m sorry that’s happening
Expo has gotten really amazing in the past couple years. I came back to it a couple months ago and was blown away by the progress they've made. Not using it seems crazy now!
I am not a fan of flutter, but holy crap was working with RN a pita a lot of times. From unsolvable performance issues, to weird page transitions to build tooling that breaks on every minor update. It all felt flaky as hell. I haven't worked with RN for about a year now, but I definitely wouldnt' want to. RN probably once was a really great and innovative thing (and maybe it has moved and is that again), but flutter to me seemed a lot more stable. It's a bit like moving from electron to tauri. (though I love Tauri and just find flutter ok...)
Theo is glossing over the many rough edges. I'm not sure if I would or wouldn't use it again. It has benefits but it also, as you point out, constantly feels janky and half-baked.
Expo is straight up wizardry. I can not recommend it enough!
... says the ReactNative dev ...
just show them the top 500 non gaming apps on the app stores and you'll see that most of them is built using react native.
I got the point. I got new guy in my office said to don't use lodash since there is some article said it not good because of build size. then I read more about lodash found out it already has a way to optimize it.
Damn, I remember reading this article 6 years ago
This is an awesome video! Thank you for sorting these opinions out... they are hard to deal with sometimes when you're called out for using React...
Never had a problem with react native and I’ve built iOS apps in objective C and react native.
The resulting binary of react native is huge, that’s the reason I skipped react native. Flutter on the other hand comes close to swift/kotlin built app.
I was an Android and iOS dev using Java/ObjC, for me it’s more interesting to choose Flutter. React Native just doesn’t feel out of the box.
I may eventually get to native IOS or Android development but Expo has been such a supercharger. The introduction of config plugins makes Expo a great choice 99% of the time.
Since i dont like react i will talk from the experience of a vue dev. When i have to go mobile (or desktop app), i choose PWA. Is not as limiting as people think. We now have Push on IOS, web apis to tap into hardware are really powerful and people most of the time dont grasp that javascript can actually do alot of stuff with external hardware from a web context without relying on calling native functions written in java/swift. The only thing that is a grunge for me is that is harder to develope an app that works on a desktop browser and also make it feel native when is viewed from a mobile screen (capacitor or framework7 help alot here). So yeah. I am pleased and my clients are pleased too
A lot of apps can be made in webview with no issues. Text, forms, images, simple animations, no one will see a difference between web and native framework. Even if you need more native apis you can use adapters to expose it to web.
Engineers always push hard to change directions and invest on new apps because they're too bored. this is crazy lol.
Tobi's luke tweet summarises it up
I'm a full time RN developer and with our team we ejected the app from expo 4-5 months ago and it became much faster and flexible to use. Though there were a few expo plugins that could have made some tasks a bit easier but it's definitely not worth moving to expo
same
Thank you for your service!!!! I hated this article when it was written!!!!
I'm glad Airbnb wrote this article, because then I learned Swift and it's my favorite lang
I legitimately don't understand how anyone uses React Native. I've tried using it three times now, every time giving it a solid week to convince me. And I just don't understand. It simply doesn't seem to work. Everything is hilariously buggy. Nothing lays out the same on web and android. About 50% of the react-native packages people publish simply don't work or have so little information that it's not even possible to tell whether they work or what exactly they were even supposed to do in the first place. Another 25% don't work cross-platform (what's the point of publishing a package for a cross-platform framework that doesn't work cross-platform???). The expo packages seem to be pretty high quality, though their API design could sometimes be better. But they're definitely fine. Not without their rough edges though, but at least they put in effort.
The documentation for a lot of even core components is hilariously insufficient. Even including very core components you have to use all the time. Not that the core components even work all the time. E.g. as far as I can tell, FlatList just simply doesn't lay out its items correctly on Android.
Any error might as well be impossible to debug with how terrible (and frequently simply incorrect) the error messages are. You get bangers like: "Crash without any error or log whatsoever" and "A text node cannot be a child of a " (Ok, where? What text? Hello?? Do you expect me to look through my whole codebase to find where there's a random space somewhere?). And because everyone just accepts that there is no actual systematic way to debug these errors, suggestions online usually range from "just build your own that acutally works" to "try randomly permuting your source code until it works". Wonderful.
From everything I can tell, React Native is just simply not fit for any purpose (and obviously never will be).
Great video. This sunsetting react native article, is like the one an amazon employee wrote recently about serverless not being that great. His article speaks about the monolithic approach being better. Clearly for the amazon prime video encoding. But sadly the article just gives off vibes of amazon cussing its own products.
I still hear this article cited even today. Says a lot about today's developers :)
After working for years in React Native. I would be cautious to recommend it, it has some insane benefits like OTA updates, despite that you can make pretty much anything in RN and make it look good, RN unfortunately because of how it works makes it really easy to built janky uis. And your experience as React dev working with animations will hardly translate to RN, so that’s going to be another challenge.
Every update cycle is hell, working with monorepos is still ass, native modules debugging is bad. In order to install package for it to work you better use expo as your package manager layer because it knows better than pnpm what’s best.
There are a lot of challenges with RN, a lot of pains and things that will make your hair gray. But if you need delivery speed in hours not days RN is a good choice
I have shipped 7 production apps and the only pain with react-native is upgrading and it has gotten a lot better.
@@walterlolfinally some good review, for each good review i see 1000 bad ones, i dont know what it is that people hate about it( im mot s RN dev tho)
@@walterlol forget React Native bro and use Flutter instead. React Native is very2 sucks mobile framework as well as React Js a very2 bad for web development.
Expo's development-client lets you avoid ejecting and is pretty cool but since it's kind of new, you don't see many tutorials. Spent the past few months using it and I got a lot accomplished.
Thank you for supporting react native btw
🙌🏽 glad you mentioned this and React’s changes mainly being for RN. I think that’s been my biggest gripe in FE development. A lot of these “wars” don’t even know the ethos of the codebase. React’s changes for nearly now a decade was to make react a platform agnostic language where it doesn’t matter where the view is, if you know react, you could build on it. Glad you also shredded the airbnb article that no one who shares it clearly reads and elated you highlighted the lords work the expo team has been doing to move RN to be a best-in-class tool.
also airbnb is in a big mess, not going to listen to them at this point.
To me it's infuriating that RN still doesn't have display:grid and working autocentering. There, I said it.
isn't expo team already get funding? they starting to make expo web which I think if it success then it will be game changer. we will move to react-native fully to build everything
The only source of popularity of React Native is the popularity of React as a web framework and Javascript as a language. The main downside of Flutter on the other hand is the new language that you need to learn - Dart. Other than that Flutter is much better than RN in almost all regards. I tried them both. Flutter is just better on so many levels. But I understand that there is so many React/JS guys and they naturally gravitate towards RN.
I have very conflicting feelings for React Native. I want to use it more, but at the same time I don't. I think it has more to do with the hellscape of a codebase that I've inherited rather than React Native itself though.
Boom you hit this on the nail! Awesome job!!
It's like you absolutely never wrote anything beyond 3 screen app on mobile. React Native is nightmare to maintain. I had 3 projects written in n where the cost of upgrading app to new version of RN costed more than rewriting the whole app to flutter.
Aditionaly Apps in flutter are safer, have order of magnitude less bugs, you have ability to create UI on a pixel level, platform integration is done properly etc.
There is no case for react native. Even if your team is 100% js devs it's easier for them to learn dart and flutter than learn react native alone.
I remember that article. I bet they regret it now.
Thanks for this. I'm starting building an app in React Native.. it's a bit of a headache, there's far less training for Native and what is there is not that great. Then when you find one, the dependencies aren't up to date and raise a ton of errors.. I shall push on!
I don't do much frontend but the way you've described it has me thinking React Native makes JS to native APIs like Python is to C libs with Numpy & friends
I hate, this is not a heavy term i really _h_a_t_e_ the term "sunsetting". Just stop sugar coating things, just be an adult and call things for what they are - at least use the established "discontinuing"
I remember starting to work with React Native with Android Studio and stuff many years ago and it was soo cumbersome that I quitted. Then I found about Astro and it looked like it improved the DX a lot but I never tried to get into React Native again but I would def go with it again if I need to.
Interesting to see. Perfect timing as I'm looking to build a new mobile app.
I'm a laravel and javascript dev for almost seven years and this is my first time using react and react native and it's really good especially with expo cli
This video totally changed my view of React Native. Thanks!
May I know why "mobile development" is less adopted every year? I'm a full stack web dev and I'm trying to expand my knowledge into mobile app development, I really interested in React Native but seem like there might not be as much career opportunity as I might expected
Isn't that the opposite of what is happening though? More and more of our consumption of the internet is going to mobile apps.
@@wezter96 That's what I thought at first too, but the Stack Overflow survey for 2023 showed that mobile dev accounts for only ~3.5% of all occupations, and there are very few vacant mobile dev roles in my local area too (the reason might be that all new junior developers tend to learn Flutter). Theo's wording seems to align with what I suspected, but I'm also not sure why
@@wezter96 Really? Now that iOS supports push notifications on PWA? Not really a need to have a mobile app in my opinion
@@timothycurtis5694 Stackoverflow is not a good representation of the population at large. There are those demographics that tend to use it a lot while others rarely ever use it.
Looking for actual job ads as you have with your local area makes a lot more sense.
afaict there's been a slight decline in ios/android dev postings but I expect this would be due to flutter/RN cannibalisation from when I last looked. Jobs are still there though they'll always be dwarfed by the web dev market.
@@timothycurtis5694 stack overflow survey is a really poor representation and companies have way more websites than mobile apps. B2B web is still the main platform but B2C mobile seems to be where it is trending. If you know RN you also know React and will often work with both web and mobile.
Great takes on the cultural friction. Native mobile dev is full of engineers who want to work on frontend but hate JavaScript. I'm sure many of the mobile engineers joined AirBnB specifically because they have a strong pedigree of native mobile development (e.g. Lottie).
We use React Native for our app Solo. It’s been great for us to build quickly and deliver OTA updates. I doubt most people would know it’s not a “native app” and we’ve done barely any optimisation.
Hi 👋 native android developer here. Cross platform development is great and we also have a number of cross platform technologies to share code between platforms
RN is really the last option for us in this space - not because any uninstantiated hatred towards JS - but because of the lack of first class support from the native platforms themselves (from Google and Apple)
Native development is unavoidable - sure there are packages to deal with everything you can think of - but not all mobile developers work on greenfield apps with such use cases. Most enterprise mobile development use cases are about integrating with bespoke proprietary native APIs that doesn't expose RN/flutter plugin, and developers end up writing these integrations in native languages anyways - and to throw in a third toolchain (the web) into the mix just introduces too many moving parts.
It's totally understandable not to introduce RN into an existing codebase, however having native libraries you need to integrate with is not a good reason to avoid RN. It's actually quite easy to make RN packages for them to expose them to JS, and then you gain enormous benefits from having a single codebase that drives the app behaviour on multiple platforms. I have done native development which used alternatives to RN/Flutter for sharing code between iOS and Android and I will never do that again.
For us it is the first option. There is nothing that comes remotely close on DX and moving fast when it comes to developing for iOS / Android / Web.
If there isn't already a RN plugin for it we just build it. We have both native and JS/TS developers.
Sure it might not be an option when working on an old legacy application but for everyone starting something new I don't see why it shouldn't be the first option most of the time if you are building for multiple platforms.
@@kurtblackwell7752 I broadly agree - but with enterprise apps it's always legacy applications (by definition it's not greenfield)
Exposing JS was straightforward but there were some bottlenecks to watch out for - which might no longer be the case with the new JS core. Nevertheless the main issue I see is that RN doesn't provide a convenient way to interop with native apps that goes beyond than just showing a whole screen of RN components.
This is also true for Flutter and I agree, both user & developer experience isn't ideal.
However, the newest technology to evolve in this space - Kotlin Multiplatform - is a very ideal approach to let us interop with native platforms to the level that goes beyond just showing full blown screens or parts of screens. With KMP, you can create objects in Kotlin and Seamlessly hand over to native platforms and get it back without any bottlenecks or compromise. It's truly native in a way flutter or RN never was.
Is anything going on in Android? Yeah, Jetpack Compose is one of the best DX and performant UI frameworks available right now. It's development philosophy is based on modern React, hooks, and function components. There's actually a blogger who made a dictionary been React Native APIs and Jetpack Compose APIs and there's a comparable API for every single paradigm.
It's fantastic and comparably makes SwiftUI look clunky af.
I would like to see Theo compare React Native to Ionic React, since I don’t see many people talking about Ionic although they dropped Cordoba and are now using Capacitor
Ex Android Dev here. I’ve spent ~8 years doing exclusively it as a day job. In 2019 there were still a planty of projects based on java 1.7 and android mess 🤢. Kotlin was (and still is) fun, but even then devs used to write java in kotlin. It requires to write so much code to get anything up and running and also to support different sdk versions. Switching to RN was the best decission as I can be productive with TS and existing libraries, no need to use trillion of abstraction layers. Writing native modules in swift / kotlin where necessary can also be fun. Zero problems with performance that we were not been able to solve.
I suddenly felt dejavu watching this video. Was there some similar video on the channel or it's just The Matrix is weird? :D
Flutter is superior in every single metric it's also cleaner and much more productive
…..to you
Hey, first impression of the vid (5 seconds in): nice audio processing, feelin’ crisp!
I would not be surprised if more companies will drop React Native and go full on native or start using Compose Multiplatform / KMM due to it's ability to easily bridge native stuff with Compose/KMM
I was exited about kotlin multiplatform in… 2018. Still, they were not been able to do a significant move since then. Do you know any big app written in it?
Kmm is a dead project. Not maintained, Noone to ask how to make it work.
Bridging is way easier in flutter btw. You can even write all your logic in rust if you like.
@@adriankal I would agree that flutter’s ecosystem is bigger, however the documentation for KMM is there and their expect/actual mechanism is just beautiful. It makes it much easier to bridge native and non-native stuff. The biggest problem of flutter is actually dart. The language just looks like a mess of java/js/python. UI structure look just about unreadable. However I still believe that flutter is better then react native.
i think it's extremely important to learn the native sides (android and ios) before even touching react native. im not a big fan of expo since it adds a REALLY thick abstraction layer to my app which is hard to debug/look into. expo is like a cage which limits the powers of react native. i have once setup my app with expo and soon enough i had to eject because expo wasn't providing the things i needed anymore. finally being able to change actual NATIVE code was freedom but expo haunted the project til the last day. i had to refactor the whole application into a bare react native project and i haven't had any problems since then. additionally, you can write native modules by yourself instead of relying on (no longer) maintained community libraries all the way.
@ryaaann Can you recommend some good sources to learn what exactly is the way to go about building a native module? I've coded in ObjectiveC/Java a long time ago and i am curious about this
I MIGHT be weird, but the in-sentence cuts to cut out dead air seem a bit grating in this video. The roughly 10 seconds after 3:30 are the biggest offender. The audio artifacts from those cuts make it a tad harder to listen to than I'm used to with your videos. Obviously I don't know how the raw footage was, and if and how it could have been improved, but I would rather leave that bit of criticism than not saying anything 😅
Yea, but react native produces like 60 mb apk for the simplest app.
While I've used RN and really liked it, I think it's too easy to work with. For example, my university mobile app uses it and it's a MESS, things are flashing on the screen, sometimes it will log you out for no good reason, the app is slow, and the list goes on. It feels like the developers just wanted to ship as fast as they could without thinking if that was the best solution to the problem, and now we have a pile of code that is barely hanging together.
I hope there will be SvelteNative soon
There won’t be - Svelte is built heavily in browser standards.
100% with you. Great Work. Amazing!!!
A mobile dev, I get the point about expo and all that.... But native is native.... And React Native is not.... Its good no doubt... But not what I will want to try... Same for most of the Native Devs I know... They prefer switching to Flutter then touching React Native
I'd wager that most who hate on Native have never shipped mobile prod code in their life
react native is great just that debugging is really hell with the lack of info regarding where the fck or which code break stuffs
Expo adds on-device debugging in SDK 49. This enable chrome dev tools for network inspection, breakpoints, real console logs, and more. Highly recommend
@@Baconbrix hi bacon. y're always listing the community
If it weren't for expo, React Native would have been a joke now.
why?
@@arjundureja go back to 2017 and develop a react native app with 2 or 3 native device capabilities. You will start to hate yourself
@@ijazkhan3335what do you mean lol, I don't use expo right now but I still get benefits from react native, and the DX also much better than using Flutter, especially if I use expo it would be increasing benefit for me
react-native is also entering a new golden age with the new architecture, JSI and TurboModules.
"airbnb engineering is not something to look up to" - Now I fully understand why Gary Borton sucked so much
interesting video, but theo, did you not read that one article that airbnb wrote about react native?
for those who already know react learning react native is much much easy !!😃
When i start learning SwiftUI i feel it like React Native, just with the difference that is strongly typed and somethings are more tricky to reproduce like Ref
react native, expo, ionic... i've tried all of them multiple times and i've always had an endless amount of different errors that lead me to give up on those tools.
I get PTSD every time you mention AirBnB lint rules.
Can someone quickly explain why I would choose React Native over Flutter? Take React familiarity away. Assume I know nothing about both Flutter and React. I have to learn both from the start. Would you still recommend React Native over Flutter, and why?
When writing flutter components, it is very hard to abstract away business logic from the interactivity of widgets (components) on the screen.
I needed to hear this today.
I mean Airbnb dropped react-native, Shopify went all in with react-native. Many others are using react-native and many aren't. People use one side of the story and push it as the only story that exists, but probably for every company that dropped react-native, there are 10 companies that are happily using it.
flutter is good!! I know you dont like it, but its pretty good
Expo is the best!
I'm a full stack web dev and I still prefer Flutter ¯\_(ツ)_/¯
Finally, a video that would shut the naysayers! RN all the way!
Upgrading version react native break all in the project 😂, so painfull
Kinda besides the point, but I've got to admit I actually enjoyed their linting rules as a beginner, I learnt a lot from trying to understand them. But yeah, most of my junior colleagues back then just felt suffocated.
No Theo. There is actually a good reason for not using React Native. I’m sure the majority of Swift applications could be written in RN, but should they be? If you know Swift is there a point?
React Native is awesome man
Stop adding JavaScript to mobile apps! NOW!
I don't think devs not liking a tech should be a misunderstanding.
just because they don't like or use the tech in your stack, doesn't mean they don't build awesome apps.
there is no reason to ask "why", they have their own prefs.
Flutter is best.
After reading their post I would’ve thought the main downside that was just about their organization was first render time. But I don’t know anything about it. So what they say about it not being ok for initial start screens and deep links isn’t valid anymore ? Can you point me to interesting ressources on those topics ?
You sound very emotional
Thank you
Why not just do React with Capacitor?
You forgot to mention the "Please update sdk version" of their app when they release a new sdk version. It's the most annoying part of their tech for no reason other than piss their users off. They update their sdk while the actual emulator (expo go) is still not updated. You get frustrated, since you can't open any examples on their website unless you jump a lot of hoops.
What about Meta itself not building Threads app using React native 😢 ?
How about Google itself not building UA-cam app, Drive app, Gmail App and much more using Flutter 😢 ?
@@Reactnativetech what do they use ? I have no idea. I thought they used flutter @
@@Reactnativetech as if the apps you mentioned were released a few weeks back.. 🤷
@@cowabunga2597no they use java/kotlin on Android and in iOS they use swift
@@biplabduttaif flutter was a big deal it's possible they change it to flutter even it's old app, so I think flutter is not a big deal 😂
*Tauri* FTW! Framework agnostic, super performant (rust), tiny binaries, desktop/ mobile, native webview
@tonyhart2744 true.but that's the beat part, you don't have to touch the rust backend. Can literally wrap any web app with it and it just works. And nice js api for system interaction. Ofc best don't be soy and learn an actual language