Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Also unlike Steam you might have to re-download the whole thing if your browser decides to clear the cache for whatever reason. Can't play underground, on a plane or while camping as well (not a typical scenario though - nitpicking a bit).


There's work going on for better app caching systems at the browser level. This is a UI and platform issue, but there's no tricky technical aspects. The user expresses the intent of wanting to cache a web app, and it is cached locally.


"The user expresses the intent of wanting to cache a web app, and it is cached locally."

So I will use [x] to find a game in [y] and then [z] it to play.

Where: x = {Chrome|Firefox|Steam}, y = {some-sort-of-web-app-store|Steam store}, z = {cache|install}.

I guess the success will depend on how easy and rich x-y-z experiences are, but you will still have to register, pay and download.


But crucially you will be able to buy on the app using x,y,z, and continue to play the app using a,b,c from different hardware/software vendors, unlike the situation today with say a game bought on a mac.

That's the advantage of the web over native APIs, and why I think its ethos will eventually win out - it is better for developers and users, but not for the corporations who would like to sit between the two as intermediaries.


Not when deployed with something like node-webkit which I would assume would be a common deployment strategy so you can guarantee Chrome and a certain version w/ certain features enabled/disabled.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: