Service · Browser Extensions & Plugin Platforms
Extensions are product engineering under someone else’s rules: Manifest V3 kills your background process whenever it likes, storage and auth run inside a sandbox, and every release ships through a review queue you don’t control. I build extensions daily at Writer, shipped the LottieFiles plugin portfolio across eight-plus host surfaces, and built two wallet extensions where the sandbox was also a security boundary.
Sound familiar?
Scope
Outcomes
Engagement formats
60–90 minutes
A paid working session on one defined problem: an architecture choice, an AI feature plan, a performance question, a build-vs-buy call. You bring the context; I bring pattern recognition from 13+ years of shipping in situations like yours.
Start here →3–5 days
A focused investigation of one high-impact problem. I read the code, profile the system, interview the people closest to the pain, and separate symptoms from causes.
Start here →2–4 weeks, fixed scope
I take hands-on ownership of the most critical part of the work — writing production code, making the blocking decisions, and coordinating with your product, design, and backend people until it ships.
Start here →Evidence
LottieFiles
Every plugin host has its own sandbox, auth constraints, and review process. I helped LottieFiles ship one coherent toolchain across Figma, Adobe, Canva, VS Code, WordPress, and more.
Web3 contracts
Wallets, swaps, and NFT flows are frontend engineering with money on the line. Across four Web3 products I built the extension surfaces and transaction UX that had to get it right.
I will tell you whether I can help — and what the smallest useful next step would be. If I’m not the right person, I’ll say so.