What is the proper architecture for Compose Web?

So, I am an android developer without much webdev experience, and also don’t really have much regular Compose experience either (our current project started before Compose got stable), but now I am making my personal project – a Chrome extension – so I’m learning Compose Web right now. And my main problem, is that i don’t quite understand, what is the proper structure of a project. Like, data-domain-presentation? Repository is Data, and Composables are Presentation, but what is Domain? Like, source of data and business logic, connection to data layer and all that.

Is there any analog for ViewModels in webdev? Or, like, should I just have DI-injected (or even singleton object) class without any lifecycle or anything? Or something else?

submitted by /u/L_James
[link] [comments]