Best Practices for Navigation Commands

Navigation Commands are specialized interactions designed for surfaces that do not expose traditional UI elements such as maps, custom drawings, and canvas regions. Because these gestures bypass the standard UI tree, they require precise intent, clear direction, and unambiguous context to ensure deterministic execution. This section outlines best practices to help teams use MAP_ACTION Tap and MAP_ACTION Drag reliably, avoid misfires, and maintain stability across varying map layouts and dynamic surfaces.

Recommended Best Practices for Writing Navigation Commands:

1. Provide explicit start and end directions for drag

   Example: MAP_ACTION Drag from left to right to reposition marker

2. Use intent context with map taps Example: MAP_ACTION Tap on the red pickup marker near "City Center"

3. Prefer MAP_ACTION only when element-based commands fail else for standard UI interaction, prefer tap/scroll/validate wherever possible

4. Avoid overusing navigation gestures on standard screens Reserve for canvas and map surfaces

5. Use clear directional semantics From left to right, from bottom to top, From top right to center of screen etc.