Skip to content

Design a flow to migrate private browsing users to persistent mode

Design estimate

  • Complexity: TBD
  • Uncertainty: TBD
  • Total: TBD
  • Actual:

Context

Currently, there are 2 possible browsing modes for users:

  • Normal mode: the data is saved in the disk, which means that the browser will remember information even after it is shut down.
  • Private mode: the information is saved on memory, but not in the disk, which means that the browser will remember information within a session, but not after it is shut down.

We want to offer a new mode called Persistent mode, that keeps only specific information (e.g. cookies and passwords) in the disk. These information will be available in the browser in any newer sessions after it is closed; other data, however, will be deleted.

Once shipped, Persistent mode will replace Normal mode [1] and the user will be offered to migrate private browsing users to persistent mode. This migration, however, should be optional and dismissible, as Mullvad Browser will continue to support both modes.

[1] It's possible for power users to still enable Normal mode by editing configuration options directly in about:config, but that's very difficult for regular users + won't be supported at all.

Scope

  • Design a diagram explaining the user migration flow from private browsing to Persistent mode.
  • Design mockups for each step of the flow.

Out of scope

  • Changes to any other flows.

References

Current component for the list of persistent mode: websites with "Allow" status are using persistent mode

Useful links

User flow

TBD

Mockups

TBD

Acceptance criteria

TBD

Edited by Felicia