Frontend Development 11 min read

Taming Unstable 3D Tool Interactions with a Systematic Trigger Design

This article examines the challenges of unstable and inconsistent basic-function triggers in the Kujiale 3D design platform, analyzes root causes such as module isolation, compatibility gaps, and high coupling, and proposes a systematic, entropy-aware interaction architecture with layered trigger logic, progressive optimization strategies, and flexible user-centric configurations to improve stability, extensibility, and user adoption.

Qunhe Technology User Experience Design
Qunhe Technology User Experience Design
Qunhe Technology User Experience Design
Taming Unstable 3D Tool Interactions with a Systematic Trigger Design

01 Basic Function Trigger Experience Challenges

Scope of Basic Function Triggers

In Kujiale, users mainly view and edit designs; triggers are activated via mouse or touchpad gestures for these functions.

Challenge 1: Uncontrolled User Experience

Rapid business expansion led to issues such as module isolation, inconsistent interactions, insufficient compatibility, and unstable trigger conditions.

Module isolation : Different modules maintain independent trigger logic, causing conflicting gestures (e.g., mouse left‑drag+Shift means orthogonal move in one module but free move in another).

Insufficient compatibility : Users from CAD expect left‑drag to box‑select, but Kujiale maps it to camera rotation, increasing learning cost.

Unstable trigger stability : Shared triggers with conditional hot‑zones can misinterpret user intent in complex scenes.

Challenge 2: Unordered Differentiated Design Locks Extensibility

Early lack of systematic design led to fragmented implementations, hard‑coded logic, and high coupling, making future extensions costly.

Fragmented design : Ad‑hoc solutions ignore extensibility, causing each new feature to require full re‑adaptation.

High interaction coupling : Shared trigger mechanisms cause conflicts across modules, e.g., left‑drag+Shift serves both orthogonal drag and object selection.

Challenge 3: User Habit Sunk‑Cost Risk

Long‑term usage creates inertia; changing triggers risks user resistance, training costs, and possible migration to competitors.

Inertia dependence : Users have adapted to existing gestures.

Sunk cost : Retraining incurs additional expense.

Design compromise : Balancing old and new habits leads to suboptimal solutions.

02 Exploration of Basic Function Trigger System Design

Exploration 1: Unified Modules and Re‑engineered Trigger Logic

User layering and scenario abstraction : We mapped all basic functions, defined a core matrix, and established immutable system rules with core triggers.

Exploration 2: Entropy‑Increasing Interaction Architecture

We propose a “entropy‑increasing” architecture that balances order and disorder, keeping core functions low‑entropy while allowing extensible high‑entropy modules.

Structure characteristics

Core stability : Simple, ordered, intuitive basic functions.

Controlled complexity : Differentiated features are modular, preserving core integrity.

Progressive expansion : Gradual transition from low to high entropy avoids sudden complexity.

Exploration 3: Progressive Optimization Strategy

Gradual rollout with parallel old and new interactions, guided tutorials, and configurable modes (classic vs. regular) reduces habit disruption.

03 3D Software Trigger Design Principles

Adhering to these principles ensures stable, extensible, and user‑friendly trigger designs.

Conclusion

Robust basic‑function trigger design is essential for 3D design tools, balancing efficiency and extensibility through a low‑entropy core and high‑entropy extensions.

We continue to explore best practices to simplify complex tools.

frontendUI design3D softwareinteraction architecturetrigger system
Qunhe Technology User Experience Design
Written by

Qunhe Technology User Experience Design

Qunhe MCUX

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.