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

I loved threes, Played it for close to 20-30 hours during winter break. As soon as 2048 came out, I managed to get to 2048 on my second try based on my experience with threes. I play 2048 in my browser whenever I have a spare 5 minutes, and when I'm on the Bus, I still frequently hop into a quick game of Threes.

The mechanics of the two games are very similar, and obviously 2048 is a direct descendent of threes - but I wouldn't go so far to say that one is better than the other.

Threes has claim to originality, and first publication, so significant credit does need to go to Asher Vollmer, Greg Wohlwend and composer Jimmy Hinson of Sirvo for their original invention.

But, Threes does have some "issue" - one is really poor startup times. It's slow enough that I am more likely to play 2048 in my browser, than bother firing up Threes on my iPhone. The piece assignment in threes, is also somewhat less pleasing to my experience than in 2048, for whatever reason.

Also - sometimes you are looking for nice quick fun - I get a nice rush of (finger mashing) 2048 to the 512 stage, and then very, very quickly racing to 2048 instinctively (plus the crush of defeat if I make a flickering mistake and get my pieces out of place).

Threes requires a lot more attention - I can't really play it at full-key-flick-speed - Not every game has to be chess.

If you read through the emails, and design history on the "making of" - it really, really emphasizes how damn hard it is to build that original kernel of genius. And then the piling on of all the clones/knockoffs/descendants shows how trivial it is for others to stand on the shoulders of genius.

One challenge of the AppStore (and obviously the Android stores, and simply by definition the Web) - is that there is no real way to "reward" the original developers for their many months of hard work, when others can simply clone, tweak the artwork and mechanics (or in the case of Zynga, just the artwork) - and release and market their own duplicate of a game after someone else has done all the hard work.

But, sometimes this opportunity to reinvent is good - I've tried a lot of podcast apps - because I listen to podcasts for about 4-6 hours/day, and, while "Cast" is my current preferred App, I'm looking forward to what Marco does with Overcast. I would have hated it if we couldn't have lots of diversity in that marketplace. (And I would have shot myself if I had to use Apple's (original, horrible) "reel-reel" podcast player).

Another approach though are apps like Vesper - It's "another" notepad app - but the developers (Q Branch's John Gruber, Brent Simmons, and Dave Wiskus), took months and months to polish and refine till it creates a totally different notepad experience (and, in my opinion, the best one on the iPhone) - isn't it good that they had the opportunity to build something in the notepad category, in a different way?

All in all though, I hope that Sirvo's Asher Vollmer, Greg Wohlwend and Jimmy Hinson get the credit they deserve for building the "first of".



> But, Threes does have some "issue" - one is really poor startup times. It's slow enough that I am more likely to play 2048 in my browser, than bother firing up Threes on my iPhone. The piece assignment in threes, is also somewhat less pleasing to my experience than in 2048, for whatever reason.

I'll admit that still puzzles me. I'm not sure what Threes is doing but it does seem to take an inordinately long amount of time.

Adding a 'loading' spinner just emphasized that I was being forced to wait.

It's actually effected my playing. If I go to open Threes and it pops straight up (it was still in memory) I'll play a quick game. But often if I get that 'startup screen' I'll immediately exit the app and do something else like check Twitter or Safari.


From the post, it looks like they used Unity to build the game, which as an engine is rather overkill for a 2d puzzler. The loading times are probably tied to this.


Very good point. It had one of the slowest app startup times on my iPhone 4 which for a conceptually simple tile puzzler that you play on the train is pretty bad.


I think part of the issue is that they let it try and run on hardware where it really shouldn't, given the performance issues it seems to have on older iOS releases. (I don't know about current iOS releases, since I haven't tried Threes on them yet.)


> I'm not sure what Threes is doing but it does seem to take an inordinately long amount of time.

They've blamed it on Game Center in the past.


> One challenge of the AppStore (and obviously the Android stores, and simply by definition the Web) - is that there is no real way to "reward" the original developers for their many months of hard work, when others can simply clone, tweak the artwork and mechanics (or in the case of Zynga, just the artwork) - and release and market their own duplicate of a game after someone else has done all the hard work.

There certainly are ways. But it involves building involved games that are more than the distillation of one trick. I'm confident that we'll do well with our RPG on mobile in part because Zynga will literally never copy the game I'm working on and Kemco--the biggest purveyor of RPGs on handhelds--just plain makes worse games than what we'd actually allow out the door (that whole "professional pride" thing, I'd rather release nothing than release a bad game).

I like Threes. It has a really neat core conceit and I enjoy playing it. But another word for "core conceit" is "gimmick", and most gimmicks are hard to make exclusive.


I probably should have differentiated between "Simple Games around a particular mechanic" and "Rich Environments or Game Engines."

The Simple Games around a particular mechanic can, as I've now learned, take many months to develop, and polish until they get to that nugget of experience. But, once that nugget has been published - it's tempting for others to rip off the mechanic. Tetris, Farmville, Candy Crush, PacMan, etc.. all fall into this field with threes.




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

Search: