The universal coupler menu and the interact menu should be the same thing

Thoughts & Feedback
1

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.

4 Likes
2

+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.