The claim in the title may appear bold, but I think one can argue this would be an improvement.
Interact can do things the coupler cannot. So when I open the coupler menu, and realize I want to, lets say, change visibility, I have to exit the coupler, and the interact (on mobile this feels as if it would even require to exit edit mode).
You are forced to learn two concepts and their distinct user experiences and capabilities. This would only be justified if there is a good reason for it, which I fail to see.
I am aware that this merger may have serious ramifications and would require some thought.
Still, I would be interested in how everybody feels about this.
+1 seems like a reasonable simplification that would streamline some interactions during editing.
I guess one design issue is working out functionality that wouldnât make as much sense from the âinteractâ context, such as linking or moving selected text, but these are already contextualized in the coupler, so they can likely continue to work that way and simply not display in the interact context.
I really like this idea. Iâm frequently wondering how to get to the âinteractâ menu from mobile, and just having it under a section in the UC would be fantastic. Iâd love being able to just have to remember one keyboard shortcut for all note interactions and editing, and the ability to search by text to select the right tool would be so good.
Hi all, weâve been thinking about this internally as well, generally we like to keep them separate as editing and previewing content is slightly different â however we have a bunch of ideas that we know will make both feel better and similar. @ariccb on mobile, you can tap on the (âŚ) ellipsis > then tap âInteractâ to bring up the menu.