How cryptomator/android works
Project type and purpose
• This is a native Android client application (“Cryptomator for Android”) providing transparent client-side encryption of files stored in various cloud services or local storage.
• It uses a multi-module Gradle project structured around Clean Architecture (presentation, domain, data, util layers), plus generator modules for build-time code generation and a buildsystem module for Docker-based reproducible builds.
File structure
• Top-level modules:
• presentation: UI layer (Activities, Fragments, Presenters, DI modules)
• domain: business logic (UseCases, Entities, Repository interfaces)
• data: data layer (Repository implementations, CloudContentRepositoryFactories, DB, crypto, local storage, network clients)
• util: shared utilities (cryptography helpers, file/cache utils, logging)
• generator & generator-api: annotation processors and supporting API for auto-generating boilerplate
• buildsystem: Dockerfile and scripts for reproducible builds
• fastlane, playstore, fdroid, lite, apkStorePlaystore: CI/CD and distribution metadata
• Configuration files: build.gradle in each module, settings.gradle, Gemfile, .github workflows, Docker config.
README for additional insights
• Confirms multi-flavor Android build targeting Google Play, F-Droid, Accrescent, etc.
• Mentions dependencies (JDK17, Gradle), reproducible builds via Docker.