Jetpack
Kotlin
Docs
News
Platform
Android Studio
Google Play
Jetpack
Kotlin
Docs
News
Platform
Android Studio
Google Play
Jetpack
Kotlin
Docs
News
More
Android Developers Blog
The latest Android and Google Play news for app and game developers.
Find success on Google Play: What app developers can learn from games
02 März 2016
Posted by Matteo Vallone, Business Development Manager at Google Play
(As a way to reach more app developers and help them grow successful businesses on Google Play, this post was first
published on The Next Web
– Ed.)
There is much common ground between freemium apps and games businesses when it comes to achieving success. Users are, however, more used to paying for games than apps, stemming from the history of traditional gaming consoles. Moreover, mobile games are also able to easily offer ‘virtual goods’ across a range of price points to suit every pocket. This means that game developers have had plenty of opportunity to learn about how to improve onboarding, conversion, and ultimately the user Lifetime Value (LTV). So what can app developers learn from game developers? Here are some best practice tips and insights from successful game developers that can be applied to many apps, today.
Drive app success the game developer way:
1. Optimize retention before investing in acquisition
Retention is king, and retention drives conversion. For games developers, retention is the key measure of game quality and whether it appeals to players.
Most game developers will “soft launch” to beta testing communities or test markets. During this phase, the game is tweaked to optimize retention by looking into specific areas, such as tutorial completion, level difficulty and conversion. Developers can then track retention using the
Cohorts reports in Google Analytics
. Once retention is satisfactory, the developer can go to full launch and start investing in user acquisition.
2. Retain users with step-by-step engagement
The first seven days after install are the most critical for retention: users install several apps to try them, and decide in the first few days which ones they want to keep using. If you can retain for that time span, your app is more likely to become part of the user’s daily routine.
There are some simple ways to progressively build user engagement. It’s important to present a strong story that explains why that app is relevant to the user, while introducing them to key features. Then place features that offer the user value early, so they can be found without much effort.
This is a not a one-size-fit-all. To find the right solution, a developer needs to first make assumptions on what user flows can improve retention and then run A/B tests to validate or correct them. For example, a developer could think that introducing sign-in later in the user flow might improve retention. Also, the developer needs to keep in mind what the key long term engagement metrics are for the individual app (such as photos uploaded or the number of articles read) and measure the impact of the different onboarding flows on those metrics as well.
In general, these principles are good places to start optimizing your onboarding:
Look for ways to let the users experience the app straight away, rather than taking them through a long, complex setup.
Present “activation moments” — such as registering an account, uploading a video, or finding friend — gradually
Start by requiring minimal investment by the user, then ask them for more details as they are needed to use the apps features.
Treat permissions as a service for the user. For example, if you want users to register, show them in advance that, by making their experience more personal, they’ll get more value from the app.
In this example, OkCupid tried different onboarding flows and found the most engaging version increased seven-day retention by over 20 percent.
Finally, ensure the user can understand the value of your app before you start asking them to pay. Game developers are particularly good at letting their users try most or all product features for free in in a set number of days or sessions.
A great tool to help analyze how users are engaging (or not) with the app is through the
Flow Report in Google Analytics
. Using this report, a developer can see how users navigate through the app and where they leave to identify potential roadblocks.
3. Target the right offers at the right users
Understanding different groups of users in-app purchase behavior is the key to devising strategies to encourage them to spend.
Start by identifying groups of users by how they spend and much they are likely to spend. It may be by age group, the channel that brought the install, or in-app behaviour. Use the
Segment builder in Google Analytics
to identify and define these groups of users. Then, tailor in-app purchase offers to match the segments spending behavior. For example, for segments where multiple users tend to spend more in one go, but spend infrequently, offer them in-app features bundled together.
4. Offer in-app purchases when users are most likely to spend
Users are also more likely to spend, if the purchasing experience is frictionless, and even more so when they can see how the expenditure will add value. So:
Present purchase opportunities to users when they’re most likely to need or want it — and explain to the user why it’s relevant.
Make purchasing accessible easily from within the app with a minimum number of taps. For example, offer an upgrade button on the footer of relevant screens.
TomTom added a countdown to indicate when the free service runs out (counted in kilometers travelled). The counter includes a button to upgrade offering a one tap in-app purchase.
Like all good game developers, they focus on building good experiences that retain and engage users through constant testing and analytics. First impressions are important, so users need to be able to quickly understand the importance of the app and easily navigate through the onboarding experience. And to start generating revenue, it is important to be thoughtful about how to make in-app purchases actionable.
Watch Matteo’s Playtime 2015 session ‘The rules of games, for apps’
to hear more in-depth insights which app developers can learn from games with best practices and developer examples:
You can also
watch the other sessions from Google Playtime 2015
to learn more about tools and best practices which can help you find success with business on Google Play.
Labels
Android O
Android Studio
Design
Develop
Google Play
Archive
Dezember 2022
(1)
November 2022
(22)
Oktober 2022
(23)
September 2022
(13)
August 2022
(10)
Juli 2022
(6)
Juni 2022
(10)
Mai 2022
(21)
April 2022
(8)
März 2022
(16)
Februar 2022
(9)
Januar 2022
(6)
Dezember 2021
(8)
November 2021
(4)
Oktober 2021
(15)
September 2021
(11)
August 2021
(7)
Juli 2021
(15)
Juni 2021
(9)
Mai 2021
(18)
April 2021
(10)
März 2021
(12)
Februar 2021
(11)
Januar 2021
(3)
Dezember 2020
(7)
November 2020
(7)
Oktober 2020
(7)
September 2020
(9)
August 2020
(18)
Juli 2020
(18)
Juni 2020
(18)
Mai 2020
(4)
April 2020
(7)
März 2020
(9)
Februar 2020
(9)
Januar 2020
(3)
Dezember 2019
(8)
November 2019
(12)
Oktober 2019
(11)
September 2019
(5)
August 2019
(9)
Juli 2019
(8)
Juni 2019
(6)
Mai 2019
(15)
April 2019
(10)
März 2019
(11)
Februar 2019
(5)
Januar 2019
(6)
Dezember 2018
(11)
November 2018
(9)
Oktober 2018
(13)
September 2018
(5)
August 2018
(13)
Juli 2018
(9)
Juni 2018
(16)
Mai 2018
(16)
April 2018
(8)
März 2018
(8)
Februar 2018
(7)
Januar 2018
(9)
Dezember 2017
(9)
November 2017
(13)
Oktober 2017
(14)
September 2017
(11)
August 2017
(19)
Juli 2017
(11)
Juni 2017
(13)
Mai 2017
(21)
April 2017
(12)
März 2017
(14)
Februar 2017
(11)
Januar 2017
(12)
Dezember 2016
(17)
November 2016
(16)
Oktober 2016
(9)
September 2016
(6)
August 2016
(7)
Juli 2016
(12)
Juni 2016
(14)
Mai 2016
(16)
April 2016
(14)
März 2016
(8)
Februar 2016
(8)
Januar 2016
(9)
Dezember 2015
(9)
November 2015
(13)
Oktober 2015
(19)
September 2015
(15)
August 2015
(13)
Juli 2015
(9)
Juni 2015
(8)
Mai 2015
(10)
April 2015
(10)
März 2015
(12)
Februar 2015
(8)
Januar 2015
(3)
Dezember 2014
(9)
November 2014
(13)
Oktober 2014
(11)
September 2014
(6)
August 2014
(2)
Juli 2014
(9)
Juni 2014
(10)
Mai 2014
(4)
März 2014
(4)
Februar 2014
(3)
Januar 2014
(2)
Dezember 2013
(3)
November 2013
(2)
Oktober 2013
(7)
September 2013
(2)
August 2013
(5)
Juli 2013
(5)
Juni 2013
(4)
Mai 2013
(9)
April 2013
(3)
März 2013
(2)
Februar 2013
(3)
Januar 2013
(3)
Dezember 2012
(5)
November 2012
(3)
Oktober 2012
(3)
September 2012
(1)
August 2012
(1)
Juli 2012
(2)
Juni 2012
(5)
Mai 2012
(1)
April 2012
(5)
März 2012
(5)
Februar 2012
(5)
Januar 2012
(5)
Dezember 2011
(7)
November 2011
(7)
Oktober 2011
(5)
September 2011
(5)
August 2011
(3)
Juli 2011
(7)
Juni 2011
(2)
Mai 2011
(5)
April 2011
(6)
März 2011
(8)
Februar 2011
(8)
Januar 2011
(4)
Dezember 2010
(8)
November 2010
(3)
Oktober 2010
(4)
September 2010
(7)
August 2010
(6)
Juli 2010
(10)
Juni 2010
(11)
Mai 2010
(11)
April 2010
(2)
März 2010
(3)
Februar 2010
(2)
Januar 2010
(5)
Dezember 2009
(7)
November 2009
(5)
Oktober 2009
(5)
September 2009
(8)
August 2009
(2)
Juli 2009
(1)
Juni 2009
(2)
Mai 2009
(5)
April 2009
(12)
März 2009
(5)
Februar 2009
(8)
Januar 2009
(3)
Dezember 2008
(3)
November 2008
(1)
Oktober 2008
(4)
September 2008
(6)
August 2008
(4)
Juni 2008
(1)
Mai 2008
(5)
April 2008
(4)
März 2008
(5)
Februar 2008
(2)
Januar 2008
(5)
Dezember 2007
(3)
November 2007
(5)
Feed
Newsletter
Android Developers
Google Play
Platform
Android Studio
Google Play
Jetpack
Kotlin
Docs
News
