We don’t let drug companies sell their products to everyone the second it’s produced. First you test in mice, then 10 people, then 100, then 1000, then, and only then, can you release it to an entire population (roughly speaking).
If I update the text or change a typo they take a week to release the update. During this time I can't release another version of my app.
Note that they aren't actually DOING anything in this week.
The Polar extension is literally just sitting waiting for someone to approve it because I updated the images.
Don't get me wrong. I, too, wish that other developers would drop whatever they're doing on demand to prioritize my immediate needs. I would also prefer that they waive their normal security concerns because, after all, I already know that I am trustworthy. I've got enough self awareness not to publish a blog post about it, though.
Why don't you suggest your users to switch to a browser that does not force them to use a central repository that's too slow to get your updates? You need to convince them at the same time that there are no benefits lost to the way Chrome Web Store operates.
Anyways, I get that the turnaround time stinks.
Because they have to check hundreds of thousands of applications a day, most of which improve stupid things like typos. Having the biggest part of the cake doesn't help either.
"permissions": [
"activeTab",
"fileBrowserHandler",
"webRequest",
"webRequestBlocking",
"webNavigation",
"<all_urls>",
"storage",
"tabs",
"tabCapture",
"cookies",
"http://localhost:8500/rest/v1/capture/trigger",
"contextMenus",
"unlimitedStorage",
"declarativeContent",
"idle",
"storage"
],
First up: improve the QA process on your extension to avoid having to do 5-line diffs every few days.
In the meantime, you can offer your users to switch to "developer mode" and install the extension manually.
I personally would be against the centralized nature of Chrome extensions world anyway (which, by definition, leads to bottlenecks, for dubious benefits), but at one point Google claimed there were 180,000+ extensions in the web store, and if only 0,1% of those get updated every week, that's 180 extensions to be reviewed every week.
Are you a developer? This is literally the definition of continuous delivery.
Btw, instead of attempting ad-hominem attacks, perhaps you should stop for a bit and reconsider why you are getting so many down-votes around here.
But even if it were, why do you think continuous delivery is the appropriate choice of workflow when you don't actually control the "delivery" part?
This way, you only need to push a new extension update whenever you need new api-level functionality, and you have total control over the rest of the user experience (regular HTML/CSS/javascript).
Or would this cause the extension to be rejected by Google, on the grounds that the "api" that it adds would be too open to abuse?
Perhaps someone else could make this point in a way that would be better-received.
When I say typo or image I'm talking about the appstore assets... not the binary.
There's the actual binary you push out to you chrome uses.
Then there is the text and images in the app store. This is NOT part of the app.
IF you fix a typo in the app store description, it causes a one week review.
Even when you didn't actually update the app AT ALL.
The exact same binary - bit for bit.
That's part of the the issue.
The other is that changing a small amount of code shouldn't require a full week to re-audit.
I'm looking to switch away from Calibre (which has a cluttered user interface) and if Polar supports common ebook formats it might be worth trying.