Blog
Product notes, guides, and DevPeek workflows.
Why We Built DevPeek
- Why We Built DevPeekRecommended
Why We Built DevPeek (1): HTTPS Decrypted, Body Still Gibberish
The night before a release, TLS was already open—but changing one request field still meant digging up encrypt/decrypt scripts. That pushed us toward a proxy tool with business-layer crypto built in—and DevPeek started there.
Read more - Why We Built DevPeekRecommended
Why We Built DevPeek (2): That H5 Page in the App—Debug It on Your PC
Param transform fixed login, but the activity H5 only broke inside the App WebView. Remote debug and capture lived in different windows—so we folded mirroring and our own debug panels into DevPeek.
Read more
H5 Debug in Practice
- H5 Debug in PracticeRecommended
H5 Debug in Practice (1): WeChat H5 Local Cache—Debug It on Desktop
After switching test accounts in a WeChat official-account H5, the avatar still showed the old user—capture had the new token, stale data stayed in localStorage. This post walks through a real joint-debug case and how to view and edit localStorage, sessionStorage, and IndexedDB in WeChat WebView from your PC.
Read more - H5 Debug in PracticeRecommended
H5 Debug in Practice (2): Android WebView White Screen—From Console Remote Debug to Mock Validation
A campaign H5 white-screened on some Android devices after a button tap—all requests returned 200, but the page showed nothing. Using DevPeek Console to capture WebView runtime logs, remote eval to confirm a polyfill override, then Mock to verify the fallback UI under error conditions.
Read more
API Debugging New Tricks
- API Debugging New Tricks
H5 API Encrypted? Decrypt It On the Fly with DevPeek
Stuck with AES-encrypted API params during integration? Set the key and IV once in DevPeek Param Transform, and see plaintext automatically — you can even edit and re-encrypt on resend.
Read more - API Debugging New Tricks
New API Is Live, Frontend Hasn't Shipped? Debug with Forward Rules
After a service split, the frontend still hits the old API while orders already live on the new service. DevPeek Forward Rules forward specific endpoints to the new host without code changes; if the new service isn't ready, Mock gets the page working first.
Read more
Dev Build Log
- Dev Build Log
Why We Moved Capture History from sql.js to Native SQLite
Early DevPeek stored captures in JavaScript-based SQLite (sql.js); busy sessions ate RAM and stuttered the list. Native SQLite keeps memory flat so the proxy can run all day.
Read more - Dev Build Log
DevPeek Architecture: Dropping Electron for Tauri
A debugging proxy shouldn't ship a whole Chromium just to open a window. We moved business logic into Core and swapped the desktop shell for Tauri—lighter installs, leaner background use, and the tray brings the UI back after you close the window.
Read more - Dev Build Log
Why We Designed a WebSocket Mock DSL Instead of YAML, JSON, or JS
Lightweight WebSocket Mock shouldn't feel heavier than HTTP Mock. YAML, JSON, and JS all work—but they're wordy for connect, login, heartbeat. We built a short DSL to keep lightweight Mock light.
Read more