I think putting the twt options (reply, fork, edit...) on a [drop list] menu is a bad idea. Other than the complexity for both, desktop and mobile/responsive, interfaces, it requires an extra tap/click. It would be akin of putting the formatting icons (which I don't think we need, but that's irrelevant here) on a drop list menu.
I think putting the twt options (reply, fork, edit...) on a [drop list] menu is a bad idea. Other than the complexity for both, desktop and mobile/responsive, interfaces, it requires an extra tap/click. It would be akin of putting the formatting icons (which I don't think we need, but that's irrelevant here) on a drop list menu.
f
in Tridactyl, in case somebody cares about that. Might be okay for less frequently used operations, such as edit and delete, however, introducing a second step for reply and fork is probably very annoying. Again, I don't use yarnd, but if I did, that would be my concerns.
- It allows us to have Edit/Delete options everywhere
- Reduces the amount of UI/UX noise that exists because of the above creating a lot of noise
I'm not sure how else we support: Edit, Delete, Share and Bookmark everywhere without cluttering up the UX? Plus Reply Fork and Yarn 🤔
- It allows us to have Edit/Delete options everywhere
- Reduces the amount of UI/UX noise that exists because of the above creating a lot of noise
I'm no
- It allows us to have Edit/Delete options everywhere
- Reduces the amount of UI/UX noise that exists because of the above creating a lot of noise
I'm not sure how else we support: Edit, Delete, Share and Bookmark everywhere without cluttering up the UX? Plus Reply Fork and Yarn 🤔