Skip to content

Redesign Android inspector and web dashboard; make security layers opt-in - #55

Merged
nur-shuvo merged 1 commit into
mainfrom
redesign/e-theme
Oct 19, 2026
Merged

nur-shuvo merged 1 commit into
mainfrom
redesign/e-theme

Conversation

@Shakibuzzaman3104

Copy link
Copy Markdown
Collaborator

Summary

Android inspector (Compose)

  • Flat graphite redesign: flush grouped rows, hairlines, compact type; signal green only for selection and live state.
  • Detail screens get tabs (Overview, Request, Response, Headers, Timing); data sources open as sub-screens; illustrated empty states.
  • Custom bottom navigation bar that does not recompose every animation frame, and content capture is paused while the inspector is in front (about a third less CPU when switching tabs on a Pixel 6).

Web dashboard

  • Same design language; secondary details move into collapsible folds.
  • Network view: side inspector layout, request list can be hidden and reopened as an overlay ([), one "Status · time" column, optional full endpoint.
  • Copy and empty states no longer mention redaction unless it is enabled.

Security layers are opt-in (DevConsole stays debug-only)

  • RedactionPolicy.default() is none(); recommended() keeps the previous rules.
  • New NetworkProtection (rate limiting, Host/Origin checks), off by default; NetworkProtection.recommended() turns both on.
  • Editing capabilities, Composer, state mutations and screenshots are on by default.
  • Composer: an empty composerAllowedHosts permits any host, and hosts added from the dashboard never narrow it (anyHost in GET /api/v1/composer/hosts). When the app lists hosts, composerHostsEditable (now on by default) lets the dashboard add more.
  • /api/v1/meta reports redaction.enabled and networkProtection.
  • docs/MIGRATION.md lists every changed default and how to restore it. SESSION_CODE authentication, CSRF and code-attempt limits are unchanged when selected.

Builds on #53 (private composer): its new routes and the agent follow the same opt-in defaults, and its tests that need the strict posture use a shared protected test fixture.

Verification

  • ./gradlew test testDebugUnitTest ktlintCheck detekt apiCheck passes.
  • Maestro suite on a Pixel 6: 7/7 flows pass (seed traffic, Observe tabs/search/filter, request detail tabs, Control, Data, More, theme switch).
  • Web dashboard checked in headless Chrome at 1440 and 390 px, dark and light, with no console errors or horizontal scroll.
  • Composer on device: a request to an unlisted host succeeds with no allowlist configured.

…t-in

Android inspector (Compose)
- Restyle to the flat graphite design: flush grouped rows, hairlines, compact type,
  signal green only for selection and live state
- Detail screens get tabs (Overview, Request, Response, Headers, Timing)
- Data sources open as sub-screens; empty states get illustrated spots
- Custom bottom navigation bar without per-frame recomposition; pause content
  capture while the inspector is in front (about 1/3 less CPU on tab switches)

Web dashboard
- Same design language; secondary details move into folds
- Network view: side inspector layout with a collapsible request list that opens
  as an overlay, a single "Status · time" column and a "Full endpoint" toggle
- Empty states and copy no longer imply redaction unless it is enabled

Security is opt-in
- RedactionPolicy.default() is none(); recommended() keeps the previous rules
- New NetworkProtection (rate limiting, Host/Origin checks), off by default
- Editing capabilities, Composer, state mutations and screenshots on by default
- An empty composerAllowedHosts permits any host; session hosts never narrow it
  (anyHost in GET /api/v1/composer/hosts); composerHostsEditable defaults to true
- /api/v1/meta reports redaction.enabled and networkProtection
- MIGRATION.md lists every changed default and how to restore it

Also fixes the detekt/ktlint findings and refreshes the API dumps.
@nur-shuvo
nur-shuvo merged commit 10b7b52 into main Oct 19, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants