Good format! Straight to the point. Reminds me a lot of the Flutter widget-of-the-week format, but a little more "beefy". Appreciated!
Protip: Scaffold already handles most of the insets under the hood!
THIS IS WHAT WE ALWYS WANTED, THANK YOU ANDROID TEAM. PLEASE KEEP THE GOOD CONTENT COMING!!!!!
This was super useful and easy to understand!
This will make me love Android even more. Every app should've always been edge-to-edge like iOS.
wow, perfect update for end users! It makes all the difference to us!
Exactly what I was looking for
Great, your voice is amazing, I think I should to integrate this in my project, after synchronization and list sharing
Let's gooo android development baby 💥💥💖
Excelente consejo
We need guidelines for our screen designs as we transition to edge-to-edge (e2e) layouts. Previously, we didn’t use e2e, but now that we’re adapting, we’re encountering some height issues for components. For example, we calculate button heights programmatically based on the screen height. In the past, we determined screen size by subtracting the system bars, but if we use the same approach now, our container starts from the top, causing the top components to be hidden. Adding padding to the container resolves this, but it also increases component height, making the UI look different compared to the previous version compiled on Android 34. We need specific guidance for implementing e2e layouts, including best practices for handling the navigation bar, tab bar, nested scroll views, parallax scrolls, and other components.
Nice speaker❤
love it ❤
What if we want to make sure we don't enableEdgeToEdge() when the activity goes thre configuration changes
"...take a look at the documentation." I found this in the documentation! How does this work with Scaffold?
now imagine implementing that gradient toolbar in XML, LOL
Hide the state bar cause an error 😢
This is all dandy. But if left unconfigured you force edge to edge. But you also made sure that things like camera views don't scale that way. But display metrics still reports edge to edge dimens and insets for those. Why not have the api return bound appropriately rather than make me calculate it 😡
@AndroidDevelopers