✅ What got done
- Reached out to Simeone from Chrome's Developer Experience team about a bug I'm experiencing on Chrome for my extension. The bug got escalated to the right team! More details in this IH post
- Actually still blocked by the above issue, but I hope reaching out will eventually get the attention the bug needs. In the meantime, I successfully worked on a workaround. I downgraded from Manifest V3 to Manifest V2. This means not using the new fancy APIs and removed tabGroup API 😢.
- Added analytics to my extension to know how users start interacting with it. Specifically, number of times extension is activated, number of times tabs are closed with extension, number of scheduled tabs created 📈
- Testing TurboNav extension using Manifest V2 on Mac and Windows.
- Friday, Sept 03 released my extension to Chrome Web Store. Patiently waiting on results 🙏
🎯 What's the next steps:
- Start formulating some sort of marketing plan. Mainly two goals
- Getting attention and understanding of the product by creating a walkthrough video
- Work on the landing page to get alpha sign-ups
- Work on the blog for the headline: "The vision for TurboNav". I want to talk about my plans for TurboNav so people understand what my roadmap will look like
- Thinking about starting a small community around tab management. Super niche but will start the first steps into that this week
- Work on architecture for TurboNav's next feature "Save Links using Tag Organization"
- Mainly around finding a good schedule (marketing vs development). I enjoy development, but marketing is a must. Gotta figure out the right balance.
Trending on Indie Hackers