[FR]: Avoid subcomposition on SparkImage when is not necessary

[danielriverolosa]

🕵️ Is there an existing issue for this?

• I have searched the existing issues

Describe the problem

SparkImage uses Coil library inside to display images, specifically the composable SubcomposeAsyncImage, which in itself, depending on a SizeResolver, uses a BoxWithConstraints layout. It can be seen here.
Subcomposition can be avoided building the ImageRequest yourself on the model and applying original size, but it is not documented anywhere in SparkImage and may lead to incorrect uses.

Official Coil documentation recommend not to use this component (SubcomposeAsyncImage) in listings or this kind of similar cases due to performance issues.

Describe the solution

Perhaps it is appropriate to use the component recommended by the documentation in each case or, on the other hand, document correctly what should be the building of the model to avoid the use of the subcomposition and its performance problems.

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct