Convert Figma logo to code with AI

owncloud logoandroid

:phone: The ownCloud Android App

4,164
3,080
4,164
205
View on GitHub

Top Related Projects

cryptomator's avatar

android

1,202

Cryptomator for Android

syncthing's avatar

syncthing-android

4,295

Wrapper of syncthing for Android.

Quick Overview

ownCloud Android is the official Android application for the ownCloud file synchronization and sharing platform. It allows users to access, manage, and sync their files stored on ownCloud servers directly from their Android devices. The app provides a seamless mobile experience for ownCloud users, enabling them to stay connected to their data on the go.

Pros

  • Open-source and community-driven development
  • Seamless integration with ownCloud servers
  • Regular updates and active maintenance
  • Support for multiple accounts and server instances

Cons

  • Some users report occasional sync issues
  • Limited offline functionality compared to desktop clients
  • User interface may feel dated compared to some modern cloud storage apps
  • Performance can be slow with large file collections

Getting Started

To get started with ownCloud Android:

  1. Download the app from the Google Play Store or F-Droid.
  2. Open the app and tap "Add account."
  3. Enter your ownCloud server URL, username, and password.
  4. Grant necessary permissions when prompted.
  5. Your files will start syncing, and you can now browse and manage your ownCloud content.

For developers interested in contributing:

  1. Fork the repository on GitHub.
  2. Clone your fork: git clone https://github.com/your-username/android.git
  3. Set up the development environment following the instructions in the README.
  4. Make changes and submit pull requests for review.

Competitor Comparisons

cryptomator logo

android

1,202

Cryptomator for Android

Pros of Cryptomator

  • Focuses on client-side encryption, providing enhanced security for cloud storage
  • Supports multiple cloud storage providers, offering more flexibility
  • Open-source nature allows for community audits and contributions

Cons of Cryptomator

  • More complex setup process compared to OwnCloud
  • Limited built-in file management features
  • Smaller user base and community support

Code Comparison

Cryptomator (Kotlin):

override fun onCreateView(inflater: LayoutInflater, container: ViewGroup?, savedInstanceState: Bundle?): View? {
    _binding = FragmentUnlockVaultBinding.inflate(inflater, container, false)
    return binding.root
}

OwnCloud (Java):

@Override
public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) {
    View view = inflater.inflate(R.layout.fragment_sync_list, container, false);
    ButterKnife.bind(this, view);
    return view;
}

Both repositories use similar Android development practices, but Cryptomator utilizes Kotlin while OwnCloud primarily uses Java. Cryptomator's code tends to be more concise due to Kotlin's features, while OwnCloud's Java code is more verbose but potentially more familiar to developers experienced with traditional Android development.

syncthing logo

syncthing-android

4,295

Wrapper of syncthing for Android.

Pros of Syncthing-Android

  • Decentralized and peer-to-peer, offering better privacy and control
  • Open-source with a strong community-driven development
  • Supports selective sync for individual folders

Cons of Syncthing-Android

  • Steeper learning curve for non-technical users
  • Lacks built-in file editing and viewing capabilities
  • No official web interface for remote access

Code Comparison

Syncthing-Android (Kotlin):

override fun onCreateView(inflater: LayoutInflater, container: ViewGroup?, savedInstanceState: Bundle?): View? {
    binding = FragmentDeviceListBinding.inflate(inflater, container, false)
    binding.list.layoutManager = LinearLayoutManager(context)
    binding.list.adapter = adapter
    return binding.root
}

ownCloud Android (Java):

@Override
public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) {
    View v = inflater.inflate(R.layout.list_fragment, null);
    listView = v.findViewById(R.id.list_root);
    listView.setAdapter(mAdapter);
    return v;
}

Both projects use similar patterns for creating views, but Syncthing-Android utilizes Kotlin and view binding, while ownCloud Android uses Java and traditional findViewById. Syncthing-Android's code appears more concise and modern due to Kotlin's features and the use of view binding.

Convert Figma logo designs to code with AI

Visual Copilot

Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.

Try Visual Copilot

README

ownCloud Android App

License ownCloud OSPO

Android Unit Tests Android Instrumented Data Tests Detekt Conventional Commits

The ownCloud Android app enables users to access, sync, and share files stored on their ownCloud server directly from Android devices. Built with Kotlin, it supports ownCloud Infinite Scale (oCIS) and ownCloud Classic servers, featuring file browsing, photo galleries, Spaces, sharing, passcode lock, and biometric authentication. The app is available on:

Part of Mobile (Android)

This is the official ownCloud Android app, the primary mobile client for Android users. It connects to both ownCloud Infinite Scale (oCIS) and ownCloud Classic.

Getting Started

  1. Read SETUP.md for development environment setup
  2. Fork the repository and clone it locally
  3. Open the project in Android Studio
  4. Build and run using ./gradlew assembleDebug

Beta Testing

  • Play Store: Download the app from Play Store, scroll down to the beta section, and tap "I'm in"
  • F-Droid: Open the ownCloud tab in F-Droid and download the latest beta version

Documentation

Community & Support

Star this repo and Watch for release notifications!

Contributing

We welcome contributions! Please read the Contributing Guidelines and our Code of Conduct before getting started.

Workflow

  • Rebase Early, Rebase Often! We use a rebase workflow. Always rebase on the target branch before submitting a PR.
  • Dependabot: Automated dependency updates are managed via Dependabot. Review and merge dependency PRs promptly.
  • Signed Commits: All commits must be PGP/GPG signed. See GitHub's signing guide.
  • DCO Sign-off: Every commit must carry a Signed-off-by line: 
    git commit -s -S -m "your commit message"
  • GitHub Actions Policy: Workflows may only use actions that are (a) owned by owncloud, (b) created by GitHub (actions/*), or (c) verified in the GitHub Marketplace.

Translations

Help translate this project on Transifex: https://explore.transifex.com/owncloud-org/owncloud-android/

Please submit translations via Transifex -- do not open pull requests for translation changes.

Security

Do not open a public GitHub issue for security vulnerabilities.

Report vulnerabilities at https://security.owncloud.com -- see SECURITY.md.

Bug bounty: YesWeHack ownCloud Program

License

This project is licensed under the GPL-2.0.

About the ownCloud OSPO

The Kiteworks Open Source Program Office, operating under the ownCloud brand, launched on May 5, 2026, to steward the open source ecosystem around ownCloud's products. The OSPO ensures transparent governance, license compliance, community health, and sustainable collaboration between the open source community and Kiteworks, which acquired ownCloud in 2023.

For questions about the OSPO or licensing, contact ospo@kiteworks.com.

License Migration to Apache 2.0

The OSPO is driving a strategic relicensing of ownCloud repositories toward the Apache License 2.0, following the Apache Software Foundation's third-party license policy.

Individual repositories will migrate as their audit is completed. The LICENSE file in each repo reflects its current license status (not the target).

Current license: GPL-2.0 (Category X per Apache policy -- cannot be included in Apache-2.0 works).

Migration prerequisites for this repository:

  • CLA/DCO coverage: All past contributors must have signed agreements permitting relicensing
  • Copyleft dependency audit: All GPL dependencies must be replaced or isolated
  • KDE heritage review: Any code with KDE-era copyrights requires legal analysis
  • Complete relicensing: GPL-2.0 is a strong copyleft license; migration requires full relicensing of all files