-
Notifications
You must be signed in to change notification settings - Fork 176
Hide order modal after clicking 'save' #1053
Comments
Alternatively we should put a spinner on the Save button to prevent double clicks. |
That will work too. How long will we leave the order modal hanging though? |
Ok so I chatted with @cpacia about this issues and this is what's happening in the server:
To enhance the user experience, we need to assume that crawls will always be initiated after these messages are sent. We should not leave the user staring at a modal for a 1+ minutes, even if we have a spinner or something. What I think we should do is close the modal and create a bottom status bar notification (similar to 'Saved Changes' in the Settings) saying:
I also think that the first message should keep showing until the message has been sent, because we want to discourage users closing the app immediately (which would cause problems with message delivery). This approach frees up the user to explore other parts of the app while the message is sending in the background. Best case scenario, more times than not these bottom status bar notifications will briefly show as most messages will be sent immediately (due to a direct connection) and as we make improvements to network crawling (so that it doesn't take so long). |
Just a note, I didn't add the loading spinner to this button in the loading button PR because I plan to implement something similar to the more detailed proposal with the status bar for this one. |
Cool! |
When you go to confirm an order and click 'Save', the modal can hang while it's waiting for a response. Users can mistakenly click the 'Save' button twice, thinking that they didn't click it correctly the first time, which produces a 'Data cannot be saved' error that's related to the second superfluous click.
A better UX would be to hide the order modal after clicking 'Save' and use the status bar at the bottom of client to indicate that the message is sending and when a response has been received. Also we need to think about what happen if the user clicks the 'Order Details' button to bring up the modal again.
The text was updated successfully, but these errors were encountered: