Case Study • Chrome Extension

BUG
SPOON.

Engineering a surgical tool for the modern network stack.

As applications grow in complexity, the standard browser network tab becomes a firehose of data. I built BugSpoon to solve the "noise problem" in modern web development.

View Repository
manifest-v3.json
Role
Core Architect
Architecture
Event-Driven
Platform
Manifest V3
Stack
JS • Extension APIs

The Context.

Every great developer tool starts with a personal frustration. For me, it was the chaos of the Network tab during high-stakes debugging sessions. When you're tracking a specific race condition across multiple microservices, the standard "filter" just doesn't cut it.

I found myself repeating the same filtering patterns every single morning. The friction wasn't just annoying; it was a cognitive tax on my engineering flow. I needed something that felt less like a generic browser feature and more like a dedicated workstation for network analysis.

"We spend 40% of our time debugging. If we can optimize the tools we use, we reclaim our most valuable asset: focus."

The Execution.

Building for the browser environment requires a deep understanding of asynchronous event loops and the specific constraints of the Chrome Extension Manifest V3. Here's how I approached the core engineering challenges.

Performance

Zero-Latency Filtering

I implemented a high-performance filtering engine that hooks directly into the `chrome.webRequest` and `chrome.devtools.network` APIs. This ensures that even with 1000+ requests per minute, the UI remains fluid and responsive.

Architecture

Isolated Execution

Using Service Workers and background scripts, BugSpoon operates in its own execution context. It never interferes with the host page's DOM or performance, maintaining a strict separation of concerns.

UX Design

Visual Hierarchy

Instead of a flat list, I designed a layout that prioritizes 'Actionable Data'. Large status codes, clear endpoint groupings, and immediate access to headers make it easy to spot anomalies at a glance.

Workflow

Instant Replay

The ability to 'capture' a specific network state and persist it across refreshes was a key requirement. I leveraged local storage and session APIs to create a persistent debugging state.

The Deep Dive.

Transitioning to Manifest V3 wasn't just about compliance; it was about security. I moved the core logic to Service Workers to ensure a non-blocking background process.

The communication between the DevTools panel and the background script uses a robust Long-Polling Port system, ensuring real-time updates without dropping frames or request data.

Manifest V3Service WorkersLong-PollingEvent ListenersDevTools Protocol
// Manifest V3 Architecture
chrome.runtime.onConnect.addListener((port) => {
if (port.name !== 'bugspoon-panel') return;
port.onMessage.addListener((msg) => {
// High-speed data relay
handleNetworkStream(msg);
});
});

Engineering for Engineers.

BugSpoon isn't just about code; it's about empathy for the developer experience. It's a reminder that we have the power to fix our own frustrations.

Ready to build something extraordinary?

raj@myselfraj.com

This portfolio is built with

Next.jsReactTypeScriptTailwind CSSFramer MotionSanity CMSLenis Smooth ScrollVercel

© 2026 RAJNEESH — ALL RIGHTS RESERVED