Closed holmesworcester closed 3 years ago
Here's a rough mockup of what it could look like.
Note: it may be better to put the message underneath the text entry field, the way we currently do for typing indicators. The advantage of doing it this way would be that we already have design for text that displays there. (I'm not sure we have any design for a temporary message that appears above the text entry field.
@vinkabuki is this done in the release with DMs?
Also, I think we should probably use the existing design for typing indicators, rather than improvising new design.
If there's a spinner icon we can add, that's even better.
@vinkabuki I think it was good to add this indicator here, but I don't think the current behavior is clear enough to release.
Right now you see this warning, which refers to "waggle" (something the user doesn't know about) and isn't clear.
Then if you try to send a message it disappears.
Then if you try to send another message it doesn't let you send it and enter does nothing.
I think the quickest route on this is to grey out the field and use something like our "____ is typing..." text below the field to show the message above.
But the ideal solution would be to let the user send the message, and show some indicator that it is sending.
Ideal solution needs separate task: https://github.com/ZbayApp/zbay/issues/810
@vinkabuki as long as we grey out the field while the loading indicator is happening, that's fine. we don't need to queue.
Sometimes we see an issue (#776) where Waggle takes a long time to sync on restart.
When this is happening, the user should:
I'm agnostic on the best way to achieve this, but I want to discuss it a bit and make sure that whatever we decide to do is something we'll be okay with living with for a while.