Adoption paths
Choose the right layer to adopt
This portal is moving from generic SDK marketing toward a library-first adoption model. Most open-source developers should start with the reusable core surfaces, then expand into loop orchestration, gesture systems, and simulation workflows.
Core Rust libraries
The best path for developers embedding Gestura deeply into their own application runtime, orchestration layer, or device-adjacent system.
Explore core librariesAgentic loop integrations
Use the loop architecture and protocol surfaces when your app needs model-driven tool use, orchestration, and multi-step execution.
Learn the loopGesture and haptic libraries
Bring taps, slides, tilt, haptics, and multimodal feedback into your application as stable events and interaction primitives.
See gesture guidanceSimulation and testing
Use the simulator and examples to validate interaction design, tool behavior, and multimodal flows before everything depends on hardware.
Open simulator docsRecommended path for open-source adopters
- Understand the public core library surface first.
- Learn the orchestration pattern that powers the agentic loop.
- Adopt gesture and haptic libraries as typed interaction inputs.
- Use generated Rustdoc for exact APIs and simulator workflows for validation.
Reference rule
Human-written portal pages should explain why and when to use something. Inline code docs should explain the exact API.
What changed in our documentation strategy
We are deliberately shifting away from treating language SDK pages as the whole story. The stronger story is: reusable libraries, clear architecture, generated reference, and practical examples that show how to implement the loop in ordinary software.