Analyzing Your App Using Game Thinking: Part 4 – Replayability

In this series of articles, I am taking a look at how innovators and entrepreneur developing non-game apps and other products through the application of Amy Jo Kim’s Game Thinking process can analyze their work using some of the factors that game designers use to determine that the games they are developing are delivering the desired player experience. Last week I discussed how to analyze an app in terms of its Depth. This week I will focus on its Replayability.

Replayability: The ability to find enjoyment in a game after playing it multiple times.

If you played a game only once and had no desire to return to it again, either it took a very long time to play through to the end (such as with an online role-playing game that can take weeks or months to play), or it just wasn’t fun enough the first time through.  Game designers want their games to be so fun that players play a second time, a third time, a fourth time, and if the game is sufficiently deep, a hundredth time.

In Game Thinking terms, we want apps to be sufficiently experiences that users will want to return to the activity loop during the Habit-Building Phase of the Player Journey so that Newbies become Regulars.  In non-game apps, replayability can be referred to engagement, 

Engagement is often measured by how frequently users actually use an app and is defined by the average number of sessions per Daily Active User. Every time any user, not just a unique user, opens your app, that counts as a session.  If a user is very engaged in your app, they will open your app several times a day.

The essence of an app being engaging is that users find value in it; that is, it actually does satisfy the users wants and needs.  But beyond that, there are a number of tips we can take from the world of game design about how we can make non-game apps more engaging:

  • Keep your core loop tight, so that users get value quickly through short session lengths.  Triggers, actions, and feedback should be combined into a smooth and cohesive system, so that users getting constant deliveries of value, and therefore constant hunger for more.
  • In games, successful actions will often trigger a sequence of colorful graphics or other musical fanfares congratulating players for their skill, when those actions may be owed to dumb luck. Similarly, you can provide players with such positive reinforcement when they use your app successfully, particularly when done in unusual ways.  However, remember that infrequent rewards are much more effective than frequent ones, so be careful not to overuse any over-the-top feedback.
  • Find ways continually provide new content for your app, so that users never feel like they’ve experienced it all and will keep coming back for more.
  • Allowing users to customize their app or the assets produced by their app will allow users to experience a feeling of empowerment as well as greater ownership in the app.  And if they can share their customizations with other users, then they can experience the Peacock Effect — dressing to attract the attention of others.  Attracting such attention can provide the additional feelings of accomplishment and social influence.
  • If your app’s business model is based on microtransactions, allow the user to still use the core loop for free but pay for other features, such as customization or additional functionality.  Otherwise, if users are frequently confronted with a payment demand that cannot be bypassed, they may feel like they are being shaken down and will bail out without building that habit of using your app.
  • Provide resources so that users can learn how to use your app more effectively while they are not using it.  In game design, this is called metagaming, where players study game strategies to become more skilled players.  If you’ve designed a path to Mastery in your Player Journey, then consider putting online some tips for achieving mastery with your app so that users will become engaged simply through the goal to of optimizing their skill progression.

In summary, you need to design your app so that your users get value from it quickly, feel good about developing the skill to achieve that value, and can have additional content, information, features and uses to keep them coming back for more.  Of course, there is the danger of turning off some users by providing them with too much information to absorb or too many decisions to make quickly, and so, for the next and final installment in this series, we will look at the factor pace.

 

Analyzing Your App Using Game Thinking: Part 3 – Depth

In this series of articles, I am taking a look at how innovators and entrepreneur developing non-game apps and other products through the application of Amy Jo Kim’s Game Thinking process can analyze their work using some of the factors that game designers use to determine that the games they are developing are delivering the desired player experience. Last week I discussed how to analyze an app in terms of its Complexity. This week I will focus on its Depth.

Depth: The ability to find enjoyment in a game as one’s skill in playing the game increases.

One of the Cardinal Rules of game design is that games should be easy to learn but difficult to master. The “easy to learn” provision means that a game should have low Complexity, while the “difficult to master” provision means that a game should have high Depth. The greater the Depth, the more difficult it is to master the game.

Why should a game be difficult to master? Well, that just means that a game should remain challenging even as your skill in playing that game increases. In other words, a game should remain engaging no matter how many times you play it.

Depth is directly related to the number of interesting decisions the player can make, whereas Complexity is related to the number of rules there are in the game. For example:

  • Tic-Tac-Toe has few decisions, but it also has few rules
  • Chess has more rules and elements, but it has many interesting decisions
  • Monopoly has even more rules and elements, but relatively few meaningful decisions

While it is possible to learn the basic rules of Chess in just a few minutes, it might take players years, if ever, to master the game.  A game like Chess, where there is a high Depth to Complexity ratio, is referred to as design elegance by game designers. Many game designers strive for design elegance by creating as much depth as possible without too much complexity.

This can be tricky to achieve, though, since Depth (lots of interesting decisions) can come from Complexity (lots of rules), but too much Complexity can also decrease Depth.  Why?  Well, if there are too many rules in a game, it may make it too difficult to every truly master a game.

So, what does this have to do with apps that aren’t games?  If you recall The Player’s Journey from Game Thinking, Mastery is the final state of the Journey.  It is when Enthusiasts who’ve built their skills and mastered the system are ready for something more.  If your app has Depth, there will be something more to give your Enthusiasts.  That is, it will still have value for users who have used your app for a long period of time.

Game designers have given a lot of thought to how to add Depth to a game, because the Enthusiasts who have mastered the game are often its best promoters and it’s important to keep them loyal.  Here are some take-aways from game design that you can use to add Depth to your app:

  • Providing the more advanced users with different ways to use the app’s main action, different actions to perform or even different overall uses for your app will increase the users sense of freedom of choice within the app.  However, these different choices need to produce different results for them to be meaningful and truly create an app with Depth.
  • If the knowledge or timing of when your users use the main action of the Core Learning Loop is a factor in determining how useful that action is, then your app already has a potential for Mastery.  The better your users get at acquiring the right knowledge or adjusting their timing, the more skill they develop on the Journey to Mastery.
  • If the timing of using your app’s action involves any trade-offs; that is using the action for one purpose at a given time might be at the expense of the benefits of doing something else instead, that strategic knowledge of when or the best order to use your app’s action can form the basis of Mastery.
  • While your app may built upon a single Core Learning Loop, you can design in different actions to support, expand on, or provide variations of the main action your users use, each of which makes it possible for users to train in additional skills.
  • Allowing the users with learning how the rules of cause and effect work in your app without experiencing any actual negative consequences can encourage users to learn about all the different ways your app can be used.  Such experimentation will allow users to gain information about how your app works, and that knowledge can lead to Mastery of your app.
  • Allowing users to use the actions as expressions of creativity, particularly if they can share those expressions with others, can give users a sense of creative control that can lead to Mastery.  Such expressions of creativity can be as non-obtrusive to your app’s main function as allowing the users to create the look of their avatars or change the skin of the user interface, or it may be the main purpose of the app, such as with a photo editing app.
  • Congratulatory messages for using the app well and prompting about what features can be unlocked as the users improve their skills can help motivate them to achieve Mastery.

Unfortunately, there are also mistakes you can make that can interfere with creating a Player Journey to Mastery:

  • If your app is too Difficult for people to use in the Onboarding or Habit-Building stages, they will bail on it before reaching Mastery.
  • If your app is not Complex enough to provide increased utility (more things for your users to do) as their skills in using it improve, there is little motivation for them to keep on using your app to improve their skills.

Of course, these considerations are all for users who already have become skilled in using your app.  But what about the users who are still in the Habit-Building stage?  What will keep them returning to your app so that they can build that habit?  This is what game designers call Replayability, and we will examine that factor next week.