citizenos / citizenos-fe

5 stars 3 forks source link

IDEATION: Refreshing needed to see new activity #1256

Open BeccaMelhuish opened 5 months ago

BeccaMelhuish commented 5 months ago

In the tests, users are having to refresh to see activity that has happened since they arrived.

E.g. new replies, new upvotes, etc. (So when I engage with their posts in the tests, they don't see it unless I tell them to refresh.).

And in this case my idea was showing, but I wasn't showing in the participants list until he refreshed:

image

Ideally, if possible, activity would appear without having to refresh. As it's quite possible that someone would leave their browser tab open and not see all the activity since they last arrived. Or that a lot of people would be online engaging at once, and they would miss what's going on - post the same idea as someone else, miss a reply that was important etc.

BeccaMelhuish commented 5 months ago

Another example, for discussions phase. When users have post an argument in an empty discussion, they see this after posting (no change from before posting). I then have to tell them to refresh so they will see what they posted:

image

ilmartyrk commented 4 months ago

@BeccaMelhuish this is a bigger change, it will probably need whole loading logic change to start using WebSocket or SSE

BeccaMelhuish commented 4 months ago

@ilmartyrk is this one fixable at all (and the equivalent for adding an idea)? As it's quite confusing for users who've just posted something, to not see it appear, and be back where they were before posting as if it didn't work.

ilmartyrk commented 4 months ago

@BeccaMelhuish will check, if a person posts then the content can be reloaded after the action, but I understood that the issue was about user x posting something and user y only seeing it after reloading, I'll try to fix the case 1 things where I can find them, but case 2 needs the bigger change as I mentioned in my previous comment

BeccaMelhuish commented 4 months ago

@ilmartyrk OK great yes, that would be a great start, and then let's see later about the rest :)

BeccaMelhuish commented 2 months ago

I see that for me this part is fixed (though maybe @ssin1901 could test further?)

But for the rest, I will leave it open as an 'UX - L' 'UX Priority' issue - as it's pretty important for the user experience, but sounds like it will be a big job to fix.