🐾 About the Project – Tabby: Your Smart Browser Companion
💡 Inspiration
The idea for Tabby came from the frustration of managing 20+ open browser tabs.
The core question was:
“What if your browser could actually understand your tabs and help you create content within them?”
Tabby is built on a dual-layer strategy:
- It features smart algorithms for reliable tab management.
- It includes a fully integrated framework for four key AI APIs.
This ensures the extension provides immediate value while staying ready for advanced AI-powered features.
🛠️ How It Was Built
As my first Chrome extension, the initial challenge was understanding the Manifest V3 structure.
My main focus was designing a system that could securely and efficiently handle the four core AI services:
- ✍️ Write API: Generates draft content.
- 🔁 Rewrite API: Instantly paraphrases or changes tone.
- 💬 Prompt API: Executes custom generative AI commands.
- 📝 Proofread API: Performs quick grammar and spelling checks.
The API tokens are securely integrated into the background script, enabling authenticated requests even though full live testing is still in progress.
I relied heavily on online documentation and Gemini for guidance throughout the development process.
⚙️ Core Architecture
- Popup Interface: User controls for search and quick actions.
- Background Script: Manages tab data and events, runs smart algorithms, and acts as the secure message broker and API authentication layer.
- Content Script: Injects editing functionality (Write, Rewrite, Proofread APIs) into the active tab’s context.
🧠 What I Learned
- API Integration Complexity: Initially, I thought APIs would just “plug and play.” I learned how challenging it is to manage asynchronous data flow, secure token handling, and message passing between scripts.
- Manifest V3 Mastery: Overcame the steep learning curve of Chrome’s new security model and script communication system.
- Algorithmic Design: Built reliable, local features like contextual search and idle tab detection that ensure the extension works smoothly, even without active APIs.
⚡ Challenges Faced
- Building a secure, asynchronous communication layer under Manifest V3’s strict security model.
- Structuring how Content Scripts communicate with Background Scripts for external API calls.
- Initial confusion on where to start, plus debugging permissions and event scripts during testing.
🚀 Current & Future Vision
✅ What Tabby Does Now
- API Framework Complete: Write, Rewrite, Prompt, and Proofread APIs integrated and token-ready.
- Smart Local Functionality:
- Finds tabs by title or context.
- Suggests closing idle or unused tabs.
- Offers a clean, responsive interface.
- Finds tabs by title or context.
🔮 What’s Next
- Full live deployment and testing of all API features.
- Automatic tab grouping and AI-based prioritization by content.
- Integration with Gemini Nano for on-device, low-latency tasks.
🧮 Simple Technical Model
$$ \text{Tabby} = f(\text{Popup}, \text{Background}, \text{Content Script}, \text{4 AI APIs}) \Rightarrow \text{Smarter Browsing and Content Creation} $$
Tabby – Find, Focus, and Flow. 🐾
Built With
- chromeexrentionapi
- css3
- dom
- html5
- javascript
- json
Log in or sign up for Devpost to join the conversation.