Missed this last week, but wanted to highlight it & #39;cause it& #39;s a reasonable (if unflattering) look at the challenges extensions devs face

The article calls out docs: I& #39;m currently planning to spend the rest of the year focusing on docs & resources for devs https://www.digitaltrends.com/computing/google-chrome-web-store-developers-struggle-issues/">https://www.digitaltrends.com/computing...

A few quick thoughts on the dev experience. Please note that I& #39;m not speaking for Google, but I am speaking as someone with personal experience in this space and an interest in making this better.

1. CWS rejections are obtuse, but we& #39;re actively working on this. We& #39;ve updated…

…our email format to be a bit easier to read & understand. We& #39;ve also added IDs to the emails to make it easier to find docs (both ours and others) related to a specific reason for rejection

2. Support is hard to get, but we& #39;re working on that too. We& #39;ve consolidated our…

…contact methods into a single form so devs don& #39;t have to hunt for "the right way" to contact us. If you want to reach out, use this form: https://support.google.com/chrome_webstore/contact/one_stop_support

We& #39;re">https://support.google.com/chrome_we... also working on improving how we respond to requests for clarification. Hopefully I can share more soon.

3. As we& #39;ve made progress on 1 & 2, I& #39;m focusing more on the docs & broad developer communications. My main focus will be preparing for MV3. This is also early, but if y& #39;all have thoughts on format or medium I& #39;m all ears