Not to mention those 3 seconds to ”mark as read”.
I am wondering if this should be handled on the interface level where it appears instantly while the 3 seconds is handled in the background.
You are viewing a single comment's thread from:
Not to mention those 3 seconds to ”mark as read”.
I am wondering if this should be handled on the interface level where it appears instantly while the 3 seconds is handled in the background.
Unless there’s an update to the hive mind system which fixes it, it would be a good solution to do on interface level. Especially if like peakd there’s an error queue anyway to notify if it failed.
But it applies on multiple aspects. Take for example following people, also need to wait three seconds to follow the next one. Very poor experience if an app shows a list of recommended users or you want to start by following a bunch followed by the person who onboarded you.
These are minor details but I can imagine for select demographics they actually aren’t that minor. Even four years ago, well in the mobile first era already, 3 seconds was absolutely slow.
!ENGAGE 30
Yep, it is definitely an issue for a growing number of people, at least those who are under 30 :D
ENGAGEtokens.