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 Mart 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.
Etiketler
Android O
Android Studio
Design
Develop
Google Play
Archive
Ekim 2020
(7)
Eylül 2020
(9)
Ağustos 2020
(18)
Temmuz 2020
(18)
Haziran 2020
(18)
Mayıs 2020
(4)
Nisan 2020
(7)
Mart 2020
(9)
Şubat 2020
(9)
Ocak 2020
(3)
Aralık 2019
(8)
Kasım 2019
(12)
Ekim 2019
(11)
Eylül 2019
(5)
Ağustos 2019
(9)
Temmuz 2019
(8)
Haziran 2019
(6)
Mayıs 2019
(15)
Nisan 2019
(10)
Mart 2019
(11)
Şubat 2019
(5)
Ocak 2019
(6)
Aralık 2018
(11)
Kasım 2018
(9)
Ekim 2018
(13)
Eylül 2018
(5)
Ağustos 2018
(13)
Temmuz 2018
(9)
Haziran 2018
(16)
Mayıs 2018
(16)
Nisan 2018
(8)
Mart 2018
(8)
Şubat 2018
(7)
Ocak 2018
(9)
Aralık 2017
(9)
Kasım 2017
(13)
Ekim 2017
(14)
Eylül 2017
(11)
Ağustos 2017
(19)
Temmuz 2017
(11)
Haziran 2017
(13)
Mayıs 2017
(21)
Nisan 2017
(12)
Mart 2017
(14)
Şubat 2017
(11)
Ocak 2017
(12)
Aralık 2016
(17)
Kasım 2016
(16)
Ekim 2016
(9)
Eylül 2016
(6)
Ağustos 2016
(7)
Temmuz 2016
(12)
Haziran 2016
(14)
Mayıs 2016
(16)
Nisan 2016
(14)
Mart 2016
(8)
Şubat 2016
(8)
Ocak 2016
(9)
Aralık 2015
(9)
Kasım 2015
(13)
Ekim 2015
(19)
Eylül 2015
(15)
Ağustos 2015
(13)
Temmuz 2015
(9)
Haziran 2015
(8)
Mayıs 2015
(10)
Nisan 2015
(10)
Mart 2015
(12)
Şubat 2015
(8)
Ocak 2015
(3)
Aralık 2014
(9)
Kasım 2014
(13)
Ekim 2014
(11)
Eylül 2014
(6)
Ağustos 2014
(2)
Temmuz 2014
(9)
Haziran 2014
(10)
Mayıs 2014
(4)
Mart 2014
(4)
Şubat 2014
(3)
Ocak 2014
(2)
Aralık 2013
(3)
Kasım 2013
(2)
Ekim 2013
(7)
Eylül 2013
(2)
Ağustos 2013
(5)
Temmuz 2013
(5)
Haziran 2013
(4)
Mayıs 2013
(9)
Nisan 2013
(3)
Mart 2013
(2)
Şubat 2013
(3)
Ocak 2013
(3)
Aralık 2012
(5)
Kasım 2012
(3)
Ekim 2012
(3)
Eylül 2012
(1)
Ağustos 2012
(1)
Temmuz 2012
(2)
Haziran 2012
(5)
Mayıs 2012
(1)
Nisan 2012
(5)
Mart 2012
(5)
Şubat 2012
(5)
Ocak 2012
(5)
Aralık 2011
(7)
Kasım 2011
(7)
Ekim 2011
(5)
Eylül 2011
(5)
Ağustos 2011
(3)
Temmuz 2011
(7)
Haziran 2011
(2)
Mayıs 2011
(5)
Nisan 2011
(6)
Mart 2011
(8)
Şubat 2011
(8)
Ocak 2011
(4)
Aralık 2010
(8)
Kasım 2010
(3)
Ekim 2010
(4)
Eylül 2010
(7)
Ağustos 2010
(6)
Temmuz 2010
(10)
Haziran 2010
(11)
Mayıs 2010
(11)
Nisan 2010
(2)
Mart 2010
(3)
Şubat 2010
(2)
Ocak 2010
(5)
Aralık 2009
(7)
Kasım 2009
(5)
Ekim 2009
(5)
Eylül 2009
(8)
Ağustos 2009
(2)
Temmuz 2009
(1)
Haziran 2009
(2)
Mayıs 2009
(5)
Nisan 2009
(12)
Mart 2009
(5)
Şubat 2009
(8)
Ocak 2009
(3)
Aralık 2008
(3)
Kasım 2008
(1)
Ekim 2008
(4)
Eylül 2008
(6)
Ağustos 2008
(4)
Haziran 2008
(1)
Mayıs 2008
(5)
Nisan 2008
(4)
Mart 2008
(5)
Şubat 2008
(2)
Ocak 2008
(5)
Aralık 2007
(3)
Kasım 2007
(5)
Feed
Newsletter
Android Developers
Google Play
Platform
Android Studio
Google Play
Jetpack
Kotlin
Docs
News
