DoKit One‑Machine‑Multi‑Control: Principles, Usage Scenarios and Open‑Source Plans

Background: The proliferation of cross-platform development frameworks has boosted R&D efficiency but increased pressure on quality assurance teams, which need more efficient functional regression and device compatibility testing.

In response, the DoKit team explored a “one‑machine‑multi‑control” solution that allows a host device to control slave devices over a local network without extra system permissions or a PC, while keeping business code non‑intrusive.

Stage results show that DoKit Android’s one‑machine‑multi‑control works without additional privileges, requires only that host and slave be on the same LAN, and preserves zero intrusion of business code.

Principle: The implementation consists of three steps – Android host widget path relative to window , LAN‑based long‑connection transfer of widget information , and slave‑side widget location and gesture simulation . A key breakthrough came from the Android framework API View#sendAccessibilityEventUnchecked .

Usage scenarios: Besides improving regression and compatibility testing efficiency, the technique enables global user‑behavior path‑less embedding, user behavior recording and playback (combined with interface mocking to ensure UI consistency), and can be extended to other imaginative features.

Open‑source plan: The core one‑machine‑multi‑control function on Android is already functional; the team is coordinating business validation and will prepare open‑source release afterward, or at least publish it as a learning practice if business value is not realized.

Continuous innovation: DoKit defines itself as a creativity‑intensive efficiency platform; most time is spent on research, value assessment, and technical validation, with close communication to business and community to avoid reinventing wheels and to iterate on existing open‑source solutions.

Future roadmap: After stabilizing terminal features, DoKit aims to expand into new domains such as DoKit for Flutter and DoKit for Web, welcoming community contributions.

Conclusion: DoKit continues to strive for the most convenient and intuitive developer experience, welcoming open‑source community participation and contributions via GitHub at https://github.com/didi/DoraemonKit.