v2.3.1 — Stable

Debug everything.
Ship nothing.

The all-in-one Android debugging toolkit with 23 features, zero release build risk, and no desktop app required.

23
Features
49
Modules
0KB
In Release APK

See it in action

One toolkit. Every debug tool you need.

Replace multiple debug libraries with one. Explore by category.

HTTP/HTTPS Inspector

Full request/response capture with headers, body, timing, and TLS info. Syntax-highlighted JSON/XML.

OkHttp + Ktor

Native interceptor for OkHttp and a Ktor client plugin. Both with the same feature set.

cURL & JSON Export

Export any captured request as cURL or JSON to share with your backend team.

Network features screenshot

See all features and toggles →

Physically impossible to ship debug code.

Other tools rely on ProGuard rules or runtime flags. WormaCeptor uses Gradle’s debugImplementation — the code literally does not exist in your release APK.

Debug APK

Full power
wormaceptor-client
wormaceptor-persistence
23 feature modules
Full Compose UI

Release APK

~8KB
wormaceptor-client
wormaceptor-persistence
23 feature modules
Full debug UI

The code doesn’t exist in release. Not disabled. Not hidden. Gone.

Three steps to full debugging.

Add the dependency. Init. Intercept. That’s it.

1

Add dependencies

build.gradle.kts
dependencies {
    implementation("com.azikar24.wormaceptor:wormaceptor-client:2.3.1")
    debugImplementation("com.azikar24.wormaceptor:wormaceptor-persistence:2.3.1")
}
2

Initialize

Application.kt
class MyApp : Application() {
    override fun onCreate() {
        super.onCreate()
        WormaCeptorApi.init(this)
    }
}
3

Add interceptor

OkHttp — NetworkModule.kt
val client = OkHttpClient.Builder()
    .addInterceptor(WormaCeptorInterceptor())
    .build()
Ktor — KtorClient.kt
val client = HttpClient(CIO) {
    install(WormaCeptorKtorPlugin)
}

How WormaCeptor compares.

WormaCeptor extends beyond network inspection. Chucker is excellent at HTTP traffic — WormaCeptor covers the rest.

FeatureChuckerWormaCeptor
Network InspectionHTTP onlyHTTP + WebSocket + WebView
HTTP Client SupportOkHttpOkHttp + Ktor (native)
Release SafetyProGuard no-opPhysical debugImplementation
Performance MonitorFPS + Memory + CPU overlay
SQLite BrowserBuilt-in with query execution
SharedPreferencesBuilt-in viewer & editor
Leak DetectionBuilt-in (Activities/Fragments)
Crash ReportingIntegrated with stack traces
Push SimulatorSimulated notifications with FCM-like payloads
Location MockingMock location via Android provider API
Deep Linkswormaceptor:// to every tool
Feature Toggles22 toggleable features
Tech StackPartial Kotlin / XML Views100% Kotlin + Jetpack Compose

Built for real debugging workflows.

Real scenarios Android developers face every day.

“Why is this API call slow?”

  • Open WormaCeptor via shake, floating button, or deep link
  • Filter transactions by endpoint
  • See timing breakdown, headers, and full response
  • Export as cURL and share with backend

“The app is janking during scroll.”

  • Enable the performance overlay
  • Watch FPS drop in real time on screen
  • Cross-reference with memory and CPU usage
  • Check thread violations for main-thread work

“QA found a crash on this device.”

  • Open the Crashes tab on QA’s device
  • See the full stack trace with line numbers
  • Check network transactions around that time
  • Review console logs for context leading up to it

“How does this behave on slow network?”

  • Open the Rate Limiter and pick a 3G preset
  • Use the app and watch requests throttle in real time
  • Simulate a push notification to test offline handling
  • Mock a GPS location to verify location-aware features

Frequently asked questions

Yes. WormaCeptor is open source under the MIT license — free for personal and commercial use. It has zero cost and zero release build impact.
WormaCeptor supports API 23+ (Android 6.0 and above), covering approximately 95% of active Android devices worldwide.
Yes. Both can coexist in the same project as OkHttp interceptors. Migrate incrementally and remove Chucker when you're ready. See the migration guide for step-by-step instructions.
No. WormaCeptor's UI is built with Compose internally, but your app can use XML Views, Compose, or both. There is no dependency on your UI toolkit.
WormaCeptor is a comprehensive alternative to Chucker. While Chucker only provides HTTP traffic inspection, WormaCeptor offers 23 debugging features including network inspection (HTTP, WebSocket, WebView), performance monitoring, crash reporting, leak detection, SQLite browser, and more — all in a single library.
Unlike Flipper, WormaCeptor runs entirely on-device with no desktop app required. Flipper needs a desktop companion app and USB connection. WormaCeptor provides 23 features out of the box, is built with Kotlin and Jetpack Compose, and adds 0 KB to release builds.
Yes. WormaCeptor provides a native Ktor plugin in addition to the OkHttp interceptor. It supports both OkHttp 4.x and Ktor 3.x, making it the only Android debugging toolkit with native support for both HTTP clients.
WormaCeptor uses Android's debugImplementation Gradle configuration, meaning the debug code is physically absent from release builds. Unlike Chucker's ProGuard no-op approach, there are no runtime flags or rules to misconfigure — the code simply doesn't exist in production APKs, resulting in 0 KB impact.
Yes. WormaCeptor includes built-in WebSocket monitoring that captures frames, connection lifecycle events, and errors in real time. This is a feature not available in Chucker or most other Android debugging tools.
Install WormaCeptor via Gradle, add the OkHttp interceptor to your client, and launch the on-device UI via shake gesture, floating button, notification, or deep link. All request/response data including headers, body, timing, and cURL export is available directly on the device — no USB, no proxy, no desktop app needed.
Yes. WormaCeptor includes built-in leak detection for Activities and Fragments, similar to LeakCanary. Combined with crash reporting, performance monitoring, and network inspection, it replaces multiple debug libraries with one dependency.
Absolutely. WormaCeptor is added via debugImplementation only, so it is physically excluded from release builds. The wormaceptor-client module included in all builds contains only lightweight interfaces that automatically fall back to no-op when no debug implementation is present. Zero code, zero risk in production.

One dependency. 23 tools. Zero risk.

Replace your debug stack.

Stop juggling multiple debug libraries and custom menus. One dependency covers everything.

MIT Licensed · API 23+ · 100% Kotlin