Closed jeffbl closed 1 year ago
I'm struggling to find this conversation, but I think that we were throwing around "Interpret this graphic (IMAGE extension)" as the text
I don't recall the conversation, but I'd say that "IMAGE extension" is weird? In the above vein, suggest tweak to "Interpret this graphic with IMAGE"? Maybe spell out IMAGE if that is still confusing, i.e., "I.M.A.G.E."?
It might have been between Sabrina and I, but I think the takeaway was that "interpretation" is better, and using more active language was better. Let's try "Interpret this graphic with IMAGE" for now - we don't spell it out currently and I feel like it's better to be consistent, for now at least.
I second this opinion
From: Cyan @.> Date: Monday, January 16, 2023 at 1:07 PM To: Shared-Reality-Lab/IMAGE-browser @.> Cc: Sabrina Knappe @.>, Mention @.> Subject: Re: [Shared-Reality-Lab/IMAGE-browser] Revisit potentially confusing "Get IMAGE rendering" text for triggering functionality (Issue #282)
It might have been between Sabrina and I, but I think the takeaway was that "interpretation" is better, and using more active language was better. Let's try "Interpret this graphic with IMAGE" for now - we don't spell it out currently and I feel like it's better to be consistent, for now at least.
— Reply to this email directly, view it on GitHubhttps://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FShared-Reality-Lab%2FIMAGE-browser%2Fissues%2F282%23issuecomment-1384402178&data=05%7C01%7Csabrina.knappe%40mail.mcgill.ca%7C048b18d76f1e4a889cc408daf7ec893e%7Ccd31967152e74a68afa9fcf8f89f09ea%7C0%7C0%7C638094892523818571%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=I1lIZRl5S0KxKV8F8Fv6RZcaXy8z1PTLNmE99GtW7R8%3D&reserved=0, or unsubscribehttps://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANL6MPN2ONBNDCGSBUCJ5JTWSWE6FANCNFSM6AAAAAATDQMK3U&data=05%7C01%7Csabrina.knappe%40mail.mcgill.ca%7C048b18d76f1e4a889cc408daf7ec893e%7Ccd31967152e74a68afa9fcf8f89f09ea%7C0%7C0%7C638094892523818571%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=fj6YspEih0AAs1nmjtmb%2B6%2FAekCptOozPXLQn1kahdY%3D&reserved=0. You are receiving this because you were mentioned.Message ID: @.***>
@jeffbl I take it I should assign to @jaydeepsingh25 ?
Please make one very explicit list of new text, and then yes, this should go to Jaydeep. e.g.:
Context menu text: Maps button text: Charts button text:
Note that if we're confident on the text being an improvement, I would hold our extension production update for this, so that it goes out to actual users, rather than waiting for next cycle.
Please update as follows Context menu text: "Interpret this graphic with IMAGE" Maps button text: "Interpret this map with IMAGE" Charts button text: "Interpret this chart with IMAGE"
Copied/summarized from Slack conversation in testing channel on Nov7 20222: I [@jeffbl] was testing some things this morning, and it dawned on me that our option in the browser context menu is likely super confusing if you aren't looking at the screen. Here is the context menu for a photo in Brave, with IMAGE installed (pic attached). Note that there are several "image" related items in the menu including "open image in new tab" and "copy image". Visually, our "Get IMAGE rendering" is very noticeable since it has our icon, has IMAGE in all caps, and is in a separate section of the menu. But these are all visual cues, not apparent to someone just hearing all these items in one long list. I'm pretty sure I would not recognize it as being for the "IMAGE" project vs. just another item related to generic photo functionality.
am I off-base on this given what you've seen with participants? Might this be adding to confusion of people using it for the first time, assuming they even know how to bring up a context menu?
@Sabrina-Knappe wrote: This could very well be causing confusion, we don’t have enough information from users who actively use the extension to have a good idea of how they interpret it. Personally, I’m not even sure how clear the word “rendering” is to users… We really need to do some work where we help users install the extension and then observe them using it…
Jeremy wrote: The obvious stop-gap for now is during the download/install process, to include some prominent instruction about the specific wording/location of the rendering option within the context menu.