Ever wondered what happens when you submit your extension to the Chrome Web Store? We sat down with the Trust & Safety team that leads review in the Chrome Web Store to ask your questions.
Chapters:
00:00 – Introductions
01:38 – What is your team responsible for?
04:00 – Why is review important?
05:57 – Abuse on the Chrome Web Store
07:15 – What does the review process look like?
08:04 – Questions from developers
08:55 – Can review handle large numbers of submissions?
10:11 – Why does review time vary? What can developers do?
14:32 – When should developers reach out to us?
15:18 – Is minification of code allowed?
16:50 – Do we see lots of excess permission usage? What other mistakes do developers make?
17:39 – What is the Remote Hosted Code policy?
18:52 – What happens if your extension fails review?
22:08 – How can developers handle unpredictable review times?
24:40 – How does the featured badge work?
28:12 -Why do codes like “blue argon” exist?
31:16 – How do we apply broad / vague policies?
36:10 – Do you see developers selling extensions?
37:53 – What issues do we want to solve going forward?
39:37 – Common mistakes for beginners / new AI developers
41:40 – What influences rankings in search?
42:43 – How should developers handle bad faith reviews?
44:57 – Are there interesting examples of abuse we’ve stopped?
48:58 – Wrap up
Resources:
Chromium Extensions Mailing List → https://goo.gle/4dQINmT
One Stop Support form → https://goo.gle/44XmnMt
Watch more Chrome Extensions → LINK
Subscribe to Chrome for Developers → https://goo.gle/ChromeDevs
#ChromeForDevelopers #Chrome