ScopeyNZ
commented
4 years ago The intended experience here is that the user gets the block immediately, but saving is not possible until the server responds saying it's created. We already do this for deletes ("optimistic deletes"). The user would get a slightly jarring experience if the creation fails, but that's in (hopefully)) exceptional cases.
I'm pretty confident that "optimistic adds" are pretty doable with what we have, but I agree that spinner is a good option if that's too hard 🙂 .
On setups with little machine resources (e.g. "small" cloud setups and Vagrant/Docker development boxes), the time taken from selecting "Add Block" to the block being dropped into the CMS for editing can be 3 or 4 seconds, during which time users start to wonder if anything is actually happening.
A simple fix would be to add a spinner or similar, that appears immediately upon selecting "Add Block" and disappears once the block is inserted into the CMS' UI.