Threes: The Rip-offs and Making Our Original Game
> We know Threes is a better game, we spent over a year on it.I played Threes, and I liked it. And I feel for these guys having to watch everybody and his brother pile on to the idea they had to work so hard to tease out into reality.But here is some hard truth: none of that matters.Nobody cares how hard you had to work to get from idea to product. All they care about is what you have produced at the end of all that work. What makes it better or worse is how it stacks up relative to the competition -- even the competition that is shamelessly riffing off your core ideas -- not how much sweat you put into it.And I gotta say, having played 2048, 1024 and Threes (the Android versions, at least), I think of the three of them 1024 stands up the best. It takes the core ideas in Threes and sands them down into a game that is easier to grasp and plays faster, without becoming so simple (a la 2048) that it becomes a game a script can beat. Threes makes you swipe-swipe-swipe after every game to get your score and "sign" it (why do I care about signing it?) before you can play again; 1024 just moves you straight on to the next game. Mobile games need to be simple and streamlined, and 1024 understands that imperative better than Threes does.I say all this to help others understand why I would point to this essay as an example of how not to respond to a problem like a barrage of cloners. It's because this essay sees the world entirely from the developers' perspective -- look how hard we worked! Look how long we labored! Look how subtle our decisions were! -- which is exactly the wrong angle.You want your communications to speak from the customer's perspective, not from your own. Customers don't give you brownie points for how hard you worked on something. All they care about is how to get the best product for the best price. So if you put your heart and soul into something, and then someone comes along, tweaks your thing and makes it better, the way to respond isn't to ask people to respect how hard you worked; it's to look closely at the new thing, understand why people like it better, and then bring that understanding to your next iteration or your next product.