No description
  • Dart 59.9%
  • C++ 18%
  • CMake 14.7%
  • Swift 2.4%
  • Ruby 2.1%
  • Other 2.8%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2025-03-27 10:53:58 -04:00
.github modified: .github/workflows/build.yml 2025-03-24 11:06:50 -04:00
android photo sync notification 2025-03-27 07:28:49 -04:00
assets/images Initial commit 2024-04-12 11:18:24 +01:00
ios photo sync notification 2025-03-27 07:28:49 -04:00
lib remove outline on settings icon to pass test 2025-03-27 10:53:58 -04:00
linux Initial commit 2024-04-12 11:18:24 +01:00
macos Fix auto-upload in Android and iOS, replace photo management package 2024-04-14 13:42:57 +01:00
test Make version number more obvious this is pre-alpha. 2024-04-12 11:32:16 +01:00
web Initial commit 2024-04-12 11:18:24 +01:00
windows Initial commit 2024-04-12 11:18:24 +01:00
.env.sample Initial commit 2024-04-12 11:18:24 +01:00
.gitignore Initial commit 2024-04-12 11:18:24 +01:00
.metadata Initial commit 2024-04-12 11:18:24 +01:00
analysis_options.yaml Initial commit 2024-04-12 11:18:24 +01:00
devtools_options.yaml Auto-upload for Android tested and working, probably for iOS but still needs testing 2024-04-13 13:46:55 +01:00
LICENSE Initial commit 2024-04-12 11:18:24 +01:00
Makefile Include IPA build on make build/ios 2024-04-13 20:09:25 +01:00
pubspec.lock Fix auto-upload in Android and iOS, replace photo management package 2024-04-14 13:42:57 +01:00
pubspec.yaml photo sync notification 2025-03-27 07:28:49 -04:00
README.md Add auto-upload button in settings per account 2024-05-01 08:12:34 +01:00

bewCloud Mobile

This is the Mobile client for bewCloud. It is built with Flutter and relies on the WebDav and REST APIs.

Usernames, passwords, and URLs are stored on the device, with passwords being encrypted.

If you're looking for the desktop sync app, it's at bewcloud-desktop.

Install

Download the appropriate binary from the releases page for your mobile device and run it.

Alternatively, you can build from source!

Caution

I know the key used to encrypt the config passwords in the automatic release builds, and anyone who cares to reverse-engineer the app binaries can too, so you should build your own client instead, with your own key.

Development

You need to have Flutter installed and setup, with flutter doctor passing.

Don't forget to set up your .env file based on .env.sample.

make start # runs the app
make format # formats the code
make test # runs tests

Build from source

Don't forget to check the development section above first!

Note

If you're releasing a new version, update it in pubspec.yaml first.

make build/android # builds the APK for Android
make build/ios # builds the IPA for iOS
make install # installs the app directly on a connected device

Generate icons

If the icons change, just run the following to re-generate them:

dart pub get
dart run flutter_launcher_icons