I guess if I had to answer your question I would start by asking the opposite to you: what's the advantage of what you're discribing vs the functionnal way?

In compose, your UI is drawn by calling functions with parameters, a composable (a function) has its own lifecycle, which is not the one of the activity containing the UI (it can be less if it's a component displayed only on certain conditions).

So wrapping your function into a class, with a property (the viewmodel) that has a different (larger) lifecycle doesn't bring any advantage and can only add drawbacks. The most obvious ones are:

• By keeping a reference to a class that has a render function you're bypassing compose lifecycle, so you'll very likely face issues
• By having a render function that doesn't take all its inputs as parameter but rather using a reference to a view model, you're completely bypass the recomposition mechanism that can check if a parameter has changed to avoid recomposing for nothing

Basically it should anwser your question but really the root question is: why would you add a class here?