Live data from Hacker News

Game about squares

gameaboutsquares.com

181–190 of 208 posts

Re: Game about squares

#181
post #74

Earlier quoted context omitted.

I'm hoping the author is way ahead of us. If he were smart, the game should be approved in iTunes and uploaded to Google Play, just ready for him to click "Publish" the moment this web version picks up some traffic. Otherwise, Google Play will have a clone by the weekend if not sooner, and iTunes, maybe a week or two.

I'm the author. I'm not very smart...

You probably should at least phonegap it asap, someone is bound to copy this, its a good game! well done

Re: Game about squares

#182

Earlier quoted context omitted.

I'm curious what would stop someone from directly copying his code and sticking it in an webview of an android app.?

Somebody will definitely do it, on a throwaway dev account, but the original developer will only need to file a complaint and that account will almost certainly get banned for such blatant copyright infringement.

what about all the 2048 clones?

Re: Game about squares

#187
post #83
post #63

The author is intentionally limiting this app to touch-only for touch-capable users. This breaks the game for anyone wanting to use a touchpad or mouse on their touchscreen laptop. The offending code (from http://gameaboutsquares.com/game.c.js , beautified): (function($) { try { document.createEvent("TouchEvent"); return; } catch (f) {} var eventMap = { mousedown : "touchstart", mouseup : "touchend", mousemove : "tou…

I use a touch-enabled laptop and come across this far too often. Even nytimes.com is guilty of this, as is Stripe Checkout.

We actually changed this recently in Stripe Checkout. Touch detection worked great for 99% of cases, but serving a touch-only experience to devices like yours was pretty clearly unacceptable.

We're now treating the touch-only versions as optimized for specific platforms. For example, we have a mobile version that is optimized for, and only displays on, Android and iOS. Going forward, we may explore a pointer event polyfill to improve support for less common touch devices.

Re: Game about squares

#188
post #83

Earlier quoted context omitted.

I use a touch-enabled laptop and come across this far too often. Even nytimes.com is guilty of this, as is Stripe Checkout.

We actually changed this recently in Stripe Checkout. Touch detection worked great for 99% of cases, but serving a touch-only experience to devices like yours was pretty clearly unacceptable. We're now treating the touch-only versions as optimized for specific platforms. For example, we have a mobile version that is optimized for, and only displays on, Android and iOS. Going forward, we may explore a pointer event po…

I stand corrected. Thank you for finally making this change... It's been driving me mad.

Re: Game about squares

#189
post #74

Advice to author. Create iOS and Android versions of games ASAP. You are just hours away from getting cloned on app stores.

I'm hoping the author is way ahead of us. If he were smart, the game should be approved in iTunes and uploaded to Google Play, just ready for him to click "Publish" the moment this web version picks up some traffic. Otherwise, Google Play will have a clone by the weekend if not sooner, and iTunes, maybe a week or two.

It's already on Play Store. It's called push the squares (I did not download).

Re: Game about squares

#190
post #152

Earlier quoted context omitted.

http://stackoverflow.com/questions/12566306/how-to-test-for-...

It doesn't answer why they want to do this in the first place.

Touch and mouse are separate input devices and have separate set of expectations associated with them.
Post reply on HN