Mobile application architecture
The Immich mobile application is a Flutter client that lets a user view and manage media on the device and on an Immich server. It presents server-provided memories as a guided media experience. The app starts local data and network services, builds the interface from routes, and connects user actions to domain services that coordinate media, storage, and device features.
Application entrypoint
The entrypoint prepares shared app services before Flutter draws the first screen. It opens local stores, creates the API service, applies migrations, prepares background support, and places the ready services in a Riverpod scope. If startup fails, the app shows a bootstrap error screen instead of building a partial app.
Startup lifecycle
mobile/lib/main.dart is the application entrypoint. It connects startup work with localization, themes, error logging, downloads, background work, app lifecycle events, and deep links. The bootstrap layer owns shared data setup, including the main database, log database, settings, and server endpoint.
References: mobile/…/main.dart• L52-77 mobile/…/bootstrap.dart• L47-84
Runtime shell
The runtime shell is the MaterialApp.router around the application. It supplies localization and theme state to all pages, watches the router from Riverpod, and sends app lifecycle changes to background work and view-intent handling. The shell is the boundary between Flutter pages and app-wide concerns that remain active while pages change.
References: mobile/…/main.dart• L131-173 mobile/…/main.dart• L191-223 mobile/…/main.dart• L275-305
Navigation and presentation
The presentation layer turns application state into pages, widgets, and user actions. AutoRoute defines the navigation graph, while Riverpod supplies the state and services that pages need. This keeps page composition separate from the rules that load or change media.
Route graph
mobile/lib/routing/router.dart defines routes for login, the main tab shell, media views, collections, settings, backup, sharing, and protected device areas. Guards enforce authentication, prevent duplicate destinations, and require local authentication for the locked folder. Deep links use the same graph, so external navigation does not bypass access rules.
References: mobile/…/router.dart• L86-114 mobile/…/router.dart• L117-199 mobile/…/main.dart• L191-223
Main presentation tabs
The authenticated shell gives the user four main areas: photos, search, albums, and library. It keeps tab navigation separate from page content and adapts navigation to portrait or landscape layout. It also coordinates small cross-page actions such as returning to the top of the photo timeline, clearing search filters, and refreshing albums.
References: mobile/…/tab_shell.page.dart• L20-103 mobile/…/tab_shell.page.dart• L107-134
Feature pages and widgets
Pages express user-facing features, while shared widgets express visual or interaction patterns used by several pages. A page can create a local provider scope when a feature needs state tied to that page, such as a timeline for one local album or one person. The page then supplies context without taking ownership of the data rules.
The person page keeps edits to its displayed person local to the page, then supplies a person-specific timeline service to the shared timeline widget. The remote album page uses the same boundary for route data, provider state, local edit state, and server capability checks. Provider commands perform changes and refresh dependent state after a successful update.
References: mobile/…/library.page.dart• L24-40 mobile/…/library.page.dart• L127-147 mobile/…/local_timeline.page.dart• L10-31 mobile/…/person.page.dart• L75-99 mobile/…/remote_album.page.dart• L188-234 mobile/…/remote_album.page.dart• L275-300 mobile/…/quick_date_picker.dart• L6-21 mobile/…/quick_date_picker.dart• L84-207
Search experience
Search turns a set of text and metadata choices into a paginated media view. The page keeps the current filter and small picker state local, then uses a feature-scoped timeline to present the returned assets through the same browsing and selection model as other media views.
The available search modes depend on server features. The filter set can include context, file name, description, OCR, people, tags, place, camera, date, media type, rating, and display options. A tag selected in the asset viewer can open this page with a tag pre-applied, so asset details and search remain connected without duplicating search rules.
References: mobile/…/search.page.dart• L38-127 mobile/…/search.page.dart• L165-201 mobile/…/search.page.dart• L646-719 mobile/…/search.page.dart• L775-812 mobile/…/search_api.repository.dart• L12-86
Timeline interaction state
The timeline presents ordered media in date buckets and loads the visible asset range as needed. A tap opens the asset viewer. A long press or bucket action builds a selection for later actions. Read-only and locked states can prevent changes, while localized headers expose bulk selection only when the current mode allows it.
References: mobile/…/segment.model.dart• L72-135 mobile/…/segment.model.dart• L229-318 mobile/…/header.widget.dart• L16-121 mobile/…/multiselect.provider.dart• L11-103
Memory presentation
Memory presentation turns filtered server memories into a browsing grid or an immersive story. The list and horizontal memory lane provide entry points. The memory viewer uses vertical paging between memories and horizontal paging between each memory’s assets, with image preloading and video playback handled by existing media boundaries.
Memory state stays local to the viewer while providers and repositories own the data. The viewer tracks the current memory and asset, updates progress and haptic feedback, restores normal system UI when it closes, and can return to the main timeline at the current asset date. Memory titles turn an on-this-day memory into a date or relative year label. Birthday memories use the person name and can add the asset age when that value is valid.
This diagram shows how synced memory data reaches the two presentation modes and then the shared media viewer.
flowchart LR
S[Synced memory records] --> P[Memory provider]
P --> L[Memory list or memory lane]
L --> V[Immersive memory viewer]
V --> A[Remote assets]
A --> I[Image or video presentation]
V --> T[Main timeline at asset date]
References: mobile/…/memory_list.page.dart• L22-59 mobile/…/memory.page.dart• L34-186 mobile/…/memory_lane.widget.dart• L14-31 mobile/…/memory_card.widget.dart• L13-87 mobile/…/memory_card.widget.dart• L89-123 mobile/…/memory_title.widget.dart• L8-59 mobile/…/memory_bottom_info.widget.dart• L12-53
Asset presentation actions
Presentation actions turn a selection into a user-visible operation without making a widget decide how local and server media change. The delete action separates device copies from server assets owned by the current user. It then chooses local cleanup, reversible trash, or confirmed permanent deletion. A merged asset can update both sides, while a local-only asset does not cause a server call.
Tag actions use the same boundary for asset metadata. They appear only when tags are enabled and the selection contains assets that the current user can change. Adding a tag can create it first, then applies the selected tag IDs to the assets. Removing a tag updates the local tag view and reports the result to the user.
The actions also reflect device rules at the presentation boundary. On Android, the delete prompt depends on the device version and local media permission mode. Cancellation stops cleanup. Successful work clears the selection and reports the result through a toast, while only trash offers undo.
References: mobile/…/delete.action.dart• L21-48 mobile/…/delete.action.dart• L67-99 mobile/…/delete.action.dart• L102-163 mobile/…/delete.action.dart• L209-270 mobile/…/tag.action.dart• L11-55 mobile/…/tag.action.dart• L58-111
Image presentation boundary
The image boundary chooses how a media asset reaches Flutter’s image system. An explicit local file takes priority when one is supplied. Otherwise, the boundary prefers a usable device copy when the asset is not edited and settings do not prefer the server. Edited or remote-only assets use the remote copy.
Thumbnail and ThumbHash providers give the UI a fast first image. Full images can move from a thumbnail to a preview and then to the original. Local image identity includes a checksum because a device edit can keep the same asset ID while changing the bytes. Local full images limit oversized preview targets to a safe texture size. Animated media always loads the original stream after its preview because the preview does not provide animation.
The boundary treats cancellation and cache identity as presentation behavior. A request with no listeners is cancelled. Failed final loads evict their cache entry. Remote image identity includes the asset ID, ThumbHash, edit state, and decode choices so a changed source does not reuse the wrong image.
References: mobile/…/image_provider.dart• L15-83 mobile/…/image_provider.dart• L159-229 mobile/…/local_image_provider.dart• L16-66 mobile/…/local_image_provider.dart• L69-105 mobile/…/local_image_provider.dart• L107-203 mobile/…/remote_image_provider.dart• L12-63 mobile/…/remote_image_provider.dart• L66-187 mobile/…/thumb_hash_provider.dart• L7-43
Asset viewing
Asset viewing presents a still image first and adds video playback when the asset has motion or video content. The viewer resolves the latest asset state, tries a local file when the device has one, and falls back to an authenticated server stream when it does not. The same page can therefore show device media, server media, and assets present in both places.
The viewer can open a details sheet over the media. The sheet groups date, owner, description, people, location, technical data, rating, collections, and tags. For an owned remote asset with tags enabled, a tag can open Search with that tag selected, and the same surface can add or remove tags through presentation actions.
The technical details surface identifies the file and shows available size, resolution, camera, lens, exposure, and ISO data. For device media, it can resolve the original filename through the media boundary instead of relying only on the asset record.
Playback and details follow asset-viewer state and the app lifecycle. Only the current item loads after a short delay. Playback pauses when the item or app leaves the active state. The native player reports readiness and position changes back through Riverpod. Casting and route transitions can remove the native view while the image remains as the visual fallback. Dragging the details sheet, zooming, and dismissing the viewer share one gesture boundary so the media view does not change state halfway through a transition. Zooming hides viewer controls, then restores them only when they were visible before the zoom.
References: mobile/…/asset_page.widget.dart• L68-121 mobile/…/asset_page.widget.dart• L299-316 mobile/…/asset_page.widget.dart• L427-537 mobile/…/asset_details.widget.dart• L17-61 mobile/…/technical_details.widget.dart• L27-60 mobile/…/technical_details.widget.dart• L65-96 mobile/…/technical_details.widget.dart• L99-143 mobile/…/tag_details.widget.dart• L20-73 mobile/…/tag_details.widget.dart• L85-177 mobile/…/video_viewer.widget.dart• L104-177 mobile/…/video_viewer.widget.dart• L217-344
Domain and data boundaries
The domain layer describes media behavior in terms that the UI can use. Data and repository layers supply the local database, server API, media library, and file storage needed to perform that behavior. This boundary lets a domain service combine sources without making a page know where each piece of data comes from.
Domain services
Domain services coordinate product actions such as loading an asset, changing remote metadata, managing local media, building timelines, and synchronizing device content. AssetService shows the boundary clearly: it selects local or remote repositories for reads and coordinates API changes with local remote-data updates. It also exposes asset tags through the server repository, so the viewer can request metadata without calling the API directly. The next screen can then see the new state without calling the data sources itself.
References: mobile/…/asset.service.dart• L17-43 mobile/…/asset.service.dart• L92-178 mobile/…/asset.service.dart• L180-219 mobile/…/asset.provider.dart• L8-18
Timeline services
A timeline service is the domain-facing source for ordered media views. A timeline factory creates one for a product context such as the main library, a person, a place, an album, or search. The service exposes grouped buckets and loads asset ranges as the user scrolls.
This design lets one timeline widget serve many pages without knowing how each query is built. A page supplies the context through its provider scope. The timeline service controls range loading, preloading, safe lookup, and reload events, then disposes its work when the owning feature ends.
References: mobile/…/timeline.service.dart• L41-95 mobile/…/timeline.service.dart• L97-143 mobile/…/timeline.service.dart• L145-239 mobile/…/person.page.dart• L77-89
Repository boundaries
Repositories hide the source of data from domain services. Local and remote asset repositories represent cached or device-side media and server media. API repositories represent server commands. Media and storage repositories represent files and the device media library.
The search repository translates one app-level filter into the server’s context or metadata search contract. It carries tags as tag IDs in both forms of server search and keeps pagination and server feature choices outside the page. The memory repository adds a focused read boundary. It joins active memories to visible remote assets and applies the current-day and favorites filters used by memory presentation. This separation supports flows that read local data first, use the server when needed, and update the matching local view after a write.
References: mobile/…/asset.provider.dart• L8-18 mobile/…/asset.service.dart• L17-32 mobile/…/search_api.repository.dart• L7-94 mobile/…/memory.repository.dart• L15-59 mobile/…/asset_media.repository.dart• L29-38
Local and remote data
The app keeps a local SQLite-backed view of media and app data so pages can respond to streams and continue to use device content. Local and remote asset records preserve separate device and server identities. Shared group dates then support one ordered timeline across both sources.
The merged asset view combines server assets with local assets selected for backup when no matching server asset exists. It excludes deleted or non-timeline server assets, excluded local assets, and non-primary stack members. Memories use the same local boundary: sync writes memory records and memory-to-asset links, while memory reads join those records to active timeline assets.
The schema and migrations keep existing data usable as records change. Date values are clamped to SQLite’s supported range, and older out-of-range values are repaired during migration. The shared Store exposes entity-focused access for migrated areas, while a direct database provider remains for areas that still use the older boundary. Both are initialized by the same data controller.
References: mobile/…/data_controller.dart• L12-33 mobile/…/data_controller.dart• L36-78 mobile/…/store.dart• L22-47 mobile/…/database.dart• L63-110 mobile/…/database.dart• L162-182 mobile/…/database.dart• L367-401 mobile/…/merged_asset.drift• L7-91 mobile/…/merged_asset.drift• L93-141 mobile/…/asset.dart• L8-41 mobile/…/asset.dart• L9-63 mobile/…/sync_stream.repository.dart• L643-714 mobile/…/memory.repository.dart• L15-90 mobile/…/datetime_clamp_type.dart• L3-36
Providers and local state
Riverpod is the app’s wiring and state mechanism. Providers construct services from their dependencies, expose streams or async values to the presentation layer, and dispose feature-scoped work when its page leaves the tree.
Provider graph
Infrastructure providers connect domain services to repositories, the database, the API, and platform adapters. Feature providers then expose product-level values such as assets, albums, timelines, memories, or sync status. Pages watch providers. Providers coordinate services. Services use repositories rather than pages calling data sources directly.
References: mobile/…/asset.provider.dart• L8-18 mobile/…/album.provider.dart• L13-38 mobile/…/sync.provider.dart• L13-50 mobile/…/memory_list.page.dart• L22-28 mobile/…/memory_lane.widget.dart• L14-23
Feature-scoped state
Some state belongs only to one feature instance. The timeline provider creates a timeline service from the current user set and disposes it with the provider. Local album and person pages override that provider with a context-specific timeline. Search does the same for its paginated asset stream. This keeps page filters, subscriptions, and load work from leaking into another page.
Selection state follows the same boundary. It tracks selected assets and protected selections. It also reports whether the current set includes local, remote, or merged media so presentation actions can choose a valid operation.
References: mobile/…/timeline.provider.dart• L9-30 mobile/…/local_timeline.page.dart• L18-30 mobile/…/person.page.dart• L77-89 mobile/…/search.page.dart• L775-812 mobile/…/multiselect.provider.dart• L16-103
Settings state
Settings act as shared local state for behavior such as theme and network choices. The settings provider listens for configuration changes and exposes the current app configuration to the UI. Bootstrap initializes the settings repository before the provider graph is used.
References: mobile/…/settings.provider.dart• L5-12 mobile/…/bootstrap.dart• L57-69 mobile/…/main.dart• L280-301
Platform integrations
Platform integrations connect Dart code to capabilities that Flutter cannot own by itself. Providers expose native bridges, repositories translate them into app-level operations, and domain services decide when those operations are part of a user flow.
Native device services
The platform provider exposes native sync, permission, connectivity, image, remote-image, network, and background-worker interfaces. Permission handling is presented as a device-level repository with stable app statuses. Domain and presentation code can then ask for access without depending on Android or iOS API details.
References: mobile/…/platform.provider.dart• L1-28 mobile/…/permission.repository.dart• L9-23 mobile/…/permission.repository.dart• L50-65
Media and file services
The media boundary handles device-library actions and file movement. It can delete or restore device media, find local originals, download remote files for sharing, and remove temporary files after sharing. The domain layer uses this boundary for actions that must work across local originals, remote originals, previews, and edited media.
References: mobile/…/asset_media.repository.dart• L40-77 mobile/…/asset_media.repository.dart• L144-195 mobile/…/asset_media.repository.dart• L314-419
Native media processing
The image bridge gives Flutter one contract for device image data on Android and iOS. Platform adapters load local images, produce pixel or encoded data, support cancellation, and use the shared native core for ThumbHash decoding and selected image-buffer work. The higher-level image providers remain platform-neutral.
This boundary is described in more detail in Native media core.
References: mobile/…/NativeBuffer.kt• L5-29 mobile/…/NativeImage.kt• L5-27 mobile/…/LocalImagesImpl.kt• L76-113 mobile/…/LocalImagesImpl.kt• L128-193 mobile/…/ThumbHash.kt• L3-10 mobile/…/NativeCore.swift• L3-22 mobile/…/LocalImagesImpl.swift• L6-56 mobile/…/LocalImagesImpl.swift• L169-207 mobile/…/Runner-Bridging-Header.h• L1-5
Native application targets
The mobile product includes the Flutter app and platform extensions that support sharing and widgets. Android and iOS build settings keep these targets aligned with the native media bridge and release process. Signing lanes produce development and production variants.
References: mobile/…/build.gradle• L1-8 mobile/…/build.gradle• L30-45 mobile/…/project.pbxproj• L285-306 mobile/…/project.pbxproj• L364-435 mobile/…/Fastfile• L62-95 mobile/…/Fastfile• L98-153
Video playback
Video playback is a platform-backed presentation service. The Flutter viewer supplies either a device file or an authenticated server URL to the native video player. It then maps native playback events to app state. File formats, buffering, app pause and resume, and casting changes stay behind the viewer boundary.
References: mobile/…/video_viewer.widget.dart• L114-173 mobile/…/video_viewer.widget.dart• L89-102 mobile/…/video_viewer.widget.dart• L296-344
Server connection
The API service presents the server as one client surface for authentication, assets, albums, search, sync, sharing, and other server features. It resolves and stores the usable endpoint, applies network settings, and creates the API groups that repositories call. The network layer can therefore change the active server without changing presentation code.
References: mobile/…/api.service.dart• L15-80 mobile/…/api.service.dart• L82-129 mobile/…/api.service.dart• L172-195
Related mobile flows
Three child pages describe product flows that use this architecture in more detail. Read Mobile library synchronization for device and server library state. Read Mobile capture and backup for capture, upload, background work, and backup behavior. Read Native media core for the shared native media processing boundary. For the browser product’s user-facing model, read Web application experience.
Change checklist
When these files or sections are changed, remember to consider these:
- When changing startup order, keep database migration, settings initialization, API endpoint restore, and provider overrides consistent. A mismatch can leave providers with an unconfigured service.
- When adding or moving a guarded route, check its deep-link behavior and whether the guard matches the data protection expected by the destination.
- When changing a repository contract, update the provider that assembles its domain service and the local or remote state refresh that follows a write.
- When changing an asset action, keep local-only, merged, server-owned, trashed, and locked selections mapped to the correct server and device operations.
- When changing tag visibility or tag writes, keep user preferences, ownership checks, tag creation, asset links, search filters, and viewer refreshes aligned.
- When changing search filters, keep the page filter model, feature gates, pagination, tag IDs, server search DTOs, and the search timeline in agreement.
- When changing asset details, preserve the viewer state, asset ownership rules, metadata streams, and navigation back into filtered search.
- When changing viewer zoom or control transitions, preserve the prior control visibility across zoom, fit, pinch, and double-tap state changes.
- When changing image source selection or cache identity, keep local checksums, remote IDs, edited state, decode size, and the local-versus-remote preference aligned with image cache behavior.
- When changing a native bridge, keep the platform provider, generated bridge contract, shared native core, and app-level repository aligned across Android and iOS.
- When changing tab state or feature-scoped providers, preserve disposal and invalidation rules so old timelines, searches, or album streams do not remain active.
- When changing timeline query sources or bucket updates, preserve the range buffer and reload contract used by person, album, search, and main-library pages.
- When changing video source selection, keep local-file fallback, authenticated remote playback, lifecycle pause and resume, and native view disposal aligned.
- When changing local or remote asset fields used by the merged timeline, update both asset records, the merged asset and bucket queries, the schema migration, and the indexes that support lookup.
- When changing stored date values, keep write-time clamping and the one-time repair of older out-of-range values aligned with SQLite date grouping.
- When changing a server-gated album action, keep the server capability version, user-role check, menu visibility, and provider command aligned.
- When changing a sync entity or server version capability, keep request selection, response decoding, event dispatch, local persistence, and acknowledgements aligned.
- When changing memory data, keep memory filters, memory-to-asset links, visible asset rules, title rules, and the list, lane, and viewer entry points consistent.
- When changing the memory viewer, preserve asset-viewer initialization, cross-memory paging, preloading, system UI restoration, and the timeline return action.
Important failure modes
| Trigger | Consequence | Guard |
|---|---|---|
| Local data or log database cannot open | Startup does not build the normal app, or diagnostics cannot persist | Bootstrap catches startup errors and can recreate the log database when SQLite reports corruption |
| Server endpoint is missing or unreachable | API-backed pages cannot load or write server data | The API service resolves the endpoint, checks server availability, and restores the saved endpoint during bootstrap |
| A protected page is reached without the required session or local unlock | The user could see a page outside its access boundary | Route guards enforce authentication, duplicate-route control, and locked-folder authentication |
| Device media permission is denied | Local media discovery, sync, delete, or restore cannot complete | The permission repository maps platform status to app status and exposes request and settings actions |
| Tags are disabled or an asset is not owned by the current user | Tag details and tag changes are hidden | The tag view and tag action check user preferences, asset type, and owner identity before exposing controls |
| A tag is created but asset links or tag search state are not refreshed | The asset can show stale tags, or a tag search can omit the new relation | Tag actions invalidate asset-tag data after writes, and viewer navigation clears and sets the search pre-filter |
| A selected asset has no valid local or owned remote operation | The delete action is hidden or performs no operation | Selection state filters local IDs and remote assets owned by the current user before it creates the action |
| A search filter is sent with the wrong server search form | Results do not match the selected context, metadata, or tag filters | The search repository selects the context or metadata contract and maps tags, media type, display, and page values into it |
| A device image changes while its asset ID stays the same | Flutter can reuse an older cached image | Local image identity includes the device checksum |
| A remote image request loses its listener | Work can continue after the widget no longer needs the image | Image providers cancel the loader when the last listener is removed |
| A native image bridge or shared native core is missing from a platform build | Local image loads or ThumbHash backdrops fail even when the asset exists | Android and iOS build targets include the matching bridge and native core |
| A timeline bucket count changes while a page uses an old range | The page can show stale positions or request an invalid asset range | Timeline reloads its buffer under one lock and emits a reload event only after the count and buffer agree |
| An asset is marked local but its device record or file is missing | Video playback cannot use the device copy | The viewer checks the local record and file, then falls back to the server copy for remote assets |
| A remote share download or temporary-file step fails | The share action returns no usable file and may leave temporary data | The media repository checks task status, cancels work, logs failures, and cleans temporary files |
| A local or remote asset schema change skips its migration or merged-query update | Existing data can fail to open, or the main timeline can omit or duplicate assets | The database version, migration steps, asset indexes, and merged asset and bucket queries change together |
| A date outside SQLite’s supported range reaches a date query | Timeline grouping or sync-related queries can fail or produce invalid order | The date type clamps new values and the schema migration repairs older invalid values |
| An album edit is shown for a server that does not support it | The update can fail after the user submits the form | The page checks the server capability and user role before exposing the edit action |
| A sync capability, decoder, event handler, or local writer is out of step | A server entity can be skipped, rejected, or acknowledged without reaching local state | Server capability checks and the sync request, parser, service, and repository mappings change as one contract |
| A memory has no active timeline asset or its link is stale | The memory is omitted from the list or the viewer has no usable first page | Memory queries require active timeline assets, and sync updates memory links with the memory records |
| A memory viewer opens without a current asset or leaves immersive mode uncleared | The first media page can be blank, or system controls can remain hidden after exit | Entry points set asset-viewer state, and the viewer restores edge-to-edge UI on close |
| Viewer zoom state restores controls without preserving their prior visibility | Controls can appear unexpectedly after a user had hidden them | Asset-page scale handling records the pre-zoom state and the control transition tests cover zoom, fit, pinch, and double-tap paths |
Key files
| File | Why to read it |
|---|---|
mobile/lib/main.dart | Shows application startup, the Flutter runtime shell, lifecycle handling, localization, themes, and deep-link entry. |
mobile/lib/utils/bootstrap.dart | Shows how the API service, databases, settings, and logging become ready before providers are built. |
mobile/lib/routing/router.dart | Shows the route graph and access boundaries around major user flows. |
mobile/lib/pages/common/tab_shell.page.dart | Shows the main authenticated navigation model and tab-level state changes. |
mobile/lib/presentation/pages/search/search.page.dart | Shows local search filters, server feature gates, paginated results, and the search timeline. |
mobile/lib/infrastructure/repositories/search_api.repository.dart | Shows how app search filters become server search requests. |
mobile/lib/presentation/pages/memory_list.page.dart | Shows the memory collection entry point and route hand-off to the viewer. |
mobile/lib/presentation/pages/memory.page.dart | Shows the immersive memory flow, local viewer state, paging, and timeline return. |
mobile/lib/presentation/widgets/memory/memory_card.widget.dart | Shows how memory assets share image and native video presentation. |
mobile/lib/presentation/widgets/memory/memory_title.widget.dart | Shows how memory type, person name, and asset dates become user-facing titles. |
mobile/lib/presentation/actions/delete.action.dart | Shows how presentation actions map mixed local and remote selections to trash, permanent deletion, or device cleanup. |
mobile/lib/presentation/actions/tag.action.dart | Shows how tag controls check selection and preferences, then create, apply, or remove asset tags. |
mobile/lib/presentation/widgets/timeline/fixed/segment.model.dart | Shows how visible timeline ranges become rows, asset tiles, selection, and viewer entry. |
mobile/lib/presentation/widgets/images/image_provider.dart | Shows how presentation chooses local or remote media and exposes cancellable image loading to Flutter. |
mobile/lib/presentation/widgets/images/local_image_provider.dart | Shows local thumbnail, preview, original, animation, checksum, and safe-size behavior. |
mobile/lib/presentation/widgets/images/remote_image_provider.dart | Shows remote thumbnail, preview, original, animation, and cache-key behavior. |
mobile/lib/presentation/widgets/asset_viewer/asset_page.widget.dart | Shows media viewing, details-sheet interaction, stack selection, zoom, and viewer lifecycle state. |
mobile/lib/presentation/widgets/asset_viewer/asset_details/technical_details.widget.dart | Shows how the details surface presents file identity and available camera or lens metadata for local and remote assets. |
mobile/lib/presentation/widgets/asset_viewer/asset_details.widget.dart | Shows how the viewer groups asset metadata and user actions in its details surface. |
mobile/lib/presentation/widgets/asset_viewer/asset_details/tag_details.widget.dart | Shows tag visibility, tag navigation into search, and add or remove tag controls. |
mobile/lib/presentation/widgets/asset_viewer/video_viewer.widget.dart | Shows how asset viewing chooses local or remote playback and follows app and route lifecycle state. |
mobile/test/presentation/widgets/asset_viewer/asset_page_controls_test.dart | Shows the viewer contract that control visibility survives each zoom state transition. |
mobile/lib/presentation/pages/remote_album.page.dart | Shows feature-scoped album timelines, local page state, role checks, server capability checks, and album actions. |
mobile/lib/domain/services/asset.service.dart | Shows how a domain service joins local data, remote data, API commands, asset metadata, and media operations. |
mobile/lib/domain/services/timeline.service.dart | Shows how product-specific timeline queries become grouped, buffered asset ranges. |
mobile/lib/data/data_controller.dart | Shows the shared local data boundary and the separate logging store. |
mobile/lib/data/store.dart | Shows the entity-oriented store boundary and the transition from direct database access. |
mobile/lib/data/db/main/database.dart | Shows the local schema, migration path, stream updates, and SQLite data safeguards. |
mobile/lib/data/db/main/query/merged_asset.drift | Shows how local backup candidates and server assets become one timeline view. |
mobile/lib/providers/infrastructure/asset.provider.dart | Shows provider wiring from repositories into a domain service. |
mobile/lib/providers/infrastructure/sync.provider.dart | Shows how synchronization services combine local repositories, server access, cancellation, and native APIs. |
mobile/lib/infrastructure/repositories/memory.repository.dart | Shows how memory records and linked remote assets become filtered presentation data. |
mobile/lib/repositories/asset_media.repository.dart | Shows the boundary between app media actions and the device file or media system. |
mobile/lib/services/api.service.dart | Shows server endpoint resolution and the shared API surface used by repositories. |
| mobile/…/LocalImagesImpl.kt | Shows the Android side of the shared local-image contract and cancellable device-media access. |
| mobile/…/LocalImagesImpl.swift | Shows the iOS side of the same local-image contract and device-media access. |
| mobile/…/NativeCore.swift | Shows how iOS reaches the shared native media core. |
| mobile/…/NativeImage.kt | Shows Android native image operations exposed to the local-image adapter. |
| mobile/…/Runner-Bridging-Header.h | Shows the iOS bridge declaration for the shared native core. |
| mobile/…/build.gradle | Shows the Android application target and native build dependencies. |
mobile/ios/Runner.xcodeproj/project.pbxproj | Shows the iOS app, share extension, widget extension, and native source targets. |
mobile/ios/fastlane/Fastfile | Shows how iOS variants are signed, built, and distributed. |