Contact deletion is not quick enough to be intuitive

[tadzik]

Deleting a contact waits for a complete REST API transaction (delete + refresh) before removing the contact from the screen – this is needlessly confusing, as it tempts the user to try to delete the contact again, queuing a request that will inevitably fail once the first one succeeds.

The contact should be removed from the UI immediately, for the sake of clarity and perceived snappiness :)

[tadzik]

Flagging this as bug since that's what it feels like to the end user.

[ConnectGrid]

Some immediate user interface feedback should be provided (agreed), but the other question is why is the API request/response so slow? It you monitor the XHR timing, the "Waiting" time is far too long. Fixing that would likely give much faster responses.

(This goes back to all requests going to runbox.com ... I've always felt this is putting too much demand on one system. Spreading requests across separate dedicated servers, such as "api.runbox.com" as a separate server, would result is much faster responses.)