TickYouOff
Sign in
Back
🧩

Chrome Extension Launch

Medium 19 items · 1 hour
testuser's avatar
testuser Published 1 month ago
Technical

A practical, step-by-step launch checklist for Chrome extensions, focused on Manifest V3 compliance, store listing readiness, and post-release workflow. Ideal for indie developers, small teams, or product owners preparing a first or updated Chrome extension release.

Progress
0 / 19
  1. Convert extension manifest to Manifest V3 — Update manifest_version to 3 and replace deprecated keys before publishing.
  2. Minimize declared permissions — Request only the least-privilege permissions and prefer optional/host permissions
  3. Audit and tighten Content Security Policy (CSP) — Disallow inline scripts and ensure external resource policies match your hosts.
  4. Move persistent background logic to a service worker — Refactor background pages to MV3 service workers and handle lifecycle events.
  5. Remove remote code execution and eval usage — Eliminate eval, new Function, or remotely injected scripts to meet store rules.
  6. Test extension locally and in Incognito mode — Load unpacked extension, test core flows, and enable Incognito if supported.
  7. Run linters and build a production bundle — Run static checks, remove dev-only code, and produce a minified production build.
  8. Prepare icons and graphical assets — Include required icon sizes (small to high-res) and ensure clear thumbnails.
  9. Prepare store listing screenshots and video — Showcase main workflows and permissions in clear images and a short demo video.
  10. Capture clear screenshots for main user flows — Include UI, settings, and any permission prompts; use clean backgrounds.
  11. Create a short demo video (30–60s) — Demonstrate value quickly; include captions and device framing.
  12. Write a clear privacy policy and data handling section — Document what data you collect, why, retention, and how users can contact you.
  13. Explain and justify permissions in your listing — Provide concise reasons for each permission in the store permissions section.
  14. Check Chrome Web Store policies and reviewer guidelines — Verify content, deceptive behavior, and data-use rules before submitting.
  15. Set up versioning, changelog, and release tags — Bump manifest version, tag releases, and record changes for users.
  16. Package extension ZIP and remove dev-only files — Create a clean ZIP of final files; exclude source maps and local test artifacts.
  17. Upload to Chrome Web Store and submit for review — Fill listing fields, attach privacy policy URL, and submit a precise changelog.
  18. Set up CI for automated builds and releases — Automate lint, build, and packaging; optionally sign or publish via API.
  19. Monitor reviews, respond to users, and maintain a changelog — Track reviewer feedback, fix issues quickly, and publish release notes.
Sign in to save
📝 My Notes