what is your mobile/cross-platform Framework of choice?mine is picrelwhat is your most refined/interesting project?I just got started using the flutter 2d game engine Flame and made a pong clone to get a feeling of the engine
>whole app is just a 2d canvasyeah... nah.
>>96089648why should I care how the framework draws my app on any device?
>>96089513flutter is pretty based
>>96089713>why should I care how the framework draws my app on any device?Performance
>>96089723Flutter is really cool and Dart is pretty easy to get used to
I have written a few apps in flutter, the main thing that sucks about it is that it doesn't actually draw any native widgets, but emulates them.I use nativescript at work, it's aids. who would have thought running js on a phone app would suck balls?honestly, mobile dev needs to get its shit together.
>>96089513Jetpack compose for AndroidCompose desktop for Windows & LinuxSwiftUI for iOS and macOS
>>96089802damn the 2d app with a hamburger menu accessing the plaintext database is really gonna stuffer from the performance issues!
>>96089934Yes. they really do. It's as embarrassing as it soudns. Flutter apps had an abysmal scrolling experience on iOS until very recently, and you couldn't even trust it to do lazy loading correctly
>>96089911Based and nativepilledAlso compose multiplatform for a single codebase regarding the business logic
>>96089934>damn the 2d app with a hamburger menu accessing the plaintext database is really gonna stuffer from the performance issuesKek at the coping fluttertard
>>96089648doesn't qml do the same? Its a lot less demanding but the tooling is shit.
>>96090010what exactly are you demonstrating?What should the fucking app do if you scroll you retard
>>96090241>Buggy scrolling is actually fineCope levels increased by 100x
>>96090773>scrolls on a scrollable list>items scroll just fine>it's buggy because I say sofuck off idiot
>>96091070>items scroll just fineThey literally don't on some devices, that's the fucking point brainlet
>>96089907>the main thing that sucks about it is that it doesn't actually draw any native widgetsIt's the only sane way if you want your framework to be cross platform. Look at Xamarin - you can either use a small number of widgets that are present on all platforms or you have to write wrappers for widgets you need on your own.
>>96091953>It's the only sane way if you want your framework to be cross platformWrong, it's the only brainlet way.A sane way would be a mapping system with components that are an intersection implementation of the respective native systems, and then specific components that are entirely unique to the given native system. It's just a lot of effort to do. The closest thing to it right now is compose multiplatform
>>96089513Electron + React and React Native.
>>9609209380iq take
>>96092093Sounds like you're talking about flutters platform interfaces? You can use native code and it'll auto select the implementation for the given platforms
Anyone have experience with Ionic? Some coworkers of mine like it but I see a lot of people talking shit about it too
