How martinmimigames/little-file-explorer works
Project Type and Purpose
• This is a single-module Android mobile application (“Little File Explorer”) written in Java/Kotlin under Gradle.
• Purpose: provide a lightweight (<40 KB), fully open-source file-explorer on Android (CRUD file operations, sorting, multi-share, MD5 checksum, theme toggles).
File Structure Analysis
• Top‐level:
• CI/CD: .github/workflows/build.yml, Dockerfile
• Metadata & release: fastlane/metadata/... (F-Droid/App store)
• Gradle configs: build.gradle, settings.gradle, gradle.properties, gradle/wrapper
• app/ module:
• src/main/java/com/martinmimigames/simplefileexplorer/:
– UI layer: MainActivity.java, dialog containers (DeleteConfirmationDialogContainer, DetailsDialogContainer, OpenListDialogContainer), layout subpackage.
– View components: view/ItemView.java.
– Business logic: FileOperation.java, FileOpener.java, PermissionManager.java, Preferences.java.
– FileProvider: abstraction over Android’s file APIs.
• src/main/res/: layouts (activity_main.xml, etc.), drawables, theme definitions.
• Git submodule: mg/utils for cross-cutting utilities.
README Insights
• Android SDK & OpenJDK-17 build (also Dockerfile supplied).
• Uses standard Android patterns (Activities, ContentProviders, Intents).
• Fastlane metadata for multilingual release process.
a. Main Components
1. Presentation Layer (UI)
– MainActivity & XML layouts
– Dialog containers & custom views
2. Business Logic Layer
– FileOperation (copy/paste/delete/rename)
– PermissionManager (runtime storage permissions)
– Preferences (theme, filters)
– FileOpener (Intent dispatch)
3. Data/Storage Layer
– Android File System (internal & SD volumes)
– ContentProvider abstraction (FileProvider.java)
– mg.utils library
4. External Interfaces
– Other Apps (via Intents for “Open with…” & multi-share)
– Android OS services (Storage Manager, Clipboard)
5. CI/CD Pipeline (build & release)
– GitHub Actions → Docker build → Gradle assemble → Fastlane → F-Droid/GitHub Releases
b. Relationships & Data Flows
• User taps UI → MainActivity routes to Business Logic
• Business Logic checks permissions via PermissionManager → requests/storage granted by OS
• FileOperation uses FileProvider → reads/writes file system → updates UI via callbacks
• FileOpener issues Intent → external apps consume file URI
• Preferences persisted in SharedPreferences → influences UI (theme, sort order)
• CI/CD: commits → GitHub Actions triggers Docker container → Gradle build → Fastlane pushes APK to stores
c. Architectural Patterns & Principles
• Layered MVC/MVP approach: Activities as controllers, XML as views, Java classes encapsulate model/business logic
• Clean separation of concerns: UI ↔ business ↔ data
• Use of Android framework components (ContentProvider, Intents)
• Git submodule for modular utility code
d. Key Technologies & Frameworks
• Android SDK (Activities, Content Providers, SharedPreferences, Intents)
• Gradle build system
• Docker for consistent build env
• GitHub Actions for CI
• Fastlane for package metadata & release
• mg.utils (utility submodule)