CoordinatorLayout | CoordinatorLayout demo | Learning library

I have a view hierarchy as shown in the image below.

I'm getting strange scroll behaviors like,

1. If I scroll (drag slowly or fling) from Area 1 the AppBar collapses along with it. This is fine.
2. But if I drag slowly from Area 2 the AppBar does not collapse. It stays there and RecyclerView goes beneath it. However, it works fine with a fling.

activity_challenge_detail.xml

I use a CollapsingToolbarLayout and a BottomAppBar reacting to scroll changes in a CoordinatorLayout (collapsing and hiding on scroll). As I can't use a NestedScrollview as parent of the RecyclerView because it leads to issues when I need to use scrollToPosition() or when an item is dragged out of the bounds (It doesn't scroll to move the item), the scroll behaviors are not working for the CollapsingToolbarLayout and the BottomAppBar.

I tried android:nestedScrollingEnabled="true" but it was not working

How can I keep the scroll-related behaviors in the CoordinatorLayout without NestedScrollview ?

How to use View binding in SupportMapFragment? ref my code

I have a map fragment in the layout, I want to use view bind in the fragment.

val mapFragment = childFragmentManager.findFragmentById(R.id.map) as SupportMapFragment

Plz Need solution..

In all the samples and on the Material Design website BottomAppBar is used as a direct child of CoordinatorLayout. I have read this is the recommended practice. I have tried it as a direct child of ConstraintLayout and it works fine. Why is this recommended? What is the purpose of wrapping it up in CoordinatorLayout?

I have a custom CardView that contains a Button, a RadioButton and some Text. I have several of these card placed in a GridLayout. My goal is that each button will play a different sound that will be assigned to it. Is there a way to create one onClick method, that will change the sound played based on which button is clicked? Or do I have to assign a new onClick for each button?

Here is my activity_main.xml

I am trying to implement collapsing toolbar behaviour in my app with a tab layout. I want to hide the toolbar when in collapse mode and just show the tab layout in collapse mode and in normal mode until collapsed I want to show the toolbar with the title of the app. Currently, it works as I want in collapsed mode I just want to add a toolbar that hides in collapsed mode.

My code

Actually in my app i had an activity which had a include of first fragment in it and then from that fragment i was able to press some buttons to navigate to another fragment, now i would change the activity and add a tablayout from which i will be able to navigate between the three fragments i have, but by reading the documentation i'm can't understand on how i can use the ViewPager2 to show my fragment in it by cliking on the tab.

My activity layout looks like this now:

I learned today that there is something called viewbinding other than databinding.

I was new to viewbinding, but I was already using it in code.

In other words, I knew it was data binding and was using it wrong.

To use viewbinding i need to apply below code in gradle. However, I have never applied anything other than data binding.

dataBinding { enabled = true }

However, in my code, it is accessed through the ID of the view with binding.title.text-like code. There is also no tag. Isn't this a view binding?

XML

I am working on an app using a CollapsingToolbarLayout, with an ImageView inside it. I wanted to add a gradient on top of it to look nicer and to be able to read the CollapsingToolBar title better, so I made a little hack and added a Relative Layout with a textview inside it, then I added a background to that same TextView (which is the gradient I was talking about). The problem with this is that when the ToolBar is collapsed, the gradient still shows over it and I dont want it to happen, how can I make it invisible when the ToolBar is collapsed?

Design: