[ux] How we work on usability and design at GP

[Ame Elliott]

Many thanks, Nathan. \0/ I look forward to carefully reading.
~Ame

> On Jun 1, 2016, at 8:18 PM, Nathan of Guardian <nathan at guardianproject.info> wrote:
> 
> During the UX team meeting, it came up that we should find ways to more
> fully involve UX work in Tor efforts from the beginning and not as an
> afterthought. I mentioned that over the years at Guardian Project, we
> have learned this lesson through good and bad experiences, and have been
> fortunate to be able to afford to pay smart, talented people to work on
> this with us. 
> 
> One example is with our work on the F-Droid project in creating the "app
> swap" device to device app sharing feature. I think our process isn't
> that unique overall, but it might be helpful to see some of the steps we
> take, and the tools we use to do the work. 
> 
> As often it goes, we start with user stories based on mix of inputs
> including actual reports from people in need, quantative data tracking
> "things people seem to be doing with their smartphones", and cohesive
> creative ideas that make sense within our own roadmap and capabilities:
> https://dev.guardianproject.info/projects/bazaar/wiki/User_Stories
> 
> which leads into a design, discussion thread that interleaves text and
> mockups, with practical feedback on the possible:
> https://dev.guardianproject.info/boards/9/topics/187
> 
> Threat modeling is often done here, to ensure new features don't expose
> users to an unacceptable level of risk, but I can't track down any
> public product we have of that for this effort. Trust me, they exist,
> and we do them! Here is some technical info on the wiki along these
> lines:
> https://dev.guardianproject.info/projects/bazaar/wiki/Bootstrapping_Trust
> 
> Then from this, out of this come various products produced by design
> staff:
> 
> Interactive mobile app screenflow:
> https://projects.invisionapp.com/share/U43673T7T#/screens
> 
> Nearby Design Patterns Guide (PDF):
> https://dev.guardianproject.info/attachments/download/1691/nearby_guide-draft01.pdf
> 
> Technical ideas for specific feature implementations:
> https://dev.guardianproject.info/projects/bazaar/wiki/Swap_over_bluetooth_(in_development)
> 
> and finally, the actualization of concepts into code and minimally
> viable solutions:
> 
> Work in Progress documentation:
> https://dev.guardianproject.info/projects/bazaar/wiki/%22Swap%22_apps
> 
> YouTube demo videos of successfully implemented features for review and
> feedback:
> https://talk.developersquare.net/t/user-interactions-for-nearby-sharing-and-swapping/84
> https://www.youtube.com/watch?v=0XOHyj7CXFM
> 
> Code, issues, commits, patches, code review, continuous integration,
> etc:
> https://gitlab.com/fdroid/fdroidclient/issues/583
> https://gitlab.com/fdroid/fdroidclient/issues/670
> 
> If we can manage, we try to do user focus group testing at various
> conferences and workshops, and document the outcomes as publicly as
> possible for others to learn from:
> https://talk.developersquare.net/t/wind-farm-0-people-powered-nearby-networks-event-harvard-may-15-16/48
> https://talk.developersquare.net/t/some-pictures-from-todays-event/89/3?u=n8fr8
> 
> At some point, once we have done enough internal testing and auditing,
> as well as at certain milestones external audits, we can merge these new
> features into the main app, and ship it!
> 
> Hope this helps, and would love to hear from everyone about steps we
> might have missed, or other tools, techniques, and processes we or the
> Tor community might utilize.
> 
> +n
> 
> -- 
>  Nathan of Guardian
>  nathan at guardianproject.info
> _______________________________________________
> UX mailing list
> UX at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/ux