Lines Matching refs:layer
26 layer, a domain layer, and a UI layer:
30 The classes in the data layer are `repository` instances. The classes in the
31 domain layer are `interactor` instances. The classes in the UI layer are
33 and "data layer" will be used interchangably (and the same goes for the other
39 #### Repository (data layer)
43 define `Model` objects at this layer so that clients do not have to rely on
46 #### Interactor (domain layer)
48 Here is where we define the business logic and transform the data layer objects
53 #### ViewModel (UI layer)
84 For example, `MobileConnectionsRepository` is a singleton at the data layer that
123 1. In the data layer (`repository` classes), add a new `StateFlow` that listens
145 1. In the domain layer (`interactor` classes), either use this new flow to
146 process values, or just expose the flow as-is for the UI layer.
160 1. In the UI layer (`viewmodel` classes), update the existing flows to process
186 implementation of the data layer is switched to the demo repository via the