Skip to content

Improve disconnect UX #1124

@raucao

Description

@raucao

From litewrite/litewrite#293

I see two issues there:

  1. When there's unsynced local data present, the library should warn the user about it when a disconnect is attempted, with the option for the user to cancel the disconnect and re-auth the app again (or get online and sync data, depending on what's the reason).
  2. It might make sense to give the user the choice to keep all synced local data when disconnecting, i.e. put it back in anonymous local storage. It's certainly debatable if the benefits of forcing this choice on every disconnect outweigh the drawbacks in UX. So let's discuss. :)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions