Back to all discussions

  •   7 months ago

Clarification on "Public Access" Requirement for Google Chrome Extension Submissions

Hello,

Could you please clarify what "public access" means in the case of a Chrome extension? I’m referring to this requirement:

"Access must be provided to an entrant’s working application for judging and testing by providing a link to a website, functioning demo, or a published application. If Entrant’s website is private, Entrant must include login credentials in its testing instructions. The application must be public."

Does the extension need to be published in the Chrome Web Store to qualify as "public" ? Or would it be acceptable to provide a public GitHub repository and clear build instructions (for example, judges can clone the repo, run npm install && npm run build, and load the unpacked dist/ directory in Chrome)?

Thank you for your clarification!

  • 4 comments

  • Manager   •   7 months ago

    Providing a public GitHub repository and clear build instructions is what is required in the context of a chrome extension. No need to publish it to the Chrome Web Store. Thank you!

  •   •   7 months ago

    Got it.
    Thank you for the clarification!

  •   •   7 months ago

    I'm using the Writer API in my extension, how would you recommend I host this on GitHub without the trial token?

  • Manager   •   7 months ago

    Judges will have all flags enabled to try out your extension locally, don't worry ;)

Comments are closed.