I absolutely love this! Direct native interop will be a game changer and I love how dart latest syntax looks and feel so much like swiftUI its wonderful I have been supporting flutter since 2017 and I am so proud of flutter!!!
4:43 I also wanted to improve code readability so I've created a vscode extension that automatically fades out the less important widgets. It's called Flutter Highlighter
Direct Native Interop is the best thing ever !!!! More reserved on the decorators, I actually already do this myself in some case with extensions, but I refrain to use it more often because it makes things less readable. From beginning Flutter has strong opinion on the wrapping-V-shaped style widget, which means devs have adapted to read things this way, and to know if something is aligned, center have padding etc, we use to look at parent widgets. Decorator break this and makes it longer to identify why a widget behave the way it does. Less easy to collaborate with other devs with different style. That's my opinion :')
Thank you “Flutter team” for this amazing Xmas gift haha. Native interop is what I’m most excited about. However, the current situation we import a plugin, use it once and the package handles the same logic on different platforms. Using the new approach would mean we need to separate the uses for different platforms right? Or maybe will make it easier to create a package written all in dart to sort the different platforms. But that means an added layer on performance maybe? I remember the full video mentioned something about this approach will improve performance as well but I didn’t get it
@@Khanzaki1 probably wont be entertained until we get 3d support on all platforms with Impeller/flutter_gpu even then, highly unlikely since they barely have enough team members for the current platforms
I would love to say Thank you for the hard work and because of Flutter I could make my own app for my own business. Still learning a lot but I love using it!
@@megasticky8968 for me , the most ammount of things related to react are tedious to use. i mean, super slow, super heavy, syntax verbose, performance worse than others, and so on.
my reply keeps getting removed by yt, sorry for duplicate comments if it shows back up. Canonical showed off multi window support for Windows recently. there has been great progress.
Love a lot of these changes, but please dont waste time with live-editting... there are genuinely more important issues. Flutter Flow already creates messy codebases, no reason for Flutter to go down that road
Thank you. Great dev tool. Make documentation more comprehensive and offline. Make it searchable. Python offline documentation is still the best I've used so far. Bootstrap too tried with their documentation. Let's have a great and offline documentation for flutter.
Decorators and direct native interop are really cool ideas! These features would make coding much easier and readability would be on SwiftUI level. If you would make it possible to write code almost as in SwiftUI - a lot of Swift Devs would like it!))) And all lot of Flutter developers would become much more productive!))
@@martinlesko1521 seems more like a skill issue... done a bunch of Web applications so far and haven't envpuntered any issues or Limits compared to Android or ios...
Using platform-specific widget sets, thus writing separate UIs for each platform is so Xamarin-before-Forms... Please come up with a cross-platform wrapper widget sets that automatically use cupertino widgets on macOS/iOS, fluent_ui widgets on Windows and Material on Android. Yes, it will be a relatively smaller subset of common widgerts such as button, slider, text entry, checkbox, alert dialog, etc... but still very useful.
@@tillwietlisbach9471 This should come from the Flutter team, including the official docs. So it gets adopted and becomes the standard way of writing the UI.
@ why? my app doesn’t use any of them. Technically material widgets for some part but styled the way I want. A lot of apps today get bespoke ui interfaces that align much more with the brand ui than any design guidelines from any other company.
It all sounds great except for decorators which are a bad idea: they make it harder to understand which widget "contains" which. I've already advocated against it in our team (using extensions) and I think our codebase is more maintainable and understandable like this. Please don't do it.
Decorators idea is awesome but the current sample is not very good. They should kill decoratedBox and BoxDecoration, and just inline to .border(), .shadow(), etc. Just like SwiftUI does. Way better. Tailwind is also awesome.
Decorators are a terrible idea. Adding an extra coding style will only create more problems, from formatting issues to linting conflicts and inconsistent standards. What makes Flutter great is its clear tree structure and verbose declaration, which makes the code easy to read and maintain. Using decorators will mess up the way we read code, as it seems to work from bottom to top based on the screenshots. VelocityX has this approach, and after using it in a few projects, it became really hard to maintain for both existing team members and newcomers. !! Please don't add them !!
the presenter seems anxious and make small mistakes as if his job was treatened to disapear. is google pushing to show results or terminate flutter team?.. you know, mistakes like forgetting the flow of things that had to be said and making up inmediately later, talking like a robot without showing the emphasis of the understanding of each sentence, as if blindly reading teleprompt. and those things that happen when the mind is rumiating other stuff while doing something else.
Please reconsider decorators. On the surface it may seem like a good idea, but in practice it's going to lead to widget code that is far more difficult to understand because parts will be top-down and parts down-top.
The Flutter team has been unable to enable Google Sign-In on desktop apps for five years. Flutter is still not ready for production use. If the developers lack the necessary skills, consider handing it over to Microsoft. In 10 years, will you still be boasting about creating UI widgets?
direct native interop is what im most excited about
this is the one think that will change flutter for ever. Imagine not neading to write native. this will be the true CROSS PLATFORM
yes, it will be game changer for flutter if they can do it!
Yessssssssss
direct native interop will be live changing
My top 3 🥳
- Direct native interop
- Decorators
- Enum shorthands
I feel like Flutter is the best framework in human history
I absolutely love this! Direct native interop will be a game changer and I love how dart latest syntax looks and feel so much like swiftUI its wonderful I have been supporting flutter since 2017 and I am so proud of flutter!!!
4:43 I also wanted to improve code readability so I've created a vscode extension that automatically fades out the less important widgets.
It's called Flutter Highlighter
Exciting for the future of Flutter
Widget preview is somewhat similar to Composable Preview. Welcomed!
Direct Native Interop is the best thing ever !!!!
More reserved on the decorators, I actually already do this myself in some case with extensions, but I refrain to use it more often because it makes things less readable.
From beginning Flutter has strong opinion on the wrapping-V-shaped style widget, which means devs have adapted to read things this way, and to know if something is aligned, center have padding etc, we use to look at parent widgets. Decorator break this and makes it longer to identify why a widget behave the way it does. Less easy to collaborate with other devs with different style.
That's my opinion :')
This is awesome! I shared with my Vietnam Community and got many impressions about all of these changes
Thank you “Flutter team” for this amazing Xmas gift haha. Native interop is what I’m most excited about. However, the current situation we import a plugin, use it once and the package handles the same logic on different platforms.
Using the new approach would mean we need to separate the uses for different platforms right? Or maybe will make it easier to create a package written all in dart to sort the different platforms. But that means an added layer on performance maybe?
I remember the full video mentioned something about this approach will improve performance as well but I didn’t get it
Yeah most likely will have to create a common interface ourselves, but if you're not going to publish it, it doesn't need to be comprehensive
Direct Native would be huge.
Direct native interop, visual editing, DevTools better, enum shorthands, Dart macros... Flutter is getting more amazing every day!
Any plan to support flutter for Android XR?
@@Khanzaki1 probably wont be entertained until we get 3d support on all platforms with Impeller/flutter_gpu
even then, highly unlikely since they barely have enough team members for the current platforms
Android apps will be ready for Android XR just as iOS apps will be ready Vision Pro.. our apps should work out of the box right?!
@@s.bamahfoodh not necessarily, it depends on how the input is implemented. Flutter apps dont work very well on vision os because of that
@@BooleanDev
Can I ask why would the input of an iOS app built with flutter be different to the input of an app built with Swift? The same for Android
Looks good, please fix the image filter quality on Canvaskit, as it is causing the image to appear pixelated. Thank you.
I would love to say Thank you for the hard work and because of Flutter I could make my own app for my own business. Still learning a lot but I love using it!
this is amazing 😮, I'm really glad i started flutter few months ago and didn't follow the trend of the javascripters. Just amazing ❤
I am so so so excited for Direct native interop. Fingers crossed I hope it comes as quickly as possible.
love you flutter i don't want to learn react native, i want flutter
RN better
@@megasticky8968 for me , the most ammount of things related to react are tedious to use.
i mean, super slow, super heavy, syntax verbose, performance worse than others, and so on.
@@megasticky8968 no
@@megasticky8968 Yeah, and you are spending the little time you have here on earth under a Flutter post.
Native Dart Introp is exciting ❤️
No mention of multi window support for desktop 😮💨
Yep, sad...
@@Doman0204 Canonical (Ubuntu) posted a demo video of it on youtube. It's currently most complete on Windows
it is alreaddy there and they are merged some related PRs
@@Doman0204 Ubuntu did a demo recently, they've been working on this
my reply keeps getting removed by yt, sorry for duplicate comments if it shows back up.
Canonical showed off multi window support for Windows recently. there has been great progress.
With this, guys, no one can convince me that Flutter is not the Number 1 cross-platform app development framework for mobile.
I'm looking forward to these new updates including the macros
No mention of conditional argument feature 😢, but excited about flutter future❤
Lovely, Flutter is best :D
Love a lot of these changes, but please dont waste time with live-editting... there are genuinely more important issues. Flutter Flow already creates messy codebases, no reason for Flutter to go down that road
What about a direct interop for the web?
Is it me or does the new syntax looks a lot like SwiftUI? 5:15
Haha love all this ideas. But can't ignore the fact Flutter is looking more and more like Compose and Dart is starting to look like Kotlin
I love it haha
I don't see anything wrong with that
Long Live Flutter!!!
Thank you. Great dev tool. Make documentation more comprehensive and offline. Make it searchable. Python offline documentation is still the best I've used so far. Bootstrap too tried with their documentation. Let's have a great and offline documentation for flutter.
how we can get this widget_preview ? any one know?
Interesting and exciting, also cool shirt lol
Decorators and direct native interop are really cool ideas! These features would make coding much easier and readability would be on SwiftUI level. If you would make it possible to write code almost as in SwiftUI - a lot of Swift Devs would like it!))) And all lot of Flutter developers would become much more productive!))
Dear flutter team, Please support GetX state management, and make that packages better, please support that developer
Love it !
Awesome❤
5:25 reminds me of Kotlin!!
Amazing
flutter is the future
Thanks.
Swift, is that you?
The code example looks more like Jetpack Compose
The telepromter is set too far below the camera.
you forgot about multiple desktop 😐
Focus more on web
?
That tone doesn't seem polite.
@@RamVerm what´s unpolite about that ? Flutter for web sucks even amongst flutter devs
@@martinlesko1521
Other than SEO and loading time, what u want to be fixed asap?
@@martinlesko1521 seems more like a skill issue... done a bunch of Web applications so far and haven't envpuntered any issues or Limits compared to Android or ios...
If you want web, use a good framework not flutter for web
I'm still waiting for a way to bootstrap a whole federated plugin structure directly wirh "flutter create"
👏
Ui ux iDE like visual studio or unity will be great
Using platform-specific widget sets, thus writing separate UIs for each platform is so Xamarin-before-Forms... Please come up with a cross-platform wrapper widget sets that automatically use cupertino widgets on macOS/iOS, fluent_ui widgets on Windows and Material on Android. Yes, it will be a relatively smaller subset of common widgerts such as button, slider, text entry, checkbox, alert dialog, etc... but still very useful.
just write a wrapper for the widgets you need.
@@tillwietlisbach9471 This should come from the Flutter team, including the official docs. So it gets adopted and becomes the standard way of writing the UI.
@ why? my app doesn’t use any of them. Technically material widgets for some part but styled the way I want. A lot of apps today get bespoke ui interfaces that align much more with the brand ui than any design guidelines from any other company.
@@tillwietlisbach9471 Agree for mobile but such apps look way out of place on desktop.
@@tillwietlisbach9471 For mobile, yes. But such apps look way out of place on desktop.
Not the decorators...
i didn't hear about macros.
Would Google abandoned Flutter in future ?
Second time this year fighting with a new release that breaks Gradle. Please slow down and ship stable releases
Not a word about koalas?
direct native interop was done by NativeScript many years ago using JS and it was complete disaster IMO. not sure how flutter would do it differently
Not a word about macros?
Seems like it will be ready in 2026 only
@@SergeiLitvinenko still a lot of work to be done before its stable
@ to me it looks more like this approach is abandoned for some reason. I mean, they would at least mention it otherwise, no?
@@SergeiLitvinenko no because it is nowhere near being finished. Probably everything else he mentioned will be done in 2025.
It all sounds great except for decorators which are a bad idea: they make it harder to understand which widget "contains" which. I've already advocated against it in our team (using extensions) and I think our codebase is more maintainable and understandable like this. Please don't do it.
Decorators and enums shorthands!!!
Decorators idea is awesome but the current sample is not very good. They should kill decoratedBox and BoxDecoration, and just inline to .border(), .shadow(), etc. Just like SwiftUI does. Way better. Tailwind is also awesome.
Focus please on web. SEO and ctrl + f issue should be number 1
Decorators are a terrible idea. Adding an extra coding style will only create more problems, from formatting issues to linting conflicts and inconsistent standards. What makes Flutter great is its clear tree structure and verbose declaration, which makes the code easy to read and maintain. Using decorators will mess up the way we read code, as it seems to work from bottom to top based on the screenshots. VelocityX has this approach, and after using it in a few projects, it became really hard to maintain for both existing team members and newcomers.
!! Please don't add them !!
the presenter seems anxious and make small mistakes as if his job was treatened to disapear. is google pushing to show results or terminate flutter team?.. you know, mistakes like forgetting the flow of things that had to be said and making up inmediately later, talking like a robot without showing the emphasis of the understanding of each sentence, as if blindly reading teleprompt. and those things that happen when the mind is rumiating other stuff while doing something else.
Please reconsider decorators. On the surface it may seem like a good idea, but in practice it's going to lead to widget code that is far more difficult to understand because parts will be top-down and parts down-top.
The Flutter team has been unable to enable Google Sign-In on desktop apps for five years. Flutter is still not ready for production use. If the developers lack the necessary skills, consider handing it over to Microsoft. In 10 years, will you still be boasting about creating UI widgets?