Can we say that both of the application logic and business logic codes can be represented by service classes in stacked? Does that mean that we should not call the application logic services from the viewmodels (state code)?
Yes, that's usually how it ends up. I wrote a more detailed split of the two in the Stacked docs.
I like to think of it as single responsibility services (application code). This usually wraps a package dependency for http, database, device interactions, etc. These are used by application services that delegate and control business logic.
Can we say that both of the application logic and business logic codes can be represented by service classes in stacked? Does that mean that we should not call the application logic services from the viewmodels (state code)?
Yes, that's usually how it ends up. I wrote a more detailed split of the two in the Stacked docs.
I like to think of it as single responsibility services (application code). This usually wraps a package dependency for http, database, device interactions, etc. These are used by application services that delegate and control business logic.
Here's the link to the stacked doc that goes over that separation: https://stacked.filledstacks.com/docs/in-depth/services
Don't mind the naming, I'm just naming it differently so there's a difference, but it's not important to remember.