TabDog

Product Introduction

1. Definition: TabDog is an open-source macOS menu bar utility (technical category: system productivity tool) that bridges Google Chrome/Brave browser tabs and macOS application windows into a unified searchable interface. It leverages Chrome's Native Messaging API and SwiftUI for real-time data synchronization.
2. Core Value Proposition: TabDog eliminates tab/window overload by enabling instant keyboard-driven search, navigation, and closure of browser tabs/apps. Primary keywords: macOS tab manager, Chrome tab search, keyboard productivity tool, menu bar app.

Main Features

1. Unified Tab & App Search:

   • How it works: Aggregates all open Chrome/Brave tabs (title, URL) and macOS windows (app name) into a single searchable menu bar interface. Uses Chrome's tabs API and macOS NSWorkspace for real-time data.
   • Technology: SwiftUI for rendering, JSON-based Native Messaging (stdin/stdout) for Chrome ↔ macOS communication.

2. Keyboard-Centric Navigation:

   • How it works: Press Tab to toggle between Browser Tabs and Windows modes. Use ↑/↓ arrows to navigate, Enter to activate, C to close tabs/windows, H to hide apps.
   • Technology: Swift KeyboardShortcuts library for low-latency key binding detection.

3. Memory-Optimized Tab Management:

   • How it works: Groups tabs by domain (e.g., github.com/*) to identify resource-heavy sites. Sort by recency/oldest to prioritize relevant tabs.
   • Technology: URL domain parsing via Swift Foundation; Chrome processes API for memory tracking (future update).

4. Session Recovery Tools:

   • How it works: "Recently Closed" restores Chrome tabs; "Recently Quit" relaunches macOS apps. Caches data locally for 24h.
   • Technology: Chrome sessions API for tab recovery; UserDefaults for macOS app state persistence.

Problems Solved

1. Pain Point: Eliminates manual tab/window hunting across dozens of browser instances and apps—saving 5–15 seconds per switch. Keywords: too many Chrome tabs, lost window, context switching delay.
2. Target Audience:
   • Developers juggling 50+ documentation/Stack Overflow tabs.
   • Researchers managing 20+ articles/data dashboards.
   • Freelancers multitasking between design tools and browsers.
3. Use Cases:
   • Close memory-heavy YouTube/Spotify tabs without switching windows.
   • Instantly jump from VS Code to a specific GitHub PR tab via keyboard.
   • Reopen accidentally closed Figma/Chrome windows after crashes.

Unique Advantages

1. Differentiation:
   • Vs. Alfred/Raycast: Native Chrome integration (no manual setup).
   • Vs. Tab Manager Extensions: Controls macOS apps (Slack, Figma), not just browser tabs.
   • Vs. Electron Apps: SwiftUI ensures <50ms response time; 10x lighter memory footprint.
2. Key Innovation:
   • Native Messaging Bridge: Only open-source tool using Chrome’s Native Messaging protocol for secure, real-time tab data sync (no remote servers).
   • Zero-Config Grouping: Auto-domain grouping unlike manual setups in competitors.

Frequently Asked Questions (FAQ)

1. Does TabDog work with Brave or Edge?
   Yes. Compatible with all Chromium-based browsers supporting Native Messaging (Brave, Edge, Vivaldi).

2. Is TabDog secure for accessing my tabs?
   Absolutely. All data stays local—no cloud servers. Communication is encrypted via Chrome’s Native Messaging protocol.

3. Can I use TabDog without the Chrome extension?
   No. The extension enables tab data access. The macOS app alone manages only non-browser apps.

4. How does TabDog impact battery life?
   Negligible. SwiftUI optimizations limit CPU usage to <1% during searches; idle state consumes 0% resources.

5. Does TabDog support Firefox or Safari?
   Not currently. Limited to Chromium browsers due to Native Messaging dependencies.