Define high-level UX for persistent mode

Design estimate

• Complexity: medium (3 days)
• Uncertainty: extreme (5.0)
• Total: 15 days (90 hours)
• 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 data 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**¹. Although it is the same as Private mode in essence, Persistent mode allows users to add websites to a list of exceptions. This list consists of websites whose data² will be saved in the disk, being remembered by the browser even across sessions.

This list of exceptions won't be taken into account by the browser on Private mode, and can only be edited if Persistent mode is on.

Once shipped, Persistent mode will replace Normal mode³.

¹ The names of the modes need more thoughts.

² Cookies, passwords and browsing history.

³ 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

• Draw user flows that will guide the UI design process;
• Design low-fi wireframes to validate user flows.

Out of scope

• High fidelity mockups