Compose Modifiers deep dive
Vložit
- čas přidán 24. 10. 2022
- A deep dive into the history of Modifiers and the constraints of APIs. As well as the problems they are meant to solve leading up to a major overhaul in implementation in 1.3 and the addition of several lower level, but powerful, experimental APIs that we will be migrating to over the course of 1.4. This talk will go into the why’s and how’s of this migration, how it impacts developers, and the performance impact it will have for end users.
Speaker: Leland Richardson
Watch more:
Watch all the Android Dev Summit sessions → goo.gle/ADS-All
Watch all the Modern Android Development sessions → goo.gle/ADS-MAD
Subscribe to Android Developers → goo.gle/AndroidDevs
#Featured #AndroidDevSummit #Compose - Věda a technologie
You guys are doing great job about Compose API. The best UI framework I've worked with!
You know what they say, some of the best projects are done when U and I work together 😎 😀
Loving this type of content!
If you are enjoying this type of content, make sure to catch all the Android Dev Summit sessions here: goo.gle/ADS-All
Let us know what your favorite one is!
I really love this talk. Good job compose team
"We only make public what's absolutely necessary" - I hope you consider exposing more properties or alteast parametarized them that we can easily modify, such as the offset settings of Scaffold's bottombar or floating action button. I understand there are certain Design (Ui/Ux) principles (e.g Material) that we (us) need to follow, but too much of that restricts the creativity or worse preventing a better functionality for users.
Wonderful talk !!
One of the best compose engineers 👏
Great talk. Sorry, missed seeing you @ ADS. Hope to catch up soon.
Not a problem, Siamak! We've got you covered in the video description as well as a link below for more Technical Talks from the Android Dev Summit 2022😊🙌
Technical Talks at the Android Dev Summit → goo.gle/3sRy9pN
love it!
We're glad to hear it! Don't forget to check out the link below for even more Dev Summit content, including Technical Talks where we discuss your favorite Modern Android Development tools and APIs 😄
Android Dev Summit '22 Technical Talks → goo.gle/3TU097S
🥰Nice talk! Wondering anywhere can I download this copy of keynote ?
Thanks
Great Job!!!
We're thrilled that you enjoyed Leland's video! Thanks for watching, Juan 😎
If you liked this, be sure to catch even more Android Dev Summit sessions right here→ goo.gle/ADS-All
Ở 1 khoảng thời gian lâu về trước khi tôi đang tải game về thì mất kết nối và địa chỉ của tôi từ đó nó bắt đầu không ổn, cảm ơn.
0:09 😢
Пока flutter лучше. Он еще поддерживает desktop compile
Jetpack Compose is going to dead end
Why so?
@@gi1dortrt😅😅t6t6tt😅😅😅t😅trt😅t6rt😅😅😅😅😅😅😅😅t6tt😅😅😅t😅😅😅😅trtt😅😅t😅😅😅😅😅😅😅😅t😅😅t😅😅😅😅tr😅😅😅😅t😅😅😅😅😅😅😅r😅😅😅😅r😅t😅😅😅😅😅😅trr😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅t😅😅😅😅😅😅😅5😅😅😅😅r😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅
@@gi1dorThere will always be the next new shiny thing. Google and Apple are especially big on this theme. Been doing Android for eleven years--always something new that requires changing heaps of code that used to work perfectly. Remember how great the Eclipse IDE was--what an improvement over vi and command line compiling!
@@scottbiggs8894
Compose is not just the new shiny thing, it's official UI framework of Android, and there is no way back from it. The existing code will work, View will be on maintenance mode forewer, so no urge to rewrite anything if you dono't want
If something new and better will be created, great, let's see and adopt. But I don't see anything in next 5 years on Android, and it's very minimal estimation, Compose here (same as Views) is until will exist
> Remember how great the Eclipse IDE
Not really, Eclipse never was so great, before Android was even released, for BE development (JS/PHP) Eclipse solutions were a few heads below what JetBrains offered 15 years ago when I first migrated. Same for ADT on Eclipse, they were worse than unofficial IDEA support from JB a few years before Google officially switched
Compared to Vim, yes, but I don't understand why making this comparison and how it related
Why should a developer ever have to see a video like this? This shows the failure of the team to abstract key concepts.
It's good for reference in case you want to use Modifier.Node, but the talk effectively *is* a post-mortem of how the original Modifier.composed {} was an abstraction with too high cost.
You might not find it interesting, but there are lots of people for whom it might be useful to know, whether just out of curiosity for how the underlying infrastructure works, or because they want to make contributions to the project
And the video is titled "deep dive" for a reason