Is your feature request related to a problem? Please describe.
Maestral's support for multiple accounts is simple: different app instances can use different config files, therefore working completely independently to sync different accounts and folders.
While this model reduces the complexity of the implementation, it does not work well with how some platforms model app behaviour. For example, on macOS, an app is typically expected to only have a single running instance. This is not enforced, but this expectation is apparent throughout the UX, from how login items are managed, to how apps are started by the OS.
Moving to a single instance of Maestral will have number of benefits:
Simplified interaction with the host platform: No need to manage multiple login items, simpler startup and app lifecycle model.
Shared settings can apply to all accounts if it makes sense. This is includes for example how often to check for updates, the log level, bandwidth limits used for syncing, etc.
Define separate classes for common functionality and account-level sync functionality.
Multiple accounts can be managed in the UI instead of requiring CLI usage.
Describe the solution you'd like
Allow full support for multiple accounts by:
Moving shared config items to a "shared" config file and registering all linked accounts there. Individual instances can still have their own config and state files.
Let sync clients share bandwidth between each other instead of working independently.
Define a UI that makes it easy to manage multiple accounts, instead of requiring the CLI to do so.
Describe alternatives you've considered
Keep the status quo.
Is your feature request related to a problem? Please describe. Maestral's support for multiple accounts is simple: different app instances can use different config files, therefore working completely independently to sync different accounts and folders.
While this model reduces the complexity of the implementation, it does not work well with how some platforms model app behaviour. For example, on macOS, an app is typically expected to only have a single running instance. This is not enforced, but this expectation is apparent throughout the UX, from how login items are managed, to how apps are started by the OS.
Moving to a single instance of Maestral will have number of benefits:
Describe the solution you'd like
Allow full support for multiple accounts by:
Describe alternatives you've considered Keep the status quo.