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

Should a user be able to re-record a new update? #65

Open
danillouz opened this issue Oct 8, 2019 · 1 comment
Open

Should a user be able to re-record a new update? #65

danillouz opened this issue Oct 8, 2019 · 1 comment
Assignees
Labels
enhancement New feature or request question Further information is requested

Comments

@danillouz
Copy link
Member

danillouz commented Oct 8, 2019

Currently a user can "override" their recordings by just recording a new update. This is basically an implicit delete.
But there's no way to delete (past) updates explicitly (yet?).

Additional questions:

  • Should a user explicitly delete their update first before they can re-record?
  • How are other members "affected" when updates are re-recorded (or deleted)? What are the implications?
  • Why would a user even want to delete their update, since it's possible to preview recordings, and "practice" before "publishing".

Explicitly deleting updates:

  • Why should past updates even be deleted?
  • Who can/should be able to delete updates?
@danillouz danillouz self-assigned this Oct 8, 2019
@danillouz danillouz added the question Further information is requested label Oct 28, 2019
@danillouz danillouz changed the title Fetch todays recordings in new update Should a user be able to re-record a new update? Oct 28, 2019
@danillouz
Copy link
Member Author

danillouz commented Nov 26, 2019

After using the app and getting initial feedback, it sometimes happens that we forget to include something in an update.
Currently this means we have to "redo" (i.e. override) the recording (either in preview mode or after publishing). And this is a bit inconvenient.

I think a better mechanism would be to make it possible to keep adding recordings, i.e. as separate update messages. I believe this would make sharing updates more intuitive, but also make it possible to share updates during the day. Or when something unplanned happens. This way we can keep the team informed during the day, without potentially "forcing" a specific format on the user.

Effectively this means we'll get rid of the more "rigid" structure of the 3 questions we currently ask:

  1. Did you work on something yesterday?
  2. What do you have planned for today?
  3. Do you have any blockers?

And potentially replace this with a more flexible UX that allows the user to record many messages (I guess also name them) and then publish them. After publishing, a user can record and publish new updates. Where any published update can be deleted by the user who published it.

Questions:

  • Should we limit the amount of updates a user can make?
  • Should only users that publish their update be able to delete their recording? Or do we also need some sort of moderator/team owner which can delete anyone's recording?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant