DoKit is an Apache-2.0 efficiency platform for the full research-and-development lifecycle of pan-frontend products — Android, iOS, mini programs, Flutter and Web — built for mobile developers, test engineers and UI designers who want debugging, performance-monitoring and visual-inspection tooling inside a debug build instead of hand-rolled into each application.

What it is

DoKit was created inside Didi's 城运服体验技术部 and has grown into a relatively complete ecosystem: DoKit For Android, DoKit For iOS, DoKit For 小程序, DoKit For Flutter and DoKit For Web. The project is written in Java and released under the Apache-2.0 licence. With the launch of the www.dokit.cn platform, DoKit moved from being a single efficiency tool into an efficiency tool platform that extends each client through 接口 Mock, 健康体检, 文件同步助手 and 一机多控.

The concrete problem is duplication. Almost every app of moderate size ships its own offline test code — environment switching, frame-rate viewing — with entries hidden behind special gestures, a double-tap on the status bar, a dedicated keyWindow kept above the app, or similar private conventions. Those modules are largely similar across applications, yet each team reimplements them separately. DoKit replaces that scattered, per-app debug scaffolding with one integrated set of tools presented in a Doraemon panel, into which teams can also plug their own business-coupled auxiliary tools.

Key capabilities

• A hosted platform layer at www.dokit.cn providing 数据 Mock through App network interception without code changes, 健康体检 integrated diagnostics with data visualization, 文件同步助手 for terminal file and database operations, and 一机多控 master-slave device synchronisation.
• A 性能检测 suite covering 帧率, CPU and 内存 as waveform charts, 流量监控 with overview, list, filtering and detail views, plus 卡顿 stack capture, 大图检测, 启动耗时, UI层级检查, 函数耗时, 内存泄漏 and, on iOS, Load analysis.
• A 视觉工具 set for design review: 颜色吸管 for sampling component colours, 组件检查 for control name, position, background colour and font metrics, 对齐标尺 for screen coordinates and alignment, and 元素边框线 for drawing UI component borders.
• Common tools including App 信息查看, 沙盒浏览 with AirDrop and other share-based upload to a PC, H5任意门 for loading arbitrary H5 addresses, Crash查看, DBView for operating the in-app database over a web page, and MockGPS with map selection or manual latitude and longitude entry.
• Platform-specific utilities such as 模拟弱网 on Android, and on iOS 子线程UI, NSLog output to the UI, Lumberjack log display and JS脚本 execution inside a specified WebView.
• Weex专项工具 and CML专项工具: console log viewing with leveling and search, storage cache visualization, container information and performance data, and a scan entry for Weex DevTool.
• Support for integrating custom business tools directly into the Doraemon panel.

Who uses it and how

• Teams maintaining products across several frontends adopt the same panel conventions for Android, iOS, mini programs, Flutter and Web, rather than rebuilding equivalent tooling per platform.
• The README states the project is widely used by BAT companies as well as by Didi, ByteDance, Kuaishou and JD.
• Test engineers use 健康体检 to run multiple DoKit tools in one action, and 一机多控 to drive several devices from a master device and reduce manual repetition.
• Designers and UI reviewers use 颜色吸管, 组件检查 and 对齐标尺 to verify colour values, control geometry and alignment during interface checks.
• Teams with existing business-coupled debug tools keep them and register them in the Doraemon panel, while 沙盒浏览 and 文件同步助手 give file and database access from the terminal.

Getting started

Integration is per platform and follows the official manuals published on the DoKit website at www.dokit.cn, reached through the 使用中心 documentation at xingyun.xiaojukeji.com/docs/dokit. There is no single install command: each client — Android, iOS, mini program, Flutter or Web — is added separately under its own guide and release notes.

How it compares

Among the tools named in the supplied material, the closest point of reference is Charles: DoKit's 流量监控 intercepts App internal traffic and presents it as a built-in "Charles" for the device. The README also points to Didi's Chameleon as a cross-end companion scheme, so DoKit sits alongside an in-app proxy-style traffic inspector and a cross-platform development framework rather than replacing a paid commercial product.

When to use it — and when not to

DoKit is debug-only: the README states that all functions target the Debug environment, that Release behaviour is unverified, and that the official project accepts no responsibility if a team chooses to ship it in Release. A self-hoster therefore operates per-platform integrations for Android, iOS, mini programs, Flutter and Web, and must keep the debug-only boundary enforced in build configuration. The documentation is Chinese-first with an English README, release notes are split across Android, iOS, mini program and Flutter files, and 275 open issues were recorded at last update; teams wanting production-side monitoring should not pick it for that purpose.