Chrome Web Store
chrome.google.com
chrome.google.com
Apple store, Chrome web store, Android market, etc. are all solving the marketing and distribution problem for developers all over the world. Furthermore with rankings and reviews the good apps will rise to the top while the bad ones will be lost in obscurity. It's increasingly a game of creating compelling products and not compelling marketing to win.
We're not quite there yet, there's still lots of work to be done with rankings, etc. but the trend is quite clear. I wonder when Mozilla will announce their app store.
In some countries Chrome now has more than 25% market share.
That audience could make the Chrome Web Store the biggest app store on the planet.
All the apps are built using web technologies like Javascript, HTML5 and Flash.
Mobile appstore made sense since there wasn't an existing distribution or discovery infrastructure. For web apps the Internet has already solved distribution and discovery..
I see appstores as a plague and counter to the open and free Internet. A few companies are getting (for practical purposes) "monopolies". Altering the level playing field into one in which developers are beholden to appstores.
Until then marketing is a huge part of success in these stores. Be it working with the press (blogs, traditional press, and everything in between) to good old fashioned advertising. Very few app-store developers have had sustained success without the normal marketing and sales efforts that you need with any other product (at least the ones I have insight into).
There's already a user backlash visible in reviews. A lot of people are disappointed that a Gmail app is just a link to the Gmail website, for example.
Here's a quick vocabulary of Google's terms and what they actually mean:
app – website
store – directory
install an app – add a bookmark
paid app – paywall managed by Google
in-app purchase – paywall managed by third party
If nothing else, for a developer it must be hugely beneficial to get your website link to the new tab page.
How viable is that? Wouldn't it be trivial to "steal" since you can just view the source code? Would obfuscation help at all?
I'd love to be able to sell HTML5 games, but it doesn't strike me as a realistic option.
However, this isn't necessarily any different than binary executables, which we know experience a fair amount of pirating.
Also from that FAQ:
"Update your app frequently, so that only authorized users will always have the latest, greatest version of the app. Distributing updates is easy, thanks to Chrome's support for autoupdate. You just increment the version number in the manifest, update the ZIP file, and then use the Chrome Developer Dashboard to upload and publish the updated ZIP file. Over the next few hours, the new version of the app starts going out to its existing users."
"Don't put any roadblocks in front of users. Your app should be easy to buy, and it should work everywhere users want it to work."
That is: "Don't rely on DRM to protect you. It won't work, and you'll piss your users off."
Has anyone used Bespin and/or any existing web-based IDEs? Googling didn't return anything compelling.
(Similarly I'd feel a lot more comfortable with Google Applications if I could tell it to store my documents on my storage, or at least seamlessly mirror to my storage)
Also, it appears that only US and UK developers can be a Google Checkout merchant, except for the Android Market where anyone from one of a bazillion different countries can sell.
However, the Chrome Web Store developer ToS seems to imply that other payment processors can be used, provided they are approved by Google. It doesn't say who those payment processors are or how they integrate with the store.
So yeah, anybody figured out how it all works?
https://chrome.google.com/webstore/detail/hbadbkkklnhamjjeag...
(Mibbit Chrome app, free version, ad supported)
They previewed it at Google IO and it still hasn't surfaced :-(.
But to be unfairly brief, anything that requires a download to run offline, or requires publishers to "upload" their apps is a step backwards. Since all that entails is literally running a desktop app. There's nothing there that couldn't be done 10 years ago, the only difference is that the apps have to be written in web technologies or not, using NativeClient. In my mind this is a step backwards, and essentially an unnecessary end run around the web solely for the purposes of monetization. I'll fully elaborate in an upcoming blog post tentatively titled "1 step forward, 2 steps back".
"Many installable web apps are hosted apps—normal websites with a bit of extra metadata. You can build and deploy hosted apps exactly as you would build and deploy any web app, using any server-side or client-side technologies you like. The only difference is that you must provide a small manifest file that describes the app.
If you want your app to work especially well offline or to be tightly integrated with the Google Chrome browser, you can create a packaged app. A packaged app is just a web app that the user downloads. Packaged apps have the option of using the Google Chrome Extension APIs, allowing packaged apps to change the way Chrome behaves or looks."
Standard web development has it's own support problem (browser discrepancies). But that pales in comparison to what supporting all of these store platforms would be like.
I want Firebug installed locally in Firefox (or better yet integrated directly into the browser like Chrome does). I don't want to download a bunch of Javascript every time.
Here's the developer guide for more on how it works under the covers: http://code.google.com/chrome/apps/docs/index.html
Quick Note: https://chrome.google.com/webstore/detail/mijlebbfndhelmdpml...
Am I missing something?