Multi-provider storage
Google Drive, OneDrive, Dropbox, Nextcloud, S3, WebDAV, SFTP and other providers through the rclone ecosystem.
An Android client that brings serious multi-provider cloud file operations, synchronization and encryption into a native mobile workflow.
A lightweight Android cloud-storage manager powered by rclone. The repository describes multi-provider file operations, safe move tasks, background synchronization, thumbnail caching, optional client-side encryption, native ARM64 performance considerations and release updating.
Remote Manager demonstrates Neubofy’s ability to integrate a mature systems toolchain into a user-facing product. Instead of reinventing cloud-storage protocols one provider at a time, the project uses rclone as a capability engine and builds mobile UX, task orchestration, filtering, integrity checks and lifecycle management around it.
Google Drive, OneDrive, Dropbox, Nextcloud, S3, WebDAV, SFTP and other providers through the rclone ecosystem.
Browse, upload, download, move, rename and delete remote content.
Copy-then-delete behavior with verification intended to avoid destructive operations after failed transfers.
Custom triggers, filters, checksum verification and Wi-Fi-only rules.
Memory-conscious thumbnail loading and persistent local thumbnail caching.
Rclone Crypt support for encrypted remote storage workflows.
The project documents a 64-bit ARM engine and Android 15+ 16 KB page-size alignment considerations.
The app includes GitHub-release update checking and installation support.
The manifest and repository show a real Android application with foreground data-sync services, workers, providers, boot receivers, sharing intents and storage access. This is a systems-integration project rather than a simple CRUD cloud client.
Android • Kotlin/Gradle • rclone engine • background data-sync services • local caching • checksum/integrity workflows • encrypted remotes • GitHub Releases
Remote Manager depends heavily on the behavior and compatibility of the underlying rclone ecosystem and the individual cloud providers. Provider limits, authentication flows and Android storage rules remain environmental constraints.