What is the reason paused state stands for?

[vulpeszerda]

While checking the version changelog, I found that the following changes are included in version 0.21.0:

New: Add RecordLifecycle and LocalRecordLifecycle composition local, allowing UIs and presenters to observe when they are 'active'. Currently, a record is considered 'active' when it is the top record on the back stack.
...
Behaviour Change: Presenters are now 'paused' when inactive and replay their last emitted CircuitUiState when they are not active. Presenters can opt-out of this behavior by implementing NonPausablePresenter.

As far as I understand, a circuit's presenter and UI are always disposed of when they are not the top record on the back stack.
So, why is the term 'inactive' state necessary for the presenter/UI?

The only situation I can imagine where a presenter/UI is added to the compose node and is 'inactive' is during screen transitions.
And if this is the only case, then in normal usecase, the 'inactive' state or 'RecordLifecycle' would not be used.

I am curious if I understand this correctly.

[ZacSweers]

It essentially just means we cache the last emitted state and don't resume until it's the top of the stack. Previously, we had performance issues during nav decorations because both records were active at the same time during the animation. With the new approach, we just show the previously cached value rather than restart.

[vulpeszerda]

Now I fully understood :) thank you!