I developed a Chrome extension called TabCarousel to help monitor information like our NewRelic graphs. After realizing other people might find it useful, I decided to open source it and then release it on the Chrome Web Store.
I'm really impressed with how easy it is to release code on the Web Store, but... even a couple days after the extension has been released, I still show " users" and " weekly installs" rather than something like "7 users" and "10 weekly installs". I know I've set my extension up on a few computers, and I've helped others set it up as well. A few friends have installed it too.
Why doesn't the Chrome Web Store show any users or installations? It's not showing any data at all -- that is, " users" instead of "0 users".
Am I just missing something? I've read through the FAQ, some blog posts, and even set up a Google Analytics account and entered it in the Developer Dashboard entry for my extension. I just want to get an idea of how many downloads I'm getting so I can gauge interest like I can on other projects.
This is actually a bug, and the team are in the process of preparing a fix and getting it pushed live. I don't have an exact ETA, but it should be pretty soon.
On another note, you can still use your Google Analytics accounts to detect traffic to your landing page and in your app. And if you look for the referrer chrome://newtab you will get a very good indication of all the users who are launching your app.
Just give it few days, they don't update counters in WebStore too often. Currently it doesn't show users for any extension submitted after June 15, and yours was submitted on June 19.
Related
I have a chrome extension, and I am creating a website for it, that has info, and a way to test it. I would like to show the number of users currently, but have found no way to do this. It doesn't have to update every day, but if it updated weekly that would be great!
Also- I don't care if it is by a outside company rather than chrome itself. all that matters is that it works.
I am planning to show something similar on my extension's site so I have googled around a bit recently. I found a repo (https://github.com/petasittek/chrome-web-store-stats) that parses information about extensions in the Chrome Web Store. It could be useful for you. I think I will end up just parsing the Webstore page for the user numbers everyday in save it to a database. My extension is also available for Firefox and I will do the same there then aggregate the results.
We're trying to work out how to resolve this issue, the current issue we have is our extension works on a unlimited amount of websites 1 of the features is a time & screenshot monitor so employer can track freelancers work other feature is ability to highlight text on any site and run a amazon search for the highlighted text for example.
We are always updating and any issues got fixed within 24-48 hours now with this happening every time we have to wait 1-3 weeks for a review according to google devs.
If we change the manifest to specific websites only then 99% of the time our extensions not going to work on all the other sites not listed. Can we do something else?
IF ANYONE HAS A SOLUTION OF WHAT WE CAN CHANGE TO MAKE THIS WORK I'M ALL EARS!
I have a chrome extension that im looking to monetize with subscription and free trial.
I have followed all the guide detailed here: https://developer.chrome.com/webstore/one_time_payments
Everything works, its all good, just now I need to know how to actually trigger the payment flow when a user decides they want to pay for my extension.
I can see that there is a "buy.js" for in-app purchases but im not sure how you are supposed to do it for one-time payments.
The only way I can see of doing it is by opening a new tab to my chrome store page and then somehow educating the user that they need to press the orange button...
Theres got to be a better way of doing it than that tho, surely??
If you want your extension to be paid using Chrome Web Store Payments, you have to follow Chrome Web Store Payments rules, which include fixed price tiers and the fact that payment must be initiated by Chrome Web Store. The in-app purchases work differently.
So yes, your users will have to subscribe using the orange button in your extension's Chrome Web Store entry. Usually they need not to be "educated" to do that: after all, that is the page they installed your extension from, and the orange button was already there.
Depending on which kind of free trial experience you offer, you can display relevant reminders to your users.
For example, if your free trial limits some functionality of the extension, you can prompt the users to subscribe when they try to use one of the premium functions, and/or display a Subscribe button in a visible part of your extension that links to your Chrome Web Store entry.
If your free trial is time-limited, you can display a counter of how many free-trial days your users have remaining, and the Subscribe button mentioned above. When the trial period is over you can automatically alert the users and open the Chrome Web Store entry of your extension. This latter approach (time limited free trial period) is the one I am currently using in my extensions and so far I've had no problems with the users or confusion on their part.
I have no previous experience with programming Google Chrome plugins which is why I am starting here to see if what I want to accomplish is possible/reasonable. I do however have a pretty broad experience in programming in general.
What I want:
I want some kind of "trigger" to go off when a new Chrome Notification (you know these little pop ups above the system tray) is popping up. I want to execute some script/code depending on what information the notification contains so that I for example could have an alarm go off if I receive an email from a certain user with a certain key word in the subject and get a pop up from my Gmail Notifier extension.
This is however just an example and I have a bunch of ideas for different notifications from different extensions and websites so don't get caught up on that particular example.
When I look at the Chrome Notification API I see that there is a getAll method that supposedly is getting all the "notifications in the system" but I do not find any Event for new notifications.
I suppose a possibility would be to poll with getAll a couple of times per second (it needs to be really fast for some implementations I have in mind) but it feels very tacky.
Is there any way to easily access new Notifications programmatically in Chrome?
(I'm open to all solutions, programming languages and such...)
Well, I searched long and hard and got involved with the Chromium dev group and asked around there. As far as I could figure out there was no reasonable way of accessing all Notifications programatically.
So what I ended up doing was just download the source-code of Chromium and build my own custom version of chromium adding a very crude API. Worked like a charm and not as complicated as one might think.
Cheers!
Suppose I'm the developer of a chrome extension (which indeed I am) that is up on the web store and that I want to answer the review of one the users.
Now, if I add/edit my review my previous post gets overridden (even if I AM the developer), making my efforts in helping users useless.
Is there something I'm missing, or is it how it currently works without any way to prevent this from happening?
All reviews on the Chrome Web Store are from Google+ users now. Your best option is to click through to their profile and either send them an email, send them a message, or share a post with them. The first two are more direct and likely to get noticed but there isn't much else you can do.