PRIMARY AUDIENCE
Android users who manage several personal or work storage locations, maintain cloud backups, or need a mobile interface to providers such as Google Drive, OneDrive, Dropbox, S3, WebDAV, SFTP, and Nextcloud.
Android cloud storage · Rclone-powered file control
Remote Manager
Android utility
A native Android interface for moving and synchronizing files across many cloud backends.
Interface overview
207 (v1.0.0 APK)Stable release asset downloads
346 across 3 assetsAll release asset downloads
23 stars · 0 forks · 0 open issuesRepository snapshot
v1.0.0 · 16 Aug 2026; v1.1.0-beta posted 19 AugLatest stable
01 / WHY
The problem I chose to solve
The most useful way to understand this project is to start with the friction behind it, then examine the system choices made to address that friction.
People often have files spread across several clouds, SFTP endpoints, and local storage. Doing reliable moves and sync in separate apps can mean repeated context switching, duplicate files, and risk when a file is deleted before its copy has been verified. On mobile, cloud-file tools also need to manage memory, background restrictions, and provider-specific behavior.
Remote Manager wraps the mature Rclone ecosystem in a native Android workflow. Instead of reimplementing dozens of cloud protocols independently, the app uses an Rclone-backed engine and focuses product effort on browsing, move safety, filtering, preview caching, background sync, and approachable controls.
02 / WHO IT SERVES
Where it fits in the real world
A strong implementation has a bounded audience and context. These are the use cases supported by the current design—not a claim that all of them have been validated at scale.
WHAT MAKES IT DISTINCT
- Rclone engine provides breadth across storage backends
- Move tasks use a verified copy-before-delete safety concept
- Background sync can use trigger rules, filters, checksum checks, and Wi-Fi-only conditions
- Rclone Crypt remotes provide a client-side encryption option
- Native ARM64 engine packaging and Android 15 page-size alignment are specifically documented
03 / PRODUCT SURFACE
What the system actually does
An overview of key capabilities and system features.
CAPABILITY / 01
Multi-provider file operations
Browse, upload, download, move, rename, and delete across supported remotes.
CAPABILITY / 02
Safe moves
A move operation includes verification safeguards before deleting the original.
CAPABILITY / 03
Sync rules
Configurable triggers, filters, checksums, and Wi-Fi constraints for recurring work.
CAPABILITY / 04
Thumbnail caching
Disk-backed caching aims to make image browsing lighter on mobile.
CAPABILITY / 05
Encryption
Supports Rclone Crypt remotes for client-side encryption.
CAPABILITY / 06
Native engine and updater
Includes a 64-bit ARM engine and release-check/update flow.
04 / SYSTEM MAP
Architecture & data flow
Architecture and system flow overview.
LAYER / 01
Android interface
Kotlin app manages the remote list, file browser, task UI, previews, and user interaction.
LAYER / 02
Rclone engine
Bundled native ARM64 / Go engine speaks provider-specific protocols.
LAYER / 03
Remote providers
User credentials configure cloud drives, object storage, WebDAV, SFTP, and other remotes.
LAYER / 04
Safety layer
Move verification, sync filters, checksum checks, and optional crypt remotes govern file operations.
IMPLEMENTATION STACK
Kotlin, Android, Rclone, Go 1.24+, native arm64-v8a binaries, Android SDK / NDK, background sync and local thumbnail caching.
KotlinAndroidRcloneGo 1.24+native arm64-v8a binariesAndroid SDK / NDKbackground sync and local thumbnail caching.
05 / ENGINEERING JUDGMENT
Decisions behind the implementation
Engineering choices and design decisions behind the implementation.
- Reuse a proven multi-provider engine rather than writing a separate protocol client for each provider.
- Treat move safety and transfer verification as core product features, not merely convenience options.
- Optimize for mobile memory/background behavior and the current Android binary packaging requirements.
06 / SCOPE & BOUNDARIES
Technical Considerations
Key technical details and system scope considerations.
- Stable v1.0.0 has 207 release-asset downloads; all-release totals count repeat builds and beta binaries. They do not establish active user count.
- Provider support depends on Rclone capability and provider API behavior, quotas, and authentication configuration.
- Client-side encryption only protects data placed in an appropriately configured crypt remote; it does not automatically encrypt every remote by default.
07 / NEXT ITERATION
What I would improve next
The next step is not simply adding features. It is increasing reliability, evidence quality, user trust, and clarity about the boundaries of the system.
NEXT / 01
Create a provider compatibility matrix and report which operations were tested per provider.
NEXT / 02
Publish transfer retry, checksum, duplicate, and partial-failure behavior.
NEXT / 03
Add a clear warning before destructive deletes and a dry-run option for advanced sync tasks.
08 / SOURCES
Sources & Resources
Project repositories and resource links.