IssueTracker

Running the code from the map_swipe branch - I'm seeing that MapActivity and MapWithDismissActivity are scrolling the map ok, but the SwipeToDismiss is not working (so that's different to the behaviour reported above). But I do see the reported behaviour in App itself, that within SwipeDismissableNavHost, that SwipeToDismissBox is always handling horizontal swipes, so probably the map does not receive those gestures. Not clear yet why this is, because Modifier.edgeSwipeToDismiss is working for other horizontally scrollable components.

Having looked into this in more detail, GoogleMap does not support nested scrolling, so it's not compatible with Modifier.edgeSwipeToDismiss. Instead, we've seen that adding an 'enabled' parameter to SwipeDismissableNavHost and setting enabled = !cameraPositionState.isMoving would allow panning horizontally and vertically in the map (and adding a button to dismiss the screen). NB caveat is that there's a bug where the initial swipe needs to be vertical to avoid the parent handling it - this affects other scroll types as well as the Wear SwipeToDismiss.

We will look at adding the enabled parameter to Wear Compose in the near future (after release of 1.0).

The following release(s) address this bug.It is possible this bug has only been partially addressed:

• androidx.wear.compose:compose-navigation:1.3.0-alpha02

In which version of Compose will the modifier be available?

in 1.1.0-beta03

Since there is no key param available in LazyVerticalGrid items or item. How are we supposed to use it with them.

Would it still work if I wrape item content in key composable

+1, can you please provide an update? :)

I think that list animations are pretty important and we can't always animate lists the way we want using the current APIs.

For instance, I'm trying to nicely animate a list whose items are updated every once in a while (some items are updated, some are removed, some are added). I tried to achieve this using an AnimatedVisibility block for each item (see b/222475821 for more info or this SO answer which seems similar to my solution) and it looks alright but it's not optimal because I want this list to behave the same way it would if I were using TransitionManager.beginDelayedTransition in the traditional view system:

• when an item is added, we first expand the location of the item (and move the siblings and resize their ancestors) then fade it in.
• when an item is removed, we first fade it out then shrink the location of the item.

We can simulate something similar by adding some delays in the AnimatedVisibility enter & exit transition specs, but it does not work well when removing and adding elements at the same time. This is illustrated in the video below: if my list has a single item and that I remove it but add a different item at the same time, then the following happens:

1. The list grows because of the new item that is added. At the same time we fade out the item that is removed.
2. The list shrinks because of the item that is being removed. At the same time we fade in the item that is added.

The ideal animation would just fade out the first item, then directly fade in the new item given that we don't need to shrink/grow the list.

It would be really great if this was handled out of the box by LazyColumn/LazyRow, for instance like this:

// Because we are using a MutableStateList
// or any other observable list, LazyColumn
// can keep track of the updates and animate
// its items in/out & move them accordingly.
val items = remember {
  mutableStateListOf<Item>(/* some default list */)
}

LazyColumn {
  items(items, { it.id }) { item ->
    MyItem(item)
  }

  item {
    Button(onClick = {
      if (items.isNotEmpty()) {
        // This will automatically animate given that we
        // know exactly which item has been removed.
        items.removeAt(0)
      }
    }) {
      Text("Remove First")
    }
  }
}

We could also have an API that takes any kind of List<T> + DiffUtil.ItemCallback<T> (or similar) :)

Can you please provide any status update / dates if possible?

Hi, the Play store team is working on a feature which could greatly benefit from LazyColumn's addition/deletion animation support. Do you have an updated ETA that you can share with you? Thanks!

Comment #35: Please don't use feature tickets as a place to ask for debugging assistance. If you have a reproducible Compose bug, please file that as a separate bug (and don't use images of code - we can't copy-paste from images).

its almost been 2 years now and even your internal teams at play store are asking for the item addition deletion animations, I was the first to bring this up in this thread first.

Is there any ETA on this ? It was a core functionality with DiffUtils which we shouldnt find workarounds as an implementation for Compose !

Could anyone from Google please share an ETA on this

Hello. We are currently finializing the design for the underlying mechanism we will be using for the disappearance animations. Sorry, we can't give exact estimations, but I can reassure you this feature is in works

bro

I kind of agree with the last poster, if we all "bro" the developers every year or month to bump the thread, they might feel pressured to finish the removal/addition animations. Anyways, hang in there champ, they're probably almost done with that last piece of work

Yesterday was the 4th year open anniversary of this issue lol

It's coming anytime now (probably not in the next 1-2 releases though): https://android-review.googlesource.com/c/platform/frameworks/support/+/2647907

Item appearance and disappearance animation support was added into LazyColumn and LazyRow. Previously it was possible to add Modifier.animateItemPlacement() modifier in order to support placement (reordering) animations. We deprecated this modifier and introduced a new non-experimental modifier called Modifier.animateItem() which allows you to support all three animation types: appearance (fade in), disappearance (fade out) and reordering.

This change is expected to be released as part of 1.7.0-alpha06 release.

Port of this modifier into lazy grids is tracked here: b/330510929

To staggered grids here: b/330511290

Support of other animation types aside of fade in/fade out is tracked here: b/330152398

@comment #51: Please file a separate bug with reproduction steps.

Hello, in the doc, under the heading "Item animations", the last sentence that references this issue should be changed, or removed: https://developer.android.com/develop/ui/compose/lists#item-animations

It still says:

Aside from reorderings, item animations for additions and removals is currently in development. You can track the progress in issue 150812265.

Thank you for letting us know! We've updated the documentation page :)