Team issueshttps://gitlab.torproject.org/tpo/ux/team/-/issues2023-12-14T17:36:39Zhttps://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.