Подготовка к публикации в магазине

Getting your browser extension ready for public release is exciting! But before you hit 'submit', there are crucial steps to ensure a smooth approval process and a great first impression.

This lesson guides you through packaging your extension, optimizing your manifest.json, and preparing all the necessary assets for a successful store listing.

Your manifest.json is the blueprint of your extension, and some fields are vital for store listings.

• name: The public name of your extension. Keep it clear and descriptive.
• description: A short, compelling summary for store listings.
• version: Ensure this reflects your current release.
• icons: Link to your extension's icon files.

Review these carefully to align with your public-facing information.

Icons are often the first thing users see. They need to be clear and recognizable at various sizes. You'll typically need icons in these dimensions:

• 16x16 pixels: For the favicon in tabs and extension menus.
• 32x32 pixels: For some OS contexts.
• 48x48 pixels: For the extension management page.
• 128x128 pixels: The main icon for the store listing and installation dialogs.

These are declared in your manifest.json under the "icons" key.

Your extension's description is your sales pitch! You'll typically provide two versions:

• Short Description: A concise, impactful sentence or two that grabs attention. Max 132 characters for Chrome Web Store.
• Full Description: A detailed explanation of features, benefits, and how to use your extension. Use clear language and bullet points.

Focus on what problem your extension solves and how it improves the user's browsing experience.

High-quality visuals significantly boost user engagement. Prepare:

• Screenshots: Show your extension in action! Highlight key features and user interfaces. Aim for 3-5 clear images.
• Promotional Tiles: (Primarily for Chrome Web Store) These are larger images used on the store's dashboard or category pages. They help your extension stand out.

Ensure all images are high resolution and accurately represent your extension.

Transparency about data handling is crucial. A privacy policy explains:

• What user data your extension accesses or collects.
• How that data is used.
• If and how it's shared with third parties.

You'll need a publicly accessible URL for your privacy policy, which you'll link in your store listing. This builds trust and is often a mandatory requirement.

Offering a way for users to get support or provide feedback is essential. You should prepare:

• A support URL (e.g., a help page, FAQ, or GitHub issues page).
• A contact email address.

This information is usually displayed on your extension's store listing, demonstrating your commitment to users.

To submit your extension, you'll need to package it into a single .zip file. This file should contain:

• Your manifest.json file.
• All your HTML, CSS, JavaScript files.
• Any image assets (icons, etc.).

Make sure to zip the contents of your extension's root directory, not the directory itself. The manifest.json should be at the root of the zip file.

Before packaging, perform a final, thorough check:

• All features work as expected.
• No console errors or warnings in development tools.
• Extension performs well and uses minimal resources.
• All required permissions are declared and justified.
• Content Security Policy (CSP) is correctly configured.
• All links (privacy policy, support) are valid.

Think like a user: does it install easily? Is it intuitive?

Congratulations! You've learned the vital steps to prepare your browser extension for submission. We covered:

• Reviewing your manifest.json.
• Preparing icons, descriptions, and screenshots.
• The importance of a privacy policy and support info.
• Correctly packaging your extension.
• A final testing checklist.

Next, we'll dive into the specific guidelines and processes for submitting to the Chrome Web Store!