immich/mobile/lib/domain
Peter Ombodi f7e5288173 rework trashed assets handling
- add new table trashed_local_asset
- mirror trashed assets data in trashed_local_asset.
- compute checksums for assets trashed out-of-app.
- restore assets present in trashed_local_asset and non-trashed in remote_asset.
- simplify moving-to-trash logic based on remote_asset events.
2025-09-18 13:55:56 +03:00
..
interfaces refactor(mobile): interfaces refactor (#19415) 2025-06-23 11:27:44 -05:00
models rework trashed assets handling 2025-09-18 13:55:56 +03:00
services rework trashed assets handling 2025-09-18 13:55:56 +03:00
utils fix: android crash on app pause (#21768) 2025-09-10 17:15:42 +00:00
README.md refactor(mobile): split store into repo and service (#16199) 2025-02-19 13:05:24 -06:00

Domain Layer

This directory contains the domain layer of Immich. The domain layer is responsible for the business logic of the app. It includes interfaces for repositories, models, services and utilities. This layer should never depend on anything from the presentation layer or from the infrastructure layer.

Structure

  • Interfaces: These are the interfaces that define the contract for data operations.
  • Models: These are the core data classes that represent the business models.
  • Services: These are the classes that contain the business logic and interact with the repositories.
  • Utils: These are utility classes and functions that provide common functionalities used across the domain layer.
domain/
├── interfaces/
│   └── user.interface.dart
├── models/
│   └── user.model.dart
├── services/
│   └── user.service.dart
└── utils/
    └── date_utils.dart

Usage

The domain layer provides services that implement the business logic by consuming repositories through dependency injection. Services are exposed through Riverpod providers in the root providers directory.

// In presentation layer
final userService = ref.watch(userServiceProvider);
final user = await userService.getUser(userId);

The presentation layer should never directly use repositories, but instead interact with the domain layer through services.