In this post I will point out some issues with the Reblog functionality on busy.org (beta) from a UX standpoint.
At the end I will also suggest how these issues could be resolved by giving a few examples(with images).
I tested on Opera/Windows.
First, I reblogged a post, which worked without issues. After it was reblogged I could see it on my profile page and it was also labelled at the top of the post that it was reblogged as one can see in this screenshot:
However, when I went to the profile of the post's owner, there was no label and also no way to see that I reblogged it(or someone else did).
Users could expect to see that they already reblogged that post, so that they see it at a glance and not think that maybe the reblog functionality didn't work.
Here is the same post but on the owner's profile page:
The reblog link/button seems to let me try to reblog again
And when I click on it, the reblog modal shows up, as if I didn't already reblogged it.
This could confuse users to think that they can reblog the same post more than once:
Then, when I click the 'Reblog' button in the modal to try to reblog again, I get one error on the site and two errors in the console.
The error on the site says 'Account has already reblogged this post.' which I find it personally to be depersonalizing. None likes to be called 'Account' :) Maybe instead it could say 'You have already reblogged this post' or 'This post was already reblogged by you'.
Here is how it looked like when I tried to reblog an already reblogged post:
To avoid this UX issue and improve this functionality I suggest that the 'reblog' arrow could be 'active' if I see a post that was already reblogged by me. Here is how this could look like:
And, if I actually click on the active reblog link/button, it should not show me the reblog modal and let me to try to reblog again, instead a different modal should appear that informs me that such an action cannot be repeated. Here is how such a modal could look like:
Open Source Contribution posted via Utopian.io