Hi HN! I built Tab-it to solve my own tab management problem.
*The problem:* I regularly have 50-100 tabs open across work, research, social media, and videos. Finding anything was impossible, and I'd lose important tabs to crashes.
*What Tab-it does:*
- Auto-groups tabs by type (Videos, Social, Shopping, Work, etc.) or domain
- Save entire tab sessions (perfect for context switching between projects)
- Restore sessions anytime
- Keyboard shortcuts for flow state
- Privacy-first: all data stored locally, no tracking, no servers
*Tech details:*
- Vanilla JavaScript (no frameworks - wanted to learn the fundamentals)
- Chrome Extension Manifest V3
- Uses Chrome's native tab groups API
- ~2000 lines of code
- All client-side, no backend
*Why vanilla JS?* Wanted to deeply understand browser APIs and state management before adding framework complexity. Learned a ton about event-driven architecture and DOM manipulation.
I'm a solo dev and this is my first Chrome extension. Feedback very welcome!
Hi HN! I built Tab-it to solve my own tab management problem.
*The problem:* I regularly have 50-100 tabs open across work, research, social media, and videos. Finding anything was impossible, and I'd lose important tabs to crashes.
*What Tab-it does:* - Auto-groups tabs by type (Videos, Social, Shopping, Work, etc.) or domain - Save entire tab sessions (perfect for context switching between projects) - Restore sessions anytime - Keyboard shortcuts for flow state - Privacy-first: all data stored locally, no tracking, no servers
*Tech details:* - Vanilla JavaScript (no frameworks - wanted to learn the fundamentals) - Chrome Extension Manifest V3 - Uses Chrome's native tab groups API - ~2000 lines of code - All client-side, no backend
*Why vanilla JS?* Wanted to deeply understand browser APIs and state management before adding framework complexity. Learned a ton about event-driven architecture and DOM manipulation.
I'm a solo dev and this is my first Chrome extension. Feedback very welcome!