Unlocking Interaction Design: How ‘Control Power’ Transforms UI Communication

Part 1: Interaction Design in Everyday Life

Every tap, swipe, or drag on a screen hides complex design decisions. Interaction design emerged with graphical user interfaces to solve usability problems, yet its knowledge base is still immature, often causing miscommunication among designers, product managers, and developers.

Part 2: Drag vs. Flick

In a classroom exercise, students were asked to distinguish between drag and flick gestures. The discussion highlighted how different gestures convey distinct intentions and how ambiguous descriptions can lead to misunderstandings.

Part 3: The Magic of Interaction Design Language

Interaction design language introduces core concepts such as controls, objects, and linkages. When a control changes, linked objects update accordingly, creating a sense of "control power." This framework allows designers to describe relative, absolute, and cyclic linkages, enabling precise communication of interaction details.

Part 4: Practical Power of the Theory

Case 1 – Bus‑Route App Traditional bus‑route interfaces either display a long line for both directions or use a toggle button, often confusing users. By applying the "control power" perspective, a scrollable list controls the displayed direction, and a checkbox toggles the linkage, simplifying navigation.

Case 2 – WeChat Back Navigation Users often interrupt reading to handle messages, repeatedly pressing the back button. Using the control‑power mindset, a long‑press on the back gesture reveals a layer preview, allowing quick jumps between chat, payment, and other screens, reducing interruption.

Part 5: Mastering the Art of Dialogue with Everything

Interaction design language provides an abstract "control power" view that can be applied to physical, digital, and even security contexts. It enables low‑cost, rapid iteration at the conceptual level, shortening development cycles compared to traditional prototype‑heavy workflows.

Traditional workflow (high cost, many iterations) vs. interaction‑design‑language workflow (low cost, mental iterations) is illustrated below.