What can app developers learn from Candy Crush?
[tboot_icon icon="quote-left" size="2x"] I spent a Saturday afternoon “studying” Candy Crush and taking heaps of screenshots and found the monetization and social features to be fascinating.[tboot_icon icon="quote-right" size="2x"]
The game Candy Crush is a lot of fun and really addictive. It’s so addictive that I wouldn’t recommend trying it if you have any other commitments that day! People that get addicted have been known to waste substantial amounts of money on it.
The interesting thing about Candy Crush from an app developer’s perspective is it’s use of social media and it’s monetization strategy: WAIT, SOCIALIZE or PAY or WaSP for short.
CC is very similar to Bejeweled, which is one of the most successful games of all time. CC goes a few steps beyond Bejeweled in making the game addictive and does an admirable job of adding the social component to the game. As a side effect the game is more fun and supremely viral. CC includes a number of social interactions and cues:
- Your friend’s position in the game is shown on the map of Candy Land [screenshot].
- Your friend’s high scores and their pictures appears at the bottom of the screen [screenshot].
- You can invite friends to join [screenshot].
- You can ask your Facebook friends for lives! [screenshot]
- You can give lives to your friends (in theory: the functionality was broken) [screenshot] [screenshot]
- Not only does it give you a score, but CC identifies which friend’s score you have beaten [screenshot] and gives you an option brag about it to them [screenshot].
The essence of these interactions are:
- Friendly Competition
The competitive aspects of Candy Crush are not applicable to non-game apps. However, if an app has in-app purchases, Facebook invitations and giving and receiving of items via Facebook should be directly applicable.
Candy Crush relies on in-app-purchases of a few items for monetization:
- More lives.
- A few more moves to complete a level.
- Items to help complete a level such as lollypops and fish that eat candy.
WaSP – Wait, Socialize or Pay:
CC uses a bizzarre and fascinating ploy to get a user to pay for more lives. Once the user has used up all lives, the user has three options:
- Wait for an increasing amount of time until they can play again.
- Ask for lives via facebook.
The timeout seems like a risky strategy since it risks loosing customers. On the other hand, it might prevent users from overdosing on the game and giving it up.
It would be fascinating to see the statistics for how people behave when confronted with this choice. The main questions on my mind are:
- How many people ask friends for lives?
- How many people pay for more lives?
- How many people never come back?
What did you do when you ran out of lives?
Virality Boost: asking for a life:
When a user runs out of lives, she can wait, pay or ask a friend for a life. The process that that friend has to go through is:
- The friend gets a facebook request to download the app [screenshot].
- Then the user has to play one level,
- and only then do they get the request for the life [screenshot].
- They then need to send a life via Facebook.
In my case, the life was not delivered. I assume this is due to a bug in their code.
When the user asks a friend for a life via Facebook, CC shows a dialog asking for permission to post to friends [screenshot]. When I saw this, I thought CC needed this permission to ask a friend for a new life on my behalf.
However, CC used this to spam all my friends that I was using CC!! The post is concealed from me as it did not appear on my own Facebook timeline or in my feed. I only found out when a friend liked the post. This was embarrassing.
Wait: Since we make video creation apps the idea of making our users wait to record a video would not fly! However, we have already incorporated the Wait strategy into our app. Users can play a set number previews of the sound effect items. When the previews are used up, the user can pay to unlock all the sounds, or wait until the next day to continue. Users can continue to use the basic set of sounds and use all other features such as the “PVR for real life” feature, adding badges as well as composing and sharing videos.
Socialize: In our case, sharing of videos via Facebook gives a bit of virality. However, we could learn from Candy Crush here. Giving users the option of giving a friend a set of sound effects is a fun idea that our users would enjoy.
A final word: We take the privacy of our users very seriously. We would not betray our users trust by spamming about their activity on Facebook. However, in other respects, we can learn a lot from Candy Crush.
Here is a collection of screenshot depicting the various aspects of the WaSP strategy. The images were anonymized using Facepixelizer.