hmos-multidevice-scenario-entry

HarmonyOS multi-device adaptation for overlapping UI issues requires classifying composite signals into a primary scene plus secondary scenes. This approach routes requests involving foldable creases, keyboard avoid areas, and rotation semantics to specialized handling paths without missing key constraints.

Routing a foldable device layout issue in HarmonyOS involves categorizing the request by workflow phase (REQ, DEV, FIX, or VAL) and then selecting the fold/crease scene. This phase-first routing ensures the adaptation request reaches the correct specialized scenario definition for resolution.

Scene routing for HarmonyOS responsive UI works by evaluating phase tags and scene intent signals to classify requests. It outputs structured metadata including active phases, primary scene, secondary scenes, and route reasons to direct layout and window size issues to the correct handling path.

Yes, you can use scene routing for HarmonyOS hardware capability differences and interaction methods. The routing mechanism categorizes these multi-device adaptation requests into specific scenes, applying consistent structured output to identify the correct specialized scenario definition.

You need to classify multiple secondary scenes for HarmonyOS multi-device adaptation when multiple signals are present in the request. Composite handling outputs a primary scene plus one or two secondary scenes to ensure constraints like avoid areas, keyboard behavior, and rotation semantics are all addressed.

HarmonyOS multi-device adaptation requests need phase-first routing to categorize the current workflow phase (REQ, DEV, FIX, VAL) before scene selection. This ensures the adaptation process correctly identifies the problem type and applies the appropriate phase-specific handling path.