How to deliver a chrome extension to a client.

You have taken on Chrome extension work for a client, you built it out locally and is ready to be handed over. How do you do it?

Let's explore all the ways in which you can deliver an extension to a client.

There are 3 ways

1. Transfer the code
2. Submit it in your developer account and transfer it after approval
3. Use the clients group publisher account

Transfer the code

You can transfer the extension code to the client and provide them steps on how they can generate the extension artifiact (zip file) to be submitted in the chrome store.

This is not friendly, as the client has to install and generate the artifact and they have to submit it to the web store.

If the client has never built and submitted a chrome extension before, it might be scary and time consuming to do the listing.

They have to generate web store assets (Extension description, Icons, screenshots), provide single purpose description of the extension, justify the requested permissions, filling in other privacy options etc..

There are nuances to be kept in mind while doing the submission.

For example: You have to provide a clear description or provide a valid justification for a permission that is requested in the extension. Failing to do so will lead to the submission being rejected.

Note that the extension review can take several days and any rejections can drag this process for days, before it is accepted.

Submit it in your developer account and transfer it after approval

This is the easiest and simplest way of transferring an extension to a client that I have found.

I do the submission and fill out the initial listing information in the chrome web store. Since I know the ins and outs of chrome submission guidelines, this is simple for me.

I have had 99% success rate and had only 1 rejection till now.

Typically the extension's initial submission is approved in 1-2 days (Can go longer for broader host permissions) and another 24 hours to transfer it to the client.

In this way, the client doesn't have to worry about the submission. I take care of creating the necessary assets and follow the submission guidelines & best practices.

Almost all of my clients have prefered this way of extension handover.

Here's how you can transfer the extension

1. Navigate to https://support.google.com/chrome_webstore/contact/one_stop_support
2. Choose My item (extensions, app, or theme)
3. Select I want to transfer my item
4. In the form, fill in the Item ID of the extension, Original author email (This is your email), Destination author email (The client's email)
5. Click submit

Once you submit, you will receive an email asking to confirm the transfer request. Reply to that email with a confirmation and the transfer process will be initiated.

Points to note

1. Ensure you provide the correct extension Item ID
2. Make sure the client's email ID is valid and is the same email they have used to create their developer account in the chrome store.
   • If they don't have an account, ask them to create an account and pay the initial one time 5$ registration fee

Use the clients group publisher account

Setting up a group publisher allows a user to share ownership of extensions in the Chrome web store with other developers. If a client already has a publisher account setup, this way is a better option.

Read more about it in the group publishers docs

Ask the client to add you to their group publisher account. Once they do that, you can select their publisher account from your chrome store.

Once you have selected the client's publisher account, you can go ahead and the submit the extension as usual.

Points to note

1. You can only create one group publisher account ever. This cannot be replenished, even if the group is deleted. This is relevant for the client. If you are planning to ask the client to create a publisher account, make sure you communicate this piece of information.
2. Another point you should communicate to the client is You cannot change which group is linked to the group publisher account. If they are creating publisher account just for you, make sure they understand this.

Conclusion

I prefer the 2nd option as it is the easiest and less hectic for the client. But you can choose any option according to your needs.

If a client already has a publisher account, then publishing from that account would be the best option for you.

The last option would be to just handover the code and let the client do the submission. This might need more handholding and lot of to and fro. But it might be the only option for you, if a client is not comfortable with the other 2 options.