muflon docs
Users + Future Integrators
Documentation Hub

Learn, test, and prepare future integrations.

This static docs site covers practical usage for testers and users, plus forward-looking integration context for developers. It is designed as the public documentation surface for Muflon beta growth.

Tutorials

Step-by-step guides for first-time setup and repeatable testing flow.

  • 5-minute setup Install build, grant assistant role, confirm fallback capture.
  • Gesture practice loop Warm-up pattern for consistent two-swing motion per axis.
  • Beta feedback routine Submit RCA bundle + brief repro note after each issue.

Use Cases

Real scenarios where one-handed rotational gestures are useful.

  • Busy commute control Trigger assistant flow while moving through crowded transit.
  • Field inspection capture Log status events quickly without deep screen navigation.
  • Accessibility reach support Reduce repetitive thumb travel on large devices.

Ideas

Backlog-ready concepts for future user-facing expansion.

  • Gesture-to-action profiles Map each of the 6 classes to shortcuts in specific contexts.
  • Contextual sensitivity presets Per-device or per-mode threshold profiles.
  • Validation challenge packs Guided test suites for team-wide benchmarking.

Templates

Reusable templates for testing, reporting, and rollout prep.

# Bug Report Template Title: Device + Android version: Repro steps: Expected: Observed: RCA bundle attached: yes/no # Validation Session Template OEM: Setup path success rate: False positives: P50 / P95 launch latency: Notes:

Blog Posts & Release Notes

Short release logs for testers; full historical change stream remains in `CHANGELOG.md`.

2026-02-15 Pitch page aligned to app logo palette and upgraded with branded logo assets.
2026-02-15 Static docs hub launched for tutorials, use cases, templates, and integration roadmap.

Developers: Integration Roadmap

Integration docs are intentionally forward-compatible and currently focus on deterministic recognition boundaries, manual fallback guarantees, and diagnostics/reporting touchpoints.

  • Planned docs modules Event schema, invocation lifecycle, and safety/fallback contract.
  • Planned templates Integration checklist, OEM validation matrix, release-gate worksheet.
  • Planned examples Embedding assistant entry points without coupling UI to recognition logic.