UX issueshttps://gitlab.torproject.org/groups/tpo/ux/-/issues2023-12-08T21:32:47Zhttps://gitlab.torproject.org/tpo/ux/team/-/issues/92Project idea: Update the Tor Project's brand mark2023-12-08T21:32:47ZdonutsProject idea: Update the Tor Project's brand markThe current Tor logo is iconic, but the onion is a little dated, and more importantly it displays poorly at small sizes. This is unfortunate, because in contexts where a smaller icon is required (like our websites' favicon, for example) ...The current Tor logo is iconic, but the onion is a little dated, and more importantly it displays poorly at small sizes. This is unfortunate, because in contexts where a smaller icon is required (like our websites' favicon, for example) the current practice is to use the onion on its own.
https://styleguide.torproject.org/brand-assets/
However we can update the onion to work better in small sizes while still preserving what makes the Tor logo so recognizable. It would also be a good opportunity to update and simplify the colors used in the logo to match those we're developing for the new style guide.design-dot MVPhttps://gitlab.torproject.org/tpo/ux/team/-/issues/91Project idea: Dedicated release notes and lo-fi public roadmaps2023-12-09T03:31:11ZdonutsProject idea: Dedicated release notes and lo-fi public roadmapsAt present, release notes for our software are posted either to the blog, the forum or both. We could improve on this with a dedicated feed for release notes separate from the blog, that uses a custom layout to improve the formatting for...At present, release notes for our software are posted either to the blog, the forum or both. We could improve on this with a dedicated feed for release notes separate from the blog, that uses a custom layout to improve the formatting for release posts.
Some inspiration can be drawn from:
- [Firefox](https://www.mozilla.org/en-US/firefox/releases/): Specifically the way they split up the release notes into different sections, like "New", "Fixed" etc.
- [DuckDuckGo](https://duckduckgo.com/updates): While these aren't release notes, it's a nice example of how updates ti multiple pieces of software can be combined to create a sense of momentum across the org.
- [Linear](https://linear.app/changelog): These are just really nicely designed.
Major releases that include more of a narrative could still justify an accompanying blog post, however.
I think it would also be great to provide a general sense for what's coming in the near future too in a sort of lo-fi public roadmap, that doesn't promise specific windows for delivery.https://gitlab.torproject.org/tpo/ux/team/-/issues/90Project idea: Feature comparison page2023-12-08T19:07:35ZdonutsProject idea: Feature comparison pageAfter the VPN is released, a feature comparison page for torproject.org/download would help users to choose the right app. It could also be expanded to include other apps. Some of the points of comparison it covers could be:
- App type
...After the VPN is released, a feature comparison page for torproject.org/download would help users to choose the right app. It could also be expanded to include other apps. Some of the points of comparison it covers could be:
- App type
- Platform
- Connection type
- Fingerprinting protections
- License
- Developer
- Distributor
I imagine at minimum it should feature Tor Browser, Mullvad Browser and the Tor VPN—but it could also be expanded to include trusted Tor-powered apps created by our community partners on a second tab, e.g. Tail, Orbot, Onion Browser, Onionshare and others.https://gitlab.torproject.org/tpo/ux/team/-/issues/89Project idea: Write a user research handbook2024-01-29T19:09:34ZdonutsProject idea: Write a user research handbookOnboarding partners who have little to no experience conducting user research simply isn't possible in a single session, and the existing material we have on the [community portal](https://community.torproject.org/user-research/guideline...Onboarding partners who have little to no experience conducting user research simply isn't possible in a single session, and the existing material we have on the [community portal](https://community.torproject.org/user-research/guidelines/) isn't sufficient either. Instead, I'd like to create a longer version of this content called the user research handbook, with graphic support provided by our designers, including topics like:
- Our methodology (i.e. the processes we follow)
- Research methods (i.e. the types of research we employ)
- Best practices (previously dubbed the privacy playbook)
- Assessing risk (i.e. our risk assessment procedure)
- Recruitment
- Reporting
This content may then be hosted on the future design-dot website (see [UX / milestone#17](https://gitlab.torproject.org/groups/tpo/ux/-/milestones/17)).Sponsor 9 - Phase 7 - Usability and Community Intervention on Support for Democracy and Human Rightshttps://gitlab.torproject.org/tpo/ux/team/-/issues/88Project idea: Create an "insights" dashboard for user research2023-12-08T18:46:19ZdonutsProject idea: Create an "insights" dashboard for user researchAt present, the results of our user research are scattered across several different blog posts and reports (themselves often a mix of public and private, and frequently published on completely different platforms). In addition to providi...At present, the results of our user research are scattered across several different blog posts and reports (themselves often a mix of public and private, and frequently published on completely different platforms). In addition to providing a single home for our user research reports, it would be great to create a simple dashboard summarizing findings that we still consider current, including:
- Snapshot of important metrics (linking to metrics.torproject.org)
- Recent qualitative findings
- Locations and participant numbers
- Top pain points
- Questions participants frequently ask
- A link to submit a question to the UX team, that isn't answered in our current data
The new style guide would be one potential home for this page.https://gitlab.torproject.org/tpo/ux/team/-/issues/87Project idea: Split circumvention settings into "easy" and "advanced" views2023-12-08T20:33:09ZdonutsProject idea: Split circumvention settings into "easy" and "advanced" viewsTor's circumvention settings are becoming increasingly complex due to the censorship arms race. While features like Connection Assist were originally envisioned as a way to spare users from manually configuration their circumvention sett...Tor's circumvention settings are becoming increasingly complex due to the censorship arms race. While features like Connection Assist were originally envisioned as a way to spare users from manually configuration their circumvention settings entirely, the reality is that users subjected to particularly heavy censorship often need to dive into these settings anyway.
Current routes to circumvent censorship include:
- Connection Assist
- Built-in bridges, including:
- Obfs4
- Snowflake
- Meek
- Bridges requested from rdsys
- User added bridges, distributed by:
- Telegram
- Email
- Web
In the near future, these options may be further expanded by the addition of:
- Lox bridges
- New pluggable transports, i.g. Webtunnel and Conjure
- Incorporating Orbot's "Ask Tor" feature
As such, there may be some benefit in splitting our circumvention settings into "easy" and "advanced" views, to prevent users from becoming completely overwhelmed by the sheer volume of routes. The "easy" view could include simple options like built-in bridges, alongside semi-automated options powered by the circumvention API (e.g. Connection Assist or Ask Tor), whereas the "advanced" view would contain options that provide for more manual configuration.https://gitlab.torproject.org/tpo/ux/team/-/issues/86Project idea: Document interface guidelines for Tor-powered apps2023-12-14T17:36:39ZdonutsProject idea: Document interface guidelines for Tor-powered appsAfter the new style guide is in place, we would like to add a section documenting some of the common interfaces Tor-powered apps often need to implement, for example:
- Bootstrapping
- Circuits
- Onion services
- Censorship circumventio...After the new style guide is in place, we would like to add a section documenting some of the common interfaces Tor-powered apps often need to implement, for example:
- Bootstrapping
- Circuits
- Onion services
- Censorship circumvention
The idea would be to provide application agnostic wireframes of each common interface, accompanied with short descriptions and links to other materials for implementation. The goal here is to promote greater UX consistency in the Tor ecosystem, and nudge developers towards solutions that have been validated by user research.
However we don't want to be overly prescriptive and demand that developers from our community implement Tor Browser's current UX. Instead, in addition to ideas that we've came up with internally, we should also look to the creative solutions our peers in the community have developed when creating our application agnostic UX. Similarly, after the guidelines have been established, developers shouldn't be bound to follow them exactly—and instead be encouraged to modify the UX when necessary to suit their apps' individual use-cases.
At present, I imagine the focus here to be on Tor-powered functionality specifically. While we could expand the scope to include UX recommendations for more general privacy and security features, we should take into consideration our capacity to maintain this resource in the longer term.https://gitlab.torproject.org/tpo/ux/team/-/issues/85Blog post idea: User research retrospective2023-12-08T18:07:06ZdonutsBlog post idea: User research retrospectiveWrite a blog post summarizing how the number of users who've participated in qualitative user research has increased over the years, documenting our evolving research methods and how this work has guided our design decisions.
This would...Write a blog post summarizing how the number of users who've participated in qualitative user research has increased over the years, documenting our evolving research methods and how this work has guided our design decisions.
This would probably be best accompanying the announcement of the new user research handbook, with a call to action to recruit a new generation of Tor user researchers.https://gitlab.torproject.org/tpo/ux/team/-/issues/84Blog post idea: Let's talk about feature parity2023-12-08T18:06:43ZdonutsBlog post idea: Let's talk about feature parityWrite a blog post summarizing the current state of feature parity between the core apps we distribute, alongside a call for funding to narrow the gap.Write a blog post summarizing the current state of feature parity between the core apps we distribute, alongside a call for funding to narrow the gap.https://gitlab.torproject.org/tpo/ux/team/-/issues/83Blog post idea: Tor Browser, easier to use than ever2023-12-08T18:01:18ZdonutsBlog post idea: Tor Browser, easier to use than everWrite a blog post summarizing the last year, two years or few years' worth of progress advancing Tor Browser's user experience.Write a blog post summarizing the last year, two years or few years' worth of progress advancing Tor Browser's user experience.https://gitlab.torproject.org/tpo/ux/design/-/issues/65Request access to Firefox's icon libraries for @nicob2024-01-16T19:30:14ZdonutsRequest access to Firefox's icon libraries for @nicobdonutsdonutshttps://gitlab.torproject.org/tpo/ux/design/-/issues/64Fix the style and weights of custom Acorn icons2024-01-29T19:07:04ZdonutsFix the style and weights of custom Acorn iconsSee [acorn/iconography](https://acorn.firefox.com/latest/styles/iconography-q7JqGl5H) for reference.
Judging from a quick look, it looks like we'll have to make the following changes at least (however I'll try and get you access to thei...See [acorn/iconography](https://acorn.firefox.com/latest/styles/iconography-q7JqGl5H) for reference.
Judging from a quick look, it looks like we'll have to make the following changes at least (however I'll try and get you access to their libraries to confirm):
- [ ] Remove cuts from icons
- [ ] Switch to square (not rounded) terminals
- [ ] Make dots (e.g. those in exclamation and question marks) square
- [ ] Make sure the weight of strokes is 1.25px at 16px (except for where optical adjustments are necessary)
The newer icons look like they're embracing slightly rounder shapes too.nicobnicob2024-05-30https://gitlab.torproject.org/tpo/ux/design/-/issues/63Develop a workflow to use Firefox's libraries2023-12-08T21:18:55ZdonutsDevelop a workflow to use Firefox's librariesMozilla have generously provided us with guest access to their Figma libraries for Firefox. Since they're on a separate team from us, it doesn't look like we can "add" these libraries to our files in the same manner we can with internal ...Mozilla have generously provided us with guest access to their Figma libraries for Firefox. Since they're on a separate team from us, it doesn't look like we can "add" these libraries to our files in the same manner we can with internal libraries.
We can export each library as a .fig, and re-import it into our Figma team, however I think Figma will drop the associations between each file in the process (e.g. color styles from the Styles file that get reused in design files). Alternatively, we can copy/paste individual components across where needed.
With both approaches, we'd lose updates from the canonical libraries on Mozilla's end in the process too.https://gitlab.torproject.org/tpo/ux/design/-/issues/61Draw new illustration set2024-03-27T14:34:40ZdonutsDraw new illustration setDuring the hackweek, @nicob worked on a prototype for a new illustration style:
![new-illustration-style](/uploads/5e7358be99ff09fcd647a6389eacbf25/new-illustration-style.png)
And it looks great!
The next steps are to:
0. Maybe docum...During the hackweek, @nicob worked on a prototype for a new illustration style:
![new-illustration-style](/uploads/5e7358be99ff09fcd647a6389eacbf25/new-illustration-style.png)
And it looks great!
The next steps are to:
0. Maybe document the basic rules for the style? I attempted to describe it here: [Figma / design-dot / Pages](https://www.figma.com/file/nIpahk0b9VMaeEnubiO33g/design-dot?type=design&node-id=291%3A10068&mode=design&t=fHze76LK0jCQsL6Y-1)
1. Create and agree on a list of themes to illustrate for the base set
2. Draw the illustrations!design-dot MVPnicobnicob2024-03-28https://gitlab.torproject.org/tpo/ux/research/-/issues/127Collect questions for the next user survey2024-02-29T16:03:47ZdonutsCollect questions for the next user surveyThe UX team are considering running a new Tor Browser user survey in 2024—see https://gitlab.torproject.org/tpo/ux/team/-/issues/94 for details. If your team has a question you'd like to ask our users that can be answered with predefined...The UX team are considering running a new Tor Browser user survey in 2024—see https://gitlab.torproject.org/tpo/ux/team/-/issues/94 for details. If your team has a question you'd like to ask our users that can be answered with predefined responses (i.e. no free form text boxes), please leave it here.
If your question doesn't fit the survey format, isn't suitable for a general audience, and/or requires more qualitative feedback, please open an independent issue in [ux/research](https://gitlab.torproject.org/tpo/ux/research/-/issues) instead.https://gitlab.torproject.org/tpo/ux/team/-/issues/82Consider merging the global "UX" and "UX Team" labels into "Needs UX"2024-03-07T14:49:42ZdonutsConsider merging the global "UX" and "UX Team" labels into "Needs UX"At present, we have two similar-but-different global UX labels:
- ~UX: which people use across the Tor Project to indicate an issue that has some impact on the user experience of our products.
- ~"UX Team": which we use to track issues ...At present, we have two similar-but-different global UX labels:
- ~UX: which people use across the Tor Project to indicate an issue that has some impact on the user experience of our products.
- ~"UX Team": which we use to track issues that will require work from a member of the UX Team.
Given that the bucked of issues that could be tagged as ~UX is very, very broad – and not necessarily useful to filter by – I'm beginning to think we should replace both with a `Needs UX` label that's far narrower in scope. This label should then be used to invoke a UX team-member, rather than pinging people individually in Gitlab or IRC, and can remain tagged as such until the UX Team feels it's no longer necessary to track the issue on our kanban.
So, thoughts?https://gitlab.torproject.org/tpo/ux/design/-/issues/58Add shadow-20 to Proton UI library2023-08-08T17:36:33ZdonutsAdd shadow-20 to Proton UI libraryAt the moment we have shadow styles for `shadow-10` and `shadow-30`, so I'm assuming there's also a shadow-20 in the CSS we can add.At the moment we have shadow styles for `shadow-10` and `shadow-30`, so I'm assuming there's also a shadow-20 in the CSS we can add.https://gitlab.torproject.org/tpo/ux/design/-/issues/55Update the Proton UI library following Tor Browser 13.0's release2023-12-08T21:18:55ZdonutsUpdate the Proton UI library following Tor Browser 13.0's releaseAfter Tor Browser 13.0 has been released, we'll need to update the desktop design library with any changes that have been made.After Tor Browser 13.0 has been released, we'll need to update the desktop design library with any changes that have been made.https://gitlab.torproject.org/tpo/ux/design/-/issues/54Tidy up the Connection settings screens in the Proton UI library2024-01-29T19:25:38ZdonutsTidy up the Connection settings screens in the Proton UI libraryThese still need a little tidying up.These still need a little tidying up.https://gitlab.torproject.org/tpo/ux/design/-/issues/53Add corner radiuses as varibles to the Proton UI library2023-08-08T17:23:11ZdonutsAdd corner radiuses as varibles to the Proton UI libraryCorner radiuses seem to be pretty consistent in Firefox, so I think this is another thing we could move into variables relatively easily.Corner radiuses seem to be pretty consistent in Firefox, so I think this is another thing we could move into variables relatively easily.