I'm loving all the changes, but I especially keep getting impressed by how configurable you made the shared element transition 👏

Thanks for the clarification @schimke.ee and @camaelon.bsky.social . I'll try remote-creation and using a byte array tomorrow and see how that works.

Looks really good! I tried to test but I'm having some road blocks:
- Client side: I'm not sure how to create the CoreDocument object. I assume we'll simply deserialize it from a JSON response?
- Server side: the `remote-creation-compose` is an AAR and depends on Android classes like Context.

It seems actually that this is a Live Update notification developer.android.com/develop/ui/v...

Compared to a regular LLM answer, it offers:
- Up-to-date data
- More reliable information
- Links to sources for easy verification

@johnoreilly.dev from your experience how do you compare Koog with Google's ADK? Have you also tried other frameworks? What's the best you like so far?

There is actually documentation written about this, I just found out developer.android.com/develop/ui/c...

Ideally, animations wouldn't cause a recomposition as we should prioritize deferring state read, but the case in question can happen.

The only concern I'm aware of is if a composable gets recomposed frequently due to an animation, then the modifiers will be recreated and possibly causing a spike in memory allocation.