Chrome Extension Launch

19 items · Technical · Medium difficulty · 1 hour

Essential checklist to launch a Chrome extension with Manifest V3 and store-ready assets.

• Convert extension manifest to Manifest V3

  Update manifest_version to 3 and replace deprecated keys before publishing.

• Minimize declared permissions

  Request only the least-privilege permissions and prefer optional/host permissions

• Audit and tighten Content Security Policy (CSP)

  Disallow inline scripts and ensure external resource policies match your hosts.

• Move persistent background logic to a service worker

  Refactor background pages to MV3 service workers and handle lifecycle events.

• Remove remote code execution and eval usage

  Eliminate eval, new Function, or remotely injected scripts to meet store rules.

• Test extension locally and in Incognito mode

  Load unpacked extension, test core flows, and enable Incognito if supported.

• Run linters and build a production bundle

  Run static checks, remove dev-only code, and produce a minified production build.

• Prepare icons and graphical assets

  Include required icon sizes (small to high-res) and ensure clear thumbnails.

• Prepare store listing screenshots and video

  Showcase main workflows and permissions in clear images and a short demo video.

• Capture clear screenshots for main user flows

  Include UI, settings, and any permission prompts; use clean backgrounds.

• Create a short demo video (30–60s)

  Demonstrate value quickly; include captions and device framing.

• Write a clear privacy policy and data handling section

  Document what data you collect, why, retention, and how users can contact you.

• Explain and justify permissions in your listing

  Provide concise reasons for each permission in the store permissions section.

• Check Chrome Web Store policies and reviewer guidelines

  Verify content, deceptive behavior, and data-use rules before submitting.

• Set up versioning, changelog, and release tags

  Bump manifest version, tag releases, and record changes for users.

• Package extension ZIP and remove dev-only files

  Create a clean ZIP of final files; exclude source maps and local test artifacts.

• Upload to Chrome Web Store and submit for review

  Fill listing fields, attach privacy policy URL, and submit a precise changelog.

• Set up CI for automated builds and releases

  Automate lint, build, and packaging; optionally sign or publish via API.

• Monitor reviews, respond to users, and maintain a changelog

  Track reviewer feedback, fix issues quickly, and publish release notes.

Printed from TickYouOff — the interactive version tracks your progress and can be shared with others.