Skip to content

[CORE-002] Make accounts a first-class isolated runtime context #172

Description

@veryCrunchy

Roadmap

  • Task ID: CORE-002
  • Priority: P0

Problem

Users must be able to connect multiple Nextcloud accounts, including multiple identities on the same server, without state, cache, background work, or navigation leaking between them.

Acceptance criteria

  • Multiple accounts can be added, switched, reauthenticated, and removed from a native account manager.
  • Server URL plus login identity produces a stable non-personal account key; two users on one server remain distinct.
  • Files, media, DAV, Talk, adaptive apps, caches, sync pairs, notifications, and background work are account-scoped.
  • Account switching restores independent navigation and content state without restarting the app.
  • Background notifications identify and open the correct account context.
  • Removing one account requires confirmation and deletes only that account’s local credentials and state.
  • Tests cover two accounts on one server, accounts on different servers, process restoration, and concurrent background work.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:platformAndroid, desktop, iOS, Windows, macOS, and Linux platform workarea:uxNavigation, accessibility, responsive design, and interactionpriority:P0Required for a trustworthy mobile replacement or prevents data losstype:featureNew product capabilitytype:securityAuthentication, privacy, secrets, or data protection

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions