IssueTracker

the older rows getting recomposed while the new lazy row is not. each new item that added to the list causes to each row (expect the new one) to recompose, while some of them getting skipped some components are not.

The main property of Lazy layouts is that it will only compose the items that are in the view. If they are not in the view, they won't be composed. Once you scroll to those items, then they will get composed/re-composed. If you want to compose all the items for whatever reason, consider using Row or Column instead (remember this will impact performance a lot if you have a lot of items within the row/columns).

Also and very important unhealthy behavior that you can see in this video you can also see that using 'androidx.tv.material3.Card' library for Card, each focus movement causing recomposition to the card the focus has left and a composition for the incoming card. also by disabling the cardScale the behavior stays the same (can be seen in "recomposition on focus tv").

This is expected behaviour. Card scale is not the only property listening to the focus events. There are other properties as well, that are listening to focus events like shape, colors, border. Why do you think this is "unhealthy" behaviour?

On a side note, TvLazyRow, TvLazyColumn, TvLazyHorizontalGrid and TvLazyVerticalGrid have been deprecated from androidx.tv.foundation. Kindly refer to b/348896032 for the migration steps.

I expect focus events to trigger only the layout and drawing processes, or just the drawing process, as long as the composable is not set to listen to these events.

The key advantage of most TV components is their declarative style application, based on focus or click events. This eliminates the need for developers to manually listen to and update styles. Internally, we handle this by listening to these events and dynamically swapping styles, which requires the composition phase.

Currently, we have no plans to investigate removing the recomposition step for interactive components and their descendants on focus/press events. The potential performance benefits remain unclear, especially since interactive components are typically located near the leaf nodes of the component tree.

During development, you may notice performance issues with the debug app on actual TV devices. We highly recommend creating and applying baseline profiles, which can significantly improve app performance, even on lower-end devices.

I think there was a misunderstanding. You described the expected behavior, but that is not what the layout inspector is showing in the attached video composition error TV In the attached video, I append one list for each time interval. I expect that only the newly created list will be detected as a composition by the layout inspector. However, the actual behavior shows that each time I append a list, the most recent list is not undergoing composition, while all the previously appended lists are undergoing recomposition.

I understand, thank you for clarifying. Since lazy layouts are no longer part of the TV library, I recommend filing this issue under the Compose foundation. My apologies, I should have informed you of this sooner.

There are still a lot of improvements to do in the compose framework to be able to use it on low-end tv market devices. The customer don't have Nvidia Shield or emulator. The global performances improve those last months, but it's way too slow, 2 years to get the 1.0.0 version. Is it possible to get more man power on this performance topic or quality developer ?

Sorry ma..@gmail.com to hijack your issue :-)