Does it make sense to use a normal class as a View...

# compose-desktop

[Sudarshan]

Does it make sense to use a normal class as a ViewModel since desktop apps usually don’t need lifecycle awareness? I really like ViewModels as an architectural pattern.

[Pablichjenkov]

I think lifecycle awareness is needed in all platforms.

[Alexander Maryanovsky]

It makes sense if you think you should separate logic from the UI.

[Sudarshan]

Do you think I’ll face any problems if I don’t consider lifecycle awareness?

[Pablichjenkov]

Resource leakage in general. Depends on the type of App obviously. If your App doesn't consume much network in the background you are fine not using it

[Alexander Maryanovsky]

There’s no lifecycle you really need to consider

[Alexander Maryanovsky]

Your viewmodel will not be saved and restored when the app restarts, and as long as it’s alive, your viewmodel is alive.

[Sudarshan]

Oh thanks!

[Arjan van Wieringen]

We use Viewmodels in out Compose HTML app and it works great. It is a great abstraction

[Sudarshan]

What do you mean by HTML app? Sorry I don't have much idea about it. I would like to know what is it?

[Arjan van Wieringen]

The Compose HTML version. Not desktop and not web. Same runtime, different target

[Sudarshan]

Ohh got it!

[Sudarshan]

Thanks