Skip to content

Produce the assets necessary to customize the privacy browser

This ticket is intended to track the project's visual design requirements specifically, and is not an exhaustive list for the branding patch (e.g. branding-related tasks like "update the browser name on xyz screens" are not included here). Once we agree on the exact deliverables I'll start spinning these off into separate tickets with timelines for delivery, review and sign-off by the sponsor, and will link them back to the main one to track too.

Branding

  • Get confirmation on the name of the privacy browser
  • Create application icon, and output in platform-specific formats for Linux, MacOS and Windows¹: #3 (closed)
  • Create wordmark and lockup based on the above: #2 (closed)

Installation

  • Create MacOS volume icon [nice to have]²: tor-browser#41332 (closed)
  • Update and customize the mounted volume window for MacOS
  • Select icon for Windows installer³

UI

  • Produce mock-up(s) of browser chrome⁴: tor-browser#41334 (moved)
  • Produce mock-up About window showing application icon and wordmark in situ
  • Visualize the branded start page (e.g. about:tor)⁵
    • [-] Design a new, simplified template for both browsers: tor-browser#41333 (closed)
    • Produce branded version for the privacy browser
  • [-] Visualize the onboarding flow
    • [-] Decide on a template and format for both browsers [internal prerequisite]⁶: tor-browser#41335
    • [-] Reach agreement on content⁷
    • [-] Create icons or illustrations to accompany content, if applicable
    • [-] Produce mock-ups of the full onboarding sequence
  • [-] Time permitting, package all of the above into a Figma prototype [nice to have]

Notes

¹ Mullvad has an existing desktop application. We should take care to ensure the application icon for the browser is visually differentiable from the VPN.

² We don't currently do this for Tor Browser, but it would be nice to have (and lends the DMG a little more authenticity).

³ Tor Browser currently uses the Tor Project (organization) icon, rather than the application icon in this instance. Both browsers should use their respective application icons instead.

⁴ The browser chrome won't be very different from Tor Browser's, save for the omission of Tor Network-specific elements like the circuit display, onion site icons, ".onion site available" pill, etc. However we should check-in on toolbar icons (specifically new identity), and any extensions that may be bundled in the final privacy browser.

⁵ I think a light and simple approach with limited customization (e.g. icon, name, text and colors) would be the most maintainable and user-friendly approach. We could also include our banner format here too.

⁶ Tor Browser's current onboarding template is a port of an older version from Firefox. We should explore alternatives here before deciding on a template, e.g. the practicality of modifying Firefox's current built-in format.

⁷ Firefox and Tor Browser both have very different onboarding flows – the former being pretty light, and the latter rather heavy. The privacy browser may benefit from something in between.

Resources

Logos and light brand guidelines for the sponsor can be found here: https://mullvad.net/en/press/

Edited by morgan