Comment 16 for bug 641899

It's definitely important to stress test things on a poor quality slow connection.

Imagine a new user setting up Ubuntu for a first time, already a bit overwhelmed by everything, and they've just got Dropbox setup and hogging network resources as it downloads many GB of data, while they continue to search for and install apps.

There are a few different issues I'm seeing, which I agree would be best posted separately (triage?), but as this issue already exists I'll post it in here...

1) The Install button really needs to be smart. If you go back and forward again, it needs to be at least greyed out if the software in question is already installing or in a queue to be installed.

2) If you do a search, the progress spinner should activate immediately. Currently it lags a bit. A user on a slow connection and bogged down machine has no idea if the extended lag is due to bugs, failed searches, back-logged search requests, or system slow-down.

3) I believe (but could be wrong) that in the current implementation it's possible for a search to come in after the search field has been changed to something else already, due to lag. That should never be possible - if the activate contents of the search field is not a superstring of what a search result has come in for, don't show that search result.

4) Ideally there would also be an installation queue tab so you can see what's in progress. You don't know as a user what has stalled, vs what is just being slow, vs what is back-logged.