What do you mean? Is there any doubt that they will? I would recommend to watch the Flutter/Dart talk on WASM I/O 2024... if in doubt!

@@Apenschi Google has a history of abandoning projects so people are asking them not to abandon this one :)

Toyota uses flutter for the infontainment system on their new cars, other big brands use flutter too, even google used it for google earth recently. I don't think they'd drop all this. They only kill what they don't consider successful enough or if they've built something they consider better. Flutter doesn't fall in either category.

@@kyriakos098 WELCOME KOTLIN MULTIPLATFOR

I hope and wish the same too 🥹

Google is some time very weird instead of focusing on flutter but good comes with compose which not much mature ,google would just focus on flutter only Flutter

Kotlin is more performant and would remain so for the foreseeable future.

@@muddi900 now no much different between flutter and native , flutter is mature now so performance is not a argument

Good question! There is a key difference, and it's for reasons like the ones we reference at 7:13. If the app is running in a non-fullscreen mode, OrientationBuilder wouldn't actually tell you if the window your app is running in is more tall than wide. Let's use a tablet as an example, it could be in landscape mode, but the app could be running on 1/3rd of the display with another app taking up the other 2/3rds, in which case your app would actually be taller than it is wide, even though you're in landscape orientation. Another difference is that LayoutBuilder allows you to move your widget to different places in your app, and it will always behave as expected because it gets the local min and max height and width. Let's say the widget was originally taking up the entire screen, but you want to move it to a side bar or underneath some other widget. The available space for the widget might change such that while the app window as a whole is more tall than wide, the space the widget has is actually wider than it is tall. Performance wise, there's essentially no difference between the two. If your screen size isn't actively being changed, both OrientationBuilder and LayoutBuilder would do some quick calculations to grab the current orientation or available space (respectively), and then build the child widget. All of that is extremely fast. If you're changing the size of the app window or the space your widget is given to render, LayoutBuilder would end up rebuilding your widgets every time that size changes (with a max of once per frame refresh). This isn't really a "performance" implication, it just means the UI would respond correctly while the resizing is happening. Flutter can rebuild widgets extremely quickly.

@@tylerhollandgoog Amazing!! Thanks

WELCOME KOTLIN MULTIPLATFOR

NO , THEY LEAVE FLUTTER , WELCOME KOTLIN MULTIPLATFOR