Back to feed
Dev.to
Dev.to
7/25/2026
I built 3 Chrome extensions for my developer workflow - here's what I learned shipping on weekends

I built 3 Chrome extensions for my developer workflow - here's what I learned shipping on weekends

Short summary

A software engineer shares lessons from building three Chrome extensions on weekends: a JSON formatter with TypeScript generation, a JWT decoder with security analysis, and a character counter with platform-aware limits. Key takeaways include expecting first-submission rejection from Chrome Web Store, building small focused tools rather than one large one, and using local-only data handling as a genuine differentiator. The extensions were built with Claude Code as a pair programmer under the brand ShipNano.

  • •Three weekend Chrome extensions: JSON formatter, JWT decoder, character counter — all local-only
  • •MV3 permission strictness caused two rejections; expect first submission to fail
  • •Built with Claude Code; small focused tools ship faster than one large product

Generated with AI, which can make mistakes.

#ai-tools#open-source
Read full article at Dev.to

Is this a good recommendation for you?

Comments

Failed to load comments. Please try again.

Explore more

The original title is: "DevKits: 31 privacy-first browser-based developer tools built with Next.js 15"
Dev.to
The original headline is "5 Things I Learned Building a Chrome Extension That Watches ChatGPT, Claude & Gemini"
Dev.to
The original headline is: "How a Simple Word Counter Turned Into 50+ Browser-Based Tools in Just Three Weeks"
Dev.to
Building a Chrome extension for AI usage tracking: three Manifest V3 cookie pitfalls and fixes
Dev.to