I like this video because it has nice illustrated visual examples, but everything about it works exactly the opposite compared to what I'd normally expect. Odd. As a lot of people do like this, maybe I'm the one working in reverse.
We're happy to hear this was helpful for you 🙂 If you'd like additional information about Compose modifiers, feel free to check out the resource linked below ⬇ goo.gle/3JlrE82
Was wondering the same thing, but it probably starts with the root node using all available space depending on what type of layout it is (so if compose view is taking up entire viewport, and the first compose node is unbounded, the constraints are probably bound to the size of the screen).
We have some great resources to help you get started with Compose. Check out our Introduction to Compose Basics from our MAD Skills series here: goo.gle/418kdaF We also have a guide on building your first app with Compose. You can find it here: goo.gle/419n1US
Everyone needs to start somewhere. I thought at first, the API looks similar to a builder pattern and so I thought the chain order does not matter. That's why when I realize something amiss with the modifier function(s) behaviour, I look up the documentation and they wrote: "The order of modifier functions is significant".
The `Modifier` is an interface, and every other method you call on it it's just an extension function. Therefore, no the Modifier interface isn't bloated.
@@TheMikkelet Probably because in 2007-2008 Android had to be rushed to the market in order to compete with iOS, which looking back, was a smart choice because Android is now still around. Otherwise, Android would be just like Windows Phone, with a pretty strong tech foundation, but DEAD :D
@@n-o-i-d Android was around before iOS. iOS was just more popular. Android was conceived in early 2000's and bought by Google in 2005. The only thing that iOS impacted was forcing Android to move from being button based to touch based.
Catch more videos → goo.gle/layouts-mad
Highly condensed video content. Learnt a lot. Thank you!
It's our pleasure, Roshan! Glad you enjoyed the video 😎
@@AndroidDevelopers1:17
@@AndroidDevelopers1:29
Awesome episode! Very very educational. Thank you!
Well done video, it helps you to easily understand how modifier works behind the scene
thank you for the guide. Please make more of this.
Extremely good presentation!
I like this video because it has nice illustrated visual examples, but everything about it works exactly the opposite compared to what I'd normally expect. Odd. As a lot of people do like this, maybe I'm the one working in reverse.
Really useful video, nice job!
We're happy to hear this was helpful for you 🙂
If you'd like additional information about Compose modifiers, feel free to check out the resource linked below ⬇
goo.gle/3JlrE82
It finally made more sense to me, thanks!!
wow this was amazing
At 11:28 it's not clear to me why the clip draws itself at the center of the canvas instead of from the top left corner.
So clear!
amazing video, thanks a lot
How does the root node decide what the height and width constraint should be ?
Was wondering the same thing, but it probably starts with the root node using all available space depending on what type of layout it is (so if compose view is taking up entire viewport, and the first compose node is unbounded, the constraints are probably bound to the size of the screen).
Hi Jolanda!
Thank you please Help me to start with compose.
We have some great resources to help you get started with Compose. Check out our Introduction to Compose Basics from our MAD Skills series here: goo.gle/418kdaF
We also have a guide on building your first app with Compose. You can find it here: goo.gle/419n1US
There’s Denis Neklyudov in the Image )
1:00
question I used border on column like bending the top left and top right edges but the ripple effect or the click effect still took the whole column
You should wrap it in Surface and use the onClick Lambda.
@@hashemmousavi2451 border the surface right
@@zaryabK-vi8fh I think so, I it doesn't work let me know
@@hashemmousavi2451 I did and nothing changed so I just left it there
Love it
I actually can't believe someone still thinking that modifier order doesn't matters
Everyone needs to start somewhere.
I thought at first, the API looks similar to a builder pattern and so I thought the chain order does not matter.
That's why when I realize something amiss with the modifier function(s) behaviour, I look up the documentation and they wrote: "The order of modifier functions is significant".
Remember when we used to create all complex ui using just linearLayout and RelativeLayout .
I thought we were going away from Views because the View class had gotten too bloated, but now it feels like we just have a bloated Modifier class 😅
The `Modifier` is an interface, and every other method you call on it it's just an extension function. Therefore, no the Modifier interface isn't bloated.
@@saidooubella Ah that's fair. Wonder why they didnt make the View to work this way
@@TheMikkelet I guess because it was written in Java.
@@TheMikkelet Probably because in 2007-2008 Android had to be rushed to the market in order to compete with iOS, which looking back, was a smart choice because Android is now still around. Otherwise, Android would be just like Windows Phone, with a pretty strong tech foundation, but DEAD :D
@@n-o-i-d Android was around before iOS. iOS was just more popular. Android was conceived in early 2000's and bought by Google in 2005. The only thing that iOS impacted was forcing Android to move from being button based to touch based.