Tracking problems around metadata (no "X" field which we need in the ui) certainly seems useful. Perhaps tracking cases when we have to generate missing favicons could be good as well for general awareness of what the UI looks like for most users. For bad states around highlights, this might tie in with work on the highlights algorithm in Bug 1312016. Background from an email thread: A-S on Desktop: Bad States: we try to keep track of bad states such as when we show a highlight without an image, when we show the loading screen for too long or when our addon causes a "may be making your browser slow" warning. These types of bad states are probably different in Android but worth considering if there are any you'd like to collect.

Steph, I'd prioritize this over some other UI-polish bugs that we currently have in the list. Especially with the new highlight ranking algorithm, it'll be good to get some insights into how it is performing.

All open Activity Stream bugs are moving from the whiteboard tag, "[mobileAS]", to the Firefox for Android component, "Activity Stream", so that I can keep better track of these bugs as the new triage owner; I will send out an email shortly with additional details, caveats, etc.

This does not seem actionable without specific problems we're trying to solve, and thus the specific metrics we're trying to collect: closing.