Developer

Developer tools — three jobs we actually stand behind

This hub is for a request you will run yourself, a JavaScript regex, or a Cache API worker you will host. The JSON/Base64/HTML toys in the grid below are utilities. They are not why DroidXP exists — that is Android inspection.

Decision guide

Path A — A request you will run at the desk

Fill method, URL, headers, and body. Copy bash-quoted curl or await fetch(). cmd.exe / PowerShell will mangle the quotes. CORS still exists in the browser; curl ignores it. If fetch fails and curl works, fix headers on the API with the CORS snippet generator — one origin, not an allowlist engine.

Path B — Offline / install-adjacent web

The worker generator emits vanilla Cache API: precache, network-first / cache-first / SWR. One 404 in addAll fails the whole install. HTTPS or localhost is required. A manifest is a separate JSON file; Chrome still decides whether the site is installable.

Path C — Pattern against sample text

The regex tester is new RegExp in this tab. Flags g i m s u y. Replace preview uses JavaScript $1 / $&. Nested quantifiers can still hang the tab. Paste the same pattern into Kotlin or Python and expect flavor differences.

What we keep on the shelf (and what we do not pretend)

JSON/XML formatters, Base64, URL encode, timestamps, HTML minify/beautify, snippet boilers, and storage viewers are clones of tools that exist on a thousand other domains. Use them if you are already here. Do not expect an essay. The indexed developer pages are HTTP text, regex, and the service worker.

Frequently asked questions

Does the HTTP builder send my request?

No. Copy the snippet and run it in a terminal or your app.

Is the regex engine PCRE?

No. ECMAScript only.

Which page should a reviewer open first?

The Android hub, then APK Analyzer. This hub is the adjacent web-dev desk — not the farm grid.

Indexed developer desks (3)

Read next