Complex password generator – all you need to know26/02/2020
Password sharing at work – the right way15/04/2020
Our recent launch in the G Suite marketplace sparked interest in some of our users about the process of preparing and publishing Drive Password.
In this post we will guide you through our journey and hopefully will share some insights and prepare you what to expect.
It is important to keep in mind that Drive Password requires integration only with Google Drive and the guide will cover only this side of the process. Thus if your app uses other Google products (Docs, Sheets…) the application might differ a bit.
Before we start, it is generally good idea to go through the official documentation here - https://developers.google.com/gsuite/marketplace/listing-gsm. Most likely you already read it as it is the top result in the Google search (what a surprise).
In short, the process looks like doing some boring paperwork, but you have to complete it to see your app in the G Suite Marketplace.
Table of contents
- Step 1 – Enable G Suite Marketpalce SDK
- Step 2 – Configure the G Suite Marketplace SDK
- Step 4 – Select which Google Products your app works with
- Step 5 – Configure the selected product (Google Drive only in our case)
- Step 6 – Add your detailed description and app banner
- Step 7 – Screenshots (make them count) and additional information
- Step 8 – Select your category and reach
Step 1 – Enable G Suite Marketpalce SDK
Go to https://console.developers.google.com/apis/dashboard, make sure to search for the G Suite Marketplace SDK and enable it.
Once you enable it, you need to star configuring it.
Step 2 – Configure the G Suite Marketplace SDK
This is where the “paperwork” begins. You start with writing the name and description of your app.
Things to consider when naming your app:
- [Required] Add-on has a unique name (there are no other Add-on with the same name)
- [Required] Name does not contain “Google” or any Google trademarks (e.g., Hangouts)
- [Required] Name does not include version number
- [Recommended] Name uses title case
- [Recommended] Name has no punctuation, especially parentheses
- [Recommended] Name is 15 characters or less
We had some issues with our name Drive Password as it was initially rejected because it had the word “Drive” in it. After some discussion, we manage to get it accepted as this is the name of our software and it is by no means misleading the user.
- [Required] Description explains what the third-party service does, optionally links to the relevant website
- [Required] Description explains how Add-on interacts with the third-party service
- [Required] Short description does not exceed 90 characters (i.e., is displayed in full in the listing)
- [Recommended] Detailed description is provided (maximum 16,000 characters, to be displayed in the Overview section)
- [Recommended] The full set of attributes (name, short description, detailed description) is provided for each language the developer chooses to support
Step 4 – Select which Google Products your app works with
It can be more than just one. In our case, Drive Password is a Google Drive app. Keep in mind that you will need to configure each one separately.
Step 5 – Configure the selected product (Google Drive only in our case)
One more time – you need to add Name, Short and Long descriptions. Although they are marked as optional here – we strongly advise you to fill them. Besides the text, you have to upload your app icons in PNG, with transparent background in the following sizes:
- 256 x 256
- 128 x 128
- 64 x 64
- 32 x 32
- 16 x 16
Step 6 – Add your detailed description and app banner
The detailed description can be added in multiple languages if you prefer that. This is the description which will be visible to the people interested in installing your app. Take your time and prepare a decent copy with every detail that might be helpful to the person willing to install it. Make sure that you include any key points in order to prevent negative feedback and reviews.
Step 7 – Screenshots (make them count) and additional information
Most of us rarely read the whole description. First, we scan the screenshots trying to make sense of what the software might be doing. If it sparks an interest, only then we might consider reading the description and actually installing it. That said, don’t spare your creativity and efforts to prepare screenshots that communicate clear your apps’ strongest points and features.
If you are able to prepare an interesting video showcasing your product, that is even better than the screenshots. However, if you lack that skill and hiring a professional is not an option – don’t worry. Focus on the screenshots.
Developer name and website are required fields, but it is a good idea to fill developer email, FAQ, support page and tips for the user after the installation is complete. The more you can provide here, the better. If an users is unable to quickly solve a problem they encountered with your software and there is nowhere to look up for a solution – the uninstall button is highly likely destination.
Step 8 – Select your category and reach
Consider carefully in what category your potential users will be most likely looking for a solution like yours. It is a good idea to check your competitors. Do your research, don’t rely on your opinion only.
When you are done with this step, hit Publish and wait for the review.
Once you go through the steps, a Google Representative will be appointed to check your details. We waited approximately 48 hours for someone to contact us. The rep will share with you a Google Doc with things that you need to fix in order to have your app approved. They are polite and will help you out, so don’t worry if you are rejected for some reason. Follow their instructions, make the adjustments accordingly and within a week or so (depending on rejection reasons) your app will be visible on the G Suite Marketplace.
Need help? Let us know!
If you have questions or need an advice, we are happy to help you out. Just contact us via the chat widget on the website