I encountered another issue with `stackAnimation`,...

# decompose

[Philip Dukhov]

I encountered another issue with stackAnimation, which is probably related to movableContent, as discussed here.

When I push a screen with a text field and this text field focuses automatically with a launched effect, the text field becomes unfocused after the transition finishes. If this is not a known bug and you need a reproducible example, let me know. I stopped investigating when I found that removing stackAnimation fixed the bug.

Using extensions-compose-experimental also solves the issue.

My questions are:

1. What are the plans for the experimental module? Is it planned to replace extensions-compose?
2. Do you use it in your production apps? Are there any known issues with it compared to extensions-compose?

[Arkadii Ivanov]

Hey! Yeah, movableContenOf hasn't been great. If it works for you, there is another overload of stackAnimation {} not annotated with FaultyDecomposeApi. Otherwise, the new experimental ChildStack is the recommended way to go.

Answering your questions:

1. The extensions-compose-experimental module will be merged into extensions-compose in Decompose 4.0, which is on my radar. Child Stack will replace Children. No timeline for now.
2. We use Child Stack in all our apps, Children function is not used. It's been working great so far.