Telling people about your web app in the Chrome Web Store is just as important as making your landing page rock. The more people that you can drive to your detail page the better your application will do, but you want to do it in a targeted way.
For this reason I created Badgemator – an app that creates badges for you to put on your website. It is about a month old, so why am I telling you now? Well the answer is simple, I posted it on twitter, and then forgot to post this blog – DOH!
It is an interesting project because it does a couple of cool things that make it super easy for you to use.
- All you need is your Web Store URL – for example see http://badgemator.appspot.com/#https://chrome.google.com/webstore/detail/dhbgookgdfbbinnmmkbmjgolhikbbhpj to get started.
- It is self contained – it base64 encodes your initial logo and css so that all you need to do is drop a single script tag into your HTML and BOOM, you have a great looking badge with no extra HTTP requests. Check out the source of Appmator and you will see there is a simple html tag that points to an embedded script.
- It will only appear for Chrome users.
- If installed on your app, it will detect if your app is installed using the window.chrome.app.isInstalled variable and not show it to users who already have your app running.
- It will scan your listing page and pluck out all the important information including your Logo
- The default style is 'basic' to say the least, but you can style this up to look however ever you want, it could look like the Butter bar, or it could be some crazy 3d transform.
My good friend Mike Mahemoff suggested a neat use of URL fragments a while ago to enable quick sharing of links, hence you will see all my services support #URL at the end, so that if you wanted you could share it on Twitter and any reader would see the completed action – most of my service logic is on the client side.
I really need some more designs for default badges, so feel free to fork this project and make some changes to the CSS and I will incorporate it into the project and give you credit and links from the app.
I lead the Chrome Developer Relations team at Google.
We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.
Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on web.dev, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.