Chrome Extension Development — Manifest V3 Guide

Chrome extensions for Amazon sellers are a competitive market. We've built extensions with 2,000+ paying subscribers. Here's our technical playbook.

Manifest V3 - The New Reality

Google deprecated Manifest V2 in 2024. Manifest V3 brings significant changes:

• Service workers replace background pages (no persistent background scripts)
• DeclarativeNetRequest replaces webRequest for network interception
• Content Security Policy is more restrictive
• Remote code execution is banned (no eval, no remote scripts)

Architecture

Our extensions follow this pattern:

1. Content Script - injected into Amazon pages, reads DOM, renders overlay UI
2. Service Worker - handles API calls, token management, alarm-based scheduling
3. Side Panel - detailed analytics views (replaces popups for complex UIs)
4. Options Page - user settings, subscription management

Content Script Performance

The #1 rule: your extension must not slow down Amazon pages. Our target is <50ms of added page load time.

How We Achieve This

• Lazy rendering - only inject UI when the user scrolls to relevant sections
• Web Workers - offload data processing to background threads
• Virtual DOM - React with minimal re-renders for injected components
• Debounced observers - MutationObserver with 100ms debounce for DOM changes
• Skeleton loaders - show placeholders while data loads from API

Lessons Learned

1. Amazon changes their DOM frequently - use resilient selectors, not exact class names
2. Test on all Amazon marketplaces - .com, .co.uk, .de, .co.jp have different page structures
3. Handle logged-out users gracefully - not everyone is signed into Amazon
4. Memory management matters - extensions that leak memory get terrible reviews

Want to build an Amazon extension? Our team has done it before.

Frequently Asked Questions

Manifest V3 vs V2 for Amazon extensions?

V3 is required for Chrome Web Store.new submissions. Service workers replace background pages; plan for ephemeral worker lifecycle.