You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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:
Did you work on something yesterday?
What do you have planned for today?
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?
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:
Explicitly deleting updates:
The text was updated successfully, but these errors were encountered: