#44 Usability testing for fedora happiness packets
Opened 5 years ago by algogator. Modified 4 years ago

Goal: Find out if community members would use the app during FAW
https://happinesspackets.fedorainfracloud.org/

Target: Fedora Contributors

Tasks: Pick any 2 at least per test, and the medium i.e laptop or phone
First, introduce Fedora Appreciation Week and How it ties in with Fedora Happiness Packets website
Tell them about this test and how much time it will take. Emphasize that they are in control and nothing can go wrong.

Max 5 mins per test
Go through the website
1. Send a happiness packet (with different privacy permissions)

* What is this task difficulty level for you? Easy/ Medium/ Hard
  1. Share it on social media of your choice

    • What is this task difficulty level for you? Easy/ Medium/ Hard
  2. Locate an inspiration message or a past message

    • What is this task difficulty level for you? Easy/ Medium/ Hard
  3. Do you find it easy to use the options to anonymize? Are there any other options you would like to see?

  4. What do you like the most about this app? (Figure out the things we did right and maybe improve it)
  5. If you could change one thing about it the app what would it be and why? (Find out what can be changed)

Location: Community Operations workshop @ FLOCK

Time: 15 mins

What do I need:
1. Pens
2. Paper
3. What tasks they did
4. What medium they used i.e Phone vs Laptop

Get the attendees details:
- Name
- FAS ID

Questions:
1. Do you have any questions for us?
2. Would you use this app to send happiness packets? (Getting straight to the point :P)
3. What feature would you like to see out of this? Choose one!

- IRC bot messages of happiness packets send

- Audio or video message support

- Emoji support
  1. Are there any other features you would like to see?
  2. Have you used Happiness packets website? If yes, when would you use Fedora Happiness Packets vs Happiness Packets?
  3. How often do you think you will use this app normally? (Obviously, we want people to use it after FAW)

Summary:

The general trend seems to be:
- The emails confirmation is a tedious step
- Needs to be responsive on mobile
- Be able to search for users by their usernames
- The privacy options can be simplified


Hi @algogator I want to start working on this, Pls assign

Metadata Update from @jflory7:
- Issue assigned to jonatoni
- Issue priority set to: waiting on assignee (was: awaiting triage)
- Issue tagged with: new change, type - Flock, type - summer coding

5 years ago

@jonatoni @bee2502 Do either of you have the data recorded from the usability tests? Can the data be shared publicly?

@jflory7 yes, I have the data but I will need some time to find all the tests and publish them. Before doing that, I will also ask each of the people that helped with the usability testings if they are okay with publishing the results or not.

Metadata Update from @jflory7:
- Issue set to the milestone: Summer Coding 2019: community bonding

5 years ago

@jonatoni Sounds good. I tagged this one for the community bonding period of Summer Coding 2019. Leaving this one assigned to you for now. :thumbsup:

@jflory7 Can I be assigned to this as well? I am struggling to find what I can contribute to :-(

@severusho This one is waiting for other work to be done before we open it up for applicants. If you are just getting started, please check out tickets #100 and #103 to begin. :thumbsup:

Metadata Update from @jflory7:
- Issue set to the milestone: Future releases (was: Summer Coding 2019: community bonding)

5 years ago

Metadata Update from @jflory7:
- Issue set to the milestone: None (was: Future releases)

5 years ago

Hi @jonatoni, is it possible to find this feedback before the end of Outreachy phase 1 (8 June)? I'd like to get the feedback integrated into our project planning if possible.

I've shared with @jflory7 all the feedbacks we gathered last year at Flock.

Thanks @jonatoni! I'm going to work on filtering and anonymizing next week.

Metadata Update from @jflory7:
- Issue assigned to jflory7 (was: jonatoni)
- Issue set to the milestone: Summer Coding 2019: phase 1

4 years ago

Metadata Update from @jflory7:
- Issue set to the milestone: Summer Coding 2019: phase 2 (was: Summer Coding 2019: phase 1)

4 years ago

Metadata Update from @jflory7:
- Issue set to the milestone: None (was: Summer Coding 2019: phase 2)

4 years ago

Login to comment on this ticket.

Metadata