Work with Peter H/Ori on Performance team to determine heuristic/testing flow for performance inspector.
I am reaching out to Daisy to see if she has any documentation from the beginning of the research, and what the research question was, and what point she got to. Will update here when I hear back from her.
Also, after reading T129322 (about where the inspector should be invoked) it looks like it is not really resolved. (To be honest, I read SOME of the discussion on the task.) Is the work blocked on this decision?
I am wondering if the inspector could benefit from a basic heuristic evaluation of the UX? There is a lot of feedback in the ticket from many perspectives, and not only about where to invoke.
It might also be useful to observe some people (the people who the tool was designed and built for) using the inspector, and see what works and doesn't for them. We could ask them their opinions of where it might be invoked and if they need it on mobile, etc.
Someone needs to clarify if this is still wanted and what this task is about. Following https://www.mediawiki.org/wiki/Phabricator/Project_management#Use_plain_language.2C_define_actions_and_expected_results would help.
Hey @aripstra let setup a meeting so we can sync, maybe that is easier.
We need to get an OK where we can place the link to start the inspector, we don't have that today and also checking the usability/look and feel would be great.
You can test out the current version of the inspector on https://en.wikipedia.beta.wmflabs.org/wiki/Chamber_music (search for Performance inspector under the Tools menu).