immich/mobile/lib/domain
Santo Shakil 35c2a90fca
fix(mobile): video playback controls dead for backed up videos opened from search (#30587)
* key video player state by asset id instead of hero tag

* expose id on BaseAsset instead of a separate playerKey
2026-08-09 23:54:55 +06:00
..
models fix(mobile): video playback controls dead for backed up videos opened from search (#30587) 2026-08-09 23:54:55 +06:00
services refactor: gallery permission notifier (#30477) 2026-08-08 11:14:14 -05:00
utils fix(mobile): run one more sync round when a request arrives mid sync (#30478) 2026-08-04 14:59:19 +00:00
README.md

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.