Spymaster took off like a rocket over this past weekend. A little bit of hype, plus the desire to be playing with the cool new thing, and boom… you’ve got an instant hit. There was a dark side, however, in the way that it used Twitter to communicate with users and recruit others to the game. The Twitter audience is not the Facebook audience, and many Twitter users reacted negatively. Even those who tried it, rapidly abandoned the game.
Yesterday I started seeing the first signs that the Spymaster phenomenon might have peaked. I had a busy day at work. In the morning my circle of Spymasters was 78. By the time I checked it last night, it had shrunk to 62. This morning, bit.ly showed that users clicking on the Spymaster links had flat-lined from Sunday to Monday also.
What can you learn from Spymaster’s experience?
- Pick the audience that you’re targeting your viral experience at carefully. Spymaster chose the Twitter audience, but they might have been better off chasing Facebook users.
- Make sure there’s enough product to engage the customer without turning on the viral engine first. A lot of folks, myself included, concluded that Spymaster was dull. While beautiful to look at, the gameplay wasn’t engaging enough. Virality alone can’t drive an application to success. Success requires that all of the elements that make for an engaging game, or useful application, be there already. Virality is simply a way to drive down marketing costs. The Spymaster team could have chosen to spend an a little more time developing more engaging game play and profited more from the viral wave they created.
The Spymaster team already understands both these points. Developer Eston Bond commented here yesterday that “we are literally only three weeks into the development cycle and on our first shot at having ever built an online game. I’m sure the team and I still have a lot more to learn about compelling gameplay, and at the end of the day it’s going to be the players that help shape its future.”
Full marks, Eston.