Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Global/General Network Activity Indicator #56

Open
ninavizz opened this issue May 29, 2019 · 4 comments
Open

Global/General Network Activity Indicator #56

ninavizz opened this issue May 29, 2019 · 4 comments
Assignees
Labels
Low team priority Others not quite convinced we should do this anytime in the near future, abreast other priorities. Needs Field Obvservation Things we need to track in the Pilot study SDW Client Workstation Beta

Comments

@ninavizz
Copy link
Member

ninavizz commented May 29, 2019

This is a next-iteration upon #32 for indicating network activity status to users


Problem

How will general network activity be shown within the Client?

Considerations

  • This ticket is for a non-specific, global "things are happening, packets are flying!" indicator.
  • States discussed:
    • "We have contact with the Server, but packets have yet to fly"
    • "Packets are flying!"
    • "Derp, unstable or no contact with Server"

Acceptance Criteria

  • Simple animation of a scenario that team agrees upon as good-to-go
  • Animation is reasonably implementable for Beta
  • Mockup(s) demonstrating possible different states
  • Ready to handoff to @creviera
@ninavizz ninavizz added Needs Testing Something we need to get in front of users Workstation Beta labels May 29, 2019
@ninavizz ninavizz added this to the Beta milestone May 29, 2019
@ninavizz ninavizz self-assigned this May 29, 2019
@ninavizz ninavizz added Needs Field Obvservation Things we need to track in the Pilot study and removed Needs Testing Something we need to get in front of users labels May 29, 2019
@eloquence
Copy link
Member

(Keeping off near-term backlog on the board for now - priority is #32 and, as you note, field observations to better understand real world network conditions, so we can determine empirically what kind of user feedback we want to give while the client is running, in addition to error states.)

@ninavizz
Copy link
Member Author

ninavizz commented Jun 6, 2019

This document ready for review. If it is difficult to understand, pls ping @ninavizz offline; brain got mushy & I decided it was time to get collab happening. :)

https://docs.google.com/spreadsheets/d/1jXalueqcT8RWWG7osGLFO8dsG6_EB9NdbfJfE_NEmqw/edit?usp=sharing

@eloquence
Copy link
Member

Thanks for the detailed spreadsheet, Nina! I suggest we take a look at this in the UX review on Tuesday. My immediate takeaway: I think we should be able to add many of these messages in a first iteration, and then perform measurements in Qubes and other observations to determine which messages should be grouped, etc.

Whether the next sprint is a good time to start making these updates, I would especially appreciate Jen's and Allie's input on.

@ninavizz ninavizz removed this from the Beta milestone Jul 21, 2021
@ninavizz ninavizz added the Low team priority Others not quite convinced we should do this anytime in the near future, abreast other priorities. label Jul 21, 2021
@ninavizz
Copy link
Member Author

This has been off the collective radar for many months, but a desire to show network activity to users in the client may arise in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Low team priority Others not quite convinced we should do this anytime in the near future, abreast other priorities. Needs Field Obvservation Things we need to track in the Pilot study SDW Client Workstation Beta
Projects
None yet
Development

No branches or pull requests

2 participants