(Sorry, I think this turned into a trolling ramble possibly...)<p>I cannot decide if this matters or not. Seriously, will this matter? I have web apps, I have web apps that would rock in a desktop environment where I didn't have to host the data, or could at least "sync" it with the desktop.<p>But does it matter? Will Chrome matter? Will telling people to install Chrome to install my app be worth it? Will other browsers follow suit?<p>Obviously this has so much going for it. First, it's being launched as a "store" and not just an "add-on" system. I haven't written my apps for Firefox because I need it to financially make sense. Creating something for another "store" does make sense.<p>I can now write apps for Android, iPhone, Palm, RIM, Windows, Mac, iPad, web-based, and other cell phones. Now add "browser-desktop" into the mix.<p>This means I have to write my app in Java with Android's SDK, Objective-C, (uhm?), Java, .Net Pascal C etc, more C, more C, PHP/Ruby/.Net/Python, more Java, HTML5? Uhgo.<p>Good Lord!!! Can I just write one app in Flash or Java and be able to distribute it everywhere PLEASE???
So it appears this is windows only for now according to this: <a href="http://code.google.com/chrome/apps/" rel="nofollow">http://code.google.com/chrome/apps/</a><p>Which seems so weird considering this is what will make chrome os, at least in terms of the web as a desktop sort of thing.<p>Though they probably did this for other reasons such as a larger userbase to test with or some reason unknown to me, hopefully I'll get to try it soon when it is ported to the other OS's.