Joe, as devtools module owner, has made the executive decision that we should do a UX review before turning the memory panel on by default. Let's use this bug for documenting and addressing issues that come up in the UX review. Depending on how many issues we identify, this may morph into a meta bug. Helen, what can I do to help the UX review go smoothly? Any idea when we might be able to squeeze this into your TODO list?

I think it might be most useful to set up a meeting and go through the Memory tool together to flesh out this bug. I'll set one up for next week.

We should be sure to update the docs for all these changes

Helen, are there any other actions items you'd like to see come out of this? Should we resolve this bug?

(In reply to Nick Fitzgerald [:fitzgen] [⏰PDT; UTC-7] from comment #3) > Helen, are there any other actions items you'd like to see come out of this? > Should we resolve this bug? In Slack Fang and I have been working on some new loading states, this being the "long" version: - https://drive.google.com/a/mozilla.com/file/d/0B1V1eo-I8g3dMWNYeVJJaXRWS0k/view I'd originally asked her to come up with the longer loading state to capture some of the longer load times for the memory panel, but I know you've put work in to making the memory tool much faster. Is this work still worth doing? Would this bug be the bug to capture implementing that work if it is?

"snapchat" lol I like that animation a lot, very cool! I think we can file a new bug for that, and close this one. Filed bug 1279116 for that. I think it is still worthwhile -- we've made lots of performance improvements but we're dealing with computations that are pretty heavy by nature, so I don't think we will ever reach something close to instant.

(In reply to Helen V. Holmes (:helenvholmes) (:✨)(pls ni?) from comment #4) > (In reply to Nick Fitzgerald [:fitzgen] [⏰PDT; UTC-7] from comment #3) > > Helen, are there any other actions items you'd like to see come out of this? > > Should we resolve this bug? > In Slack Fang and I have been working on some new loading states, this being > the "long" version: > - > https://drive.google.com/a/mozilla.com/file/d/0B1V1eo-I8g3dMWNYeVJJaXRWS0k/ > view > This animation is amazing. > I'd originally asked her to come up with the longer loading state to capture > some of the longer load times for the memory panel, but I know you've put > work in to making the memory tool much faster. Is this work still worth > doing? Would this bug be the bug to capture implementing that work if it is?