Use the umbrella artifact for the default setup path.
Published on Maven Central
Inspect your Android app from inside the app.
AppInspect is a clean, built-in debugging surface for Android apps. Add one dependency, open the inspector inside your app, and review network traffic, storage, WorkManager state, and runtime details without building your own internal tools UI.
Package details
Latest version → Maven Central
Group
io.github.suryansh1720001.appinspect
Artifact
appinspect
Dependency
implementation("io.github.suryansh1720001.appinspect:appinspect:<latest-version>")
Captured Calls
128
Failed Calls
7
GET
/api/v1/profile
Headers, body, response, and cURL in one place
POST
/api/v1/login
Persistent history with filter and search support
Why AppInspect
Simple integration, useful data, no extra inspector app required.
AppInspect is built for developers, QA teams, and internal testing flows. It opens a full-screen inspector from inside your host app, so you can inspect live data where issues actually happen.
No need to create your own debug screen or navigation flow.
Network, storage, WorkManager, and runtime tools in one place.
Integration
Integrate AppInspect in 3 steps
If your Android project already uses Gradle, the default path is very small. Add Maven Central, add the dependency, and wire the OkHttp interceptor if you want automatic network capture.
Kotlin DSL
dependencyResolutionManagement {
repositories {
google()
mavenCentral()
}
}
Groovy
dependencyResolutionManagement {
repositories {
google()
mavenCentral()
}
}
build.gradle.kts
dependencies {
implementation("io.github.suryansh1720001.appinspect:appinspect:<latest-version>")
}
build.gradle
dependencies {
implementation 'io.github.suryansh1720001.appinspect:appinspect:<latest-version>'
}
Default behavior after adding the dependency
- Auto-install at app startup through AndroidX Startup
- Built-in full-screen inspector activity
- Launcher shortcut and shake entry point support
- Compose and View long-press trigger helpers
OkHttp setup
val client = OkHttpClient.Builder()
.addAppInspectInterceptor()
.build()
Open the inspector
AppInspect.open(context)
Configuration
Use the defaults or install with your own settings
For most apps, the Maven Central dependency is enough. If you want custom build-tier gating, entry points, or power tools, you can install AppInspect manually with a configuration object.
Manual install example
Custom configuration
AppInspect.install(
application = application,
configuration = AppInspectConfiguration(
enablement = AppInspectEnablement(
allowedBuildTiers = linkedSetOf(AppInspectBuildTier.DEBUG),
),
entryPoints = AppInspectEntryPoints(
shakeToOpenEnabled = true,
launcherShortcutEnabled = true,
autoOpenOnLongPressTrigger = true,
),
powerTools = AppInspectPowerTools(
showRawSensitiveValues = true,
allowSharedPreferencesEditing = true,
allowDatabaseEditing = true,
allowSqlConsole = true,
),
),
)
Built-in tools
Everything your team needs in one inspector
AppInspect is network-first, but it also gives you storage, WorkManager, and runtime visibility so you can debug the full app state in one place.
Network
Capture OkHttp requests, responses, and failures with search, filtering, and cURL generation.
- Headers and bodies with formatted JSON and XML
- Persistent history across app restarts
- Copy and share tools for request and response data
Storage
Inspect SharedPreferences and host databases directly inside the running app.
- Add, edit, delete, and search preference values
- Browse schemas, rows, and table data
- Use SQL console support when your configuration allows it
WorkManager
Review work specs, tags, attempts, payloads, and scheduling metadata.
- Read-only inspection for safer debugging
- Status-focused summaries for faster scanning
- Useful for background task validation and QA flows
Runtime
See app, device, environment, and session details from one searchable surface.
- Session and environment metadata
- Searchable runtime keys and values
- Helpful for build verification and internal support checks
What the host app gets
The default setup is intentionally small
No custom inspector screen required
The built-in AppInspect activity is ready to use after integration.
Friendly for Compose and View apps
Use long-press triggers in both UI stacks without building custom plumbing.
Useful for debugging and QA
Inspect real app state from inside the same build your team is testing.
Power tools when you need them
Keep advanced editing and raw visibility behind explicit configuration flags.
Safety note
Important default behavior for sensitive data
AppInspect is designed as developer tooling. When it is enabled, raw sensitive values are visible by default unless you turn masking back on.
What to know
- Authorization headers, cookies, tokens, and payload values may be visible
- Production remains disabled by default unless the host app opts in
- Staging or non-debug rollouts should review these defaults carefully
Turn masking back on
Safer visibility setup
AppInspectConfiguration(
powerTools = AppInspectPowerTools(
showRawSensitiveValues = false,
),
)
Ready to use
Start with Maven Central, then tailor the setup only if your app needs it.
AppInspect is easiest to adopt through the published umbrella dependency. That gives your team a clean built-in inspector with room for deeper configuration later.