Indi Mapper - Developer Tool

Developer tool for QA and debugging: Map UI elements to API network calls. For developers and QA teams only.

# Indi — Your Friendly DevTools Sidekick Meet Blobi 🟣 — a little purple blob that lives in your DevTools and actually *wants* you to have a good day at work. Indi is a Chrome DevTools extension that monitors your API calls, catches problems before your users do, and celebrates when everything's running smooth. Because debugging doesn't have to feel like punishment. --- ## What You Get **Summary Panel** Open Indi and get the full picture instantly — total API time, call count, average response, security findings, and a Quick Win suggestion if something can be faster. No digging through 200 network rows. **Network Monitor** Every API call your app makes, captured and organized. See method, status, timing, and full request/response details. Search, filter, copy as cURL, pop out for a closer look, or replay any call with one click. **BlobiMan — Your Built-In API Tester** Think Postman, but already inside your DevTools. Pick any recent call or enter a custom URL, edit headers, tweak the body, hit Send. No switching apps, no re-entering auth tokens, no context lost. It's all right there. **Blobi's Console** Console errors matched to the API calls that caused them. No more flipping between Network and Console tabs trying to figure out which error belongs to which request. **Quick Wins** Indi spots slow calls and tells you exactly what to fix. "This call takes 1.7s. Your target: 1.0s. Fix this → save 0.7s. Your users will get their data 1.7x faster." Actionable, specific, zero fluff. **Indi Flows** Record entire user journeys — login → browse → checkout — and see every API call along the way. Replay them for regression testing, share with your team, or keep them as living documentation. **Blobi Indicators** Drop visual markers directly on page elements. Click a button, see which API it calls, what came back, and whether it worked. Debug in context, not in a separate tab. --- ## Who Is This For? **Frontend devs** who are tired of the Network tab guessing game. **Backend devs** who want to see exactly how the frontend calls their APIs. **QA engineers** who need to file bug reports with actual request/response evidence. **Full-stack devs** who want end-to-end visibility from click to response. **Teams** who want a shared debugging language and faster onboarding. --- ## Why Blobi? Most dev tools treat you like a machine. Indi doesn't. Blobi is there when things go well ("You're crushing it! All systems green 💚") and when they don't ("Caught 3 issues — here's what happened"). It's a small thing, but after 8 hours of debugging, a little encouragement goes a long way. --- ## Free Tier — Not a Demo, Actually Useful - Full network monitoring - BlobiMan API tester - Console error tracking - Quick Win suggestions - Security insights - Blobi indicators - 5 recorded flows per domain **Indi Pro** (coming soon): unlimited flows, team features, Jira integration, and more. --- ## Privacy & Security All your data stays in your browser. Period. No tracking, no analytics, no server uploads. Indi uses the Chrome DevTools Protocol (same as Chrome DevTools itself) and only activates when you tell it to. Nothing runs in the background. --- ## Permissions — Why We Need Them We know elevated permissions look scary. Here's the honest breakdown: **debugger** — This is how Indi intercepts network traffic. Same API that Chrome DevTools uses. Only active when you click Record or Create Indicator. Tab-specific, never background. **all_urls** — Dev tools need to work on localhost:3000, staging.company.com, and everywhere else you code. We can't predict your URLs. **unlimitedStorage** — A single debugging session can capture megabytes of API responses. Chrome's default 5MB isn't enough. **webRequest** — Works alongside the debugger for complete network coverage. **desktopCapture** — Optional. Only used if you record your screen for bug reports. --- ## Getting Started 1. Install Indi 2. Look for Blobi 🟣 in the bottom-right corner of your browser 3. Click him — that's your command center 4. Configure once: tell Blobi your backend URL so he knows which calls to watch 5. Start monitoring, create indicators, launch BlobiMan, record flows — all from Blobi 5. Want more detail? Open DevTools (F12) and find the "Indi" tab for the full panel view That's it. No config, no setup, no account needed. Blobi's ready when you are. --- ## System Requirements Chrome 88+ (also works on Edge, Brave, Opera — not officially supported). Windows, macOS, or Linux. --- ## Talk to Us Got feedback, bugs, or feature ideas? 📧 [email protected] 🌐 www.indimapper.com We're a small team building this because we use it ourselves every day. Every email gets read. --- *Indi is a professional developer tool. Use on applications you own or have permission to debug.*