explaingit

didi/dokit

20,417JavaAudience · developerComplexity · 3/5QuietLicenseSetup · moderate

TLDR

A floating debugging panel for mobile apps that gives developers instant access to GPS spoofing, crash logs, network monitoring, performance charts, and custom testing tools, all without leaving the device.

Mindmap

mindmap
  root((DoKit))
    What it does
      Floating debug panel
      GPS spoofing
      Crash log viewer
    Platforms supported
      Android
      iOS
      Flutter
      WeChat mini-programs
    Tool categories
      Performance monitoring
      Network inspection
      Visual design tools
      Custom business tools
    Companion features
      Web dashboard
      API mocking
      Multi-device control
    Use cases
      QA testing
      Performance debugging
      Design inspection

Things people build with this

USE CASE 1

Test your app's behavior at different GPS locations without physically traveling.

USE CASE 2

Monitor real-time CPU, memory, and frame rate performance directly on a device during development.

USE CASE 3

Inspect exact color values, font sizes, and UI element alignment without design tools.

USE CASE 4

Mock API responses and coordinate test runs across multiple phones from a web dashboard.

Tech stack

JavaAndroidiOSFlutterWeChat

Getting it running

Difficulty · moderate Time to first run · 30min

Requires Android SDK/emulator or physical device to see the floating panel in action.

Use freely for any purpose including commercial. Keep the notice and disclose changes to the patent grant.

In plain English

DoKit is an efficiency platform for mobile app developers, created by Didi (the Chinese ride-hailing company). It provides a collection of debugging and testing tools that appear as a floating panel inside your app during development, so teams can diagnose problems directly on a device without needing to connect to a computer or wade through project source code. The platform supports Android, iOS, WeChat mini-programs, and Flutter apps. Once integrated, developers get access to roughly four categories of tools. Common utilities include GPS spoofing (faking the device's location anywhere in the country), a sandbox file browser, crash log viewer, network traffic monitor, and one-tap access to developer options. Performance tools display real-time charts for frame rate, CPU usage, memory consumption, and network traffic, and can detect oversized images or UI rendering happening on background threads. Visual tools let designers inspect the exact color values, font sizes, and alignment of any element on screen. There is also support for plugging in custom business-specific tools so teams can manage all their testing code from one central panel. A companion web platform at dokit.cn extends what the device-side tools can do: it offers API response mocking without touching code, a health-check dashboard that pulls together multiple tool readings, file synchronization between the device and a desktop, and a multi-device control mode for coordinating test runs across phones. DoKit is intended for the debug build of an app only; the maintainers explicitly warn against using it in production releases. It is aimed at development and QA teams working on apps of any size who want to stop re-implementing the same testing utilities project after project.

Copy-paste prompts

Prompt 1
How do I integrate DoKit into my Android app to get a floating debug panel with GPS spoofing and crash logs?
Prompt 2
Show me how to use DoKit's performance monitoring to detect frame rate drops and background thread UI rendering issues.
Prompt 3
How can I set up custom business-specific tools in DoKit so my QA team can manage all testing utilities from one panel?
Prompt 4
What's the workflow for using DoKit's web platform to mock API responses and control multiple test devices at once?
Open on GitHub → Explain another repo

Generated 2026-05-18 · Model: sonnet-4-6 · Verify against the repo before relying on details.