Google Play store listing testing why & how – Optimize & increase the number of users in your app

By Liron Leshem

04

 

On my first day at work, my CEO at CallApp gave me a compelling challenge when he turned to me and said, “We need to increase the numbers of users downloading our app on day seven (an acceptable measuring metric), as quickly as we can.” The first thing I did was analyze the numbers in order to figure out where I should put my efforts in order to maximize the results and show improvement.

After crunching the numbers, I decided that the best place to start was in trying to improve our conversion rate in Google Play Store. I will try to give you an idea of why I chose this route and what store conversion is all about.

There are several options for downloading the app but the most common are through Google Play Store (for android users). In the Play Store, a user can search for an app by either using the app name itself or by using keywords. The search will result in a list of matching apps (if keyword search is used) or the app itself will be listed. Then the user has to decide whether they are willing to install the app and try it out. The goal is to convert the search into a download, getting the user to install the app on his device (also called ASO). Logic follows that improving this process will increase our downloads.

Google provides different testing tools for this purpose on the Google Developers Console. Looking at the options, I had to decide what to use in order to increase our install numbers.  The options I looked at included:

  1. Traffic to the store – User acquisition (paid or organic).

  2. Store conversion rate.

  3. Onboarding process – The registration wizard.
  4. App retention – Increasing app usage (by the users).

It is important to note that the above options don’t require the same resources and they each have their own time frames that need to be taken into consideration. For example, “onboarding” or “new features” requires significant development efforts (and app release), which, in comparison, can take more time since there are also different tests that need to be undertaken. So the decision I had to make was between a long cycle or fast store listing tests, which just needs a good designer and open minded product manager.

Let’s take a closer look:

The current situation is:

  • Conversion in Play store page (store to install) – 25%

  • Conversion in Reg (onboarding) – 50%

  • Retention in day 7 – 30%

 

2016-12-18_11-41-45

To summarize this part –

  1. Improving conversion in the store has a major impact on the number of users (it’s the highest number).

  2. It does not require development resources.

  3. It can be easily tested and monitored using Google tools

  4. Changes can be made without the need to release a new version of the app (Google Play)

  5. That`s the fastest way to test and increase the total conversion

 

 

google-play-48Tests in Store, ASO – App Store Optimization 

2016-12-18_13-30-37

What we can test:

  1. Feature Graphics – The top image on the page

    1. Image

    2. Text / message

    3. Video – With/without

  2. App Icon – App icon (store) design

  3. Short description – App short description (80 characters top)

  4. Full description – Long App description

  5. Screenshots

    1. App screenshots – images

    2. Screenshots order

All the tests are undertaken on the live version of the APP and the tests and the results can be monitored on the Google Play developer console, which allows you to test each of the elements as well as their impact on different language audience. There are more parameters that influence the user decision of whether to download the App or not but they cannot be tested without releasing a  new version.

 

Use Case – CallApp store listing test

During the second quarter of 2016, we undertook about 60 tests in the store in an effort to tackle and analyze each of the elements. Eventually, we applied 20% of the experiments to our app’s store listing on Google Play.

Our Method

  • Each test included only one tested parameter.

  • Tests were made in different languages (to analyze the impact in different cultures)

  • We repeated each test even in cases where the test was successful to double-check our results.

 

Breakdown test by category: Total 60:

Breakdown of applied tests: Total 15:

2016-12-18_11-46-17

 

Test Case – App icon (the icon shown on the store, this is not necessarily the icon that users get on their device after they install the app)

We tested more than 20 App icons variations. Users were able to view the icon in two places:

  1. Google Play Store app list

  2. App store page

App Icon tests are a very sensitive issue as they have far reaching consequences. Any changes made will have to be reflected in the company’s marketing materials and will impact the company’s overall branding efforts. Therefore we decided that any changes we made were to be minor changes to minimize the impact on our brand.

With that said, here was the agenda for the App Icon tests:

  • Test different icon shapes

  • Different icon colors and backgrounds

  • 2D effects vs 3D

  • Out of the box

  • Add elements to the icon

  • To announce a test as a winner, the significance level should be high (the Developer Console clearly shows you have when a test variant is a winner)

 

This is the original icon with which we started with in the store.

 

play_store_icon_original

  1. Test 1 Three variations  – We added round shapes with different color backgrounds in the assumption that users are familiar with and like round shapes. We tried to highlight the Icon within the shape.

This didn’t go down well!

play_store_icon_test_1

 

  1. Test 2 – Next we tried a round shape with 3D Icon

play_store_icon_test_2

Results: This received a positive response and the new icon was applied to the product version

 

 

  1. Test 3 – We then wanted to see if using a rectangular shape would have a better response than the circle so we added a rectangular background.

This did not go down well either!

play_store_icon_test_3

  1. Test 4 – So we went back to the circles and tried a few more variations to the background colors.

This didn’t work either.

 

play_store_icon_test_4

 

  1. Test 5 – So we thought maybe changing the color of the icon itself would be a good idea. So we tried out a colorful icon, which seemed to be very popular among other apps.

Nope! That was not a hit with our users.

play_store_icon_test_5

  1. Test 6 – And then we tried our hand at round backgrounds with a 3D effect and also since many apps use the blue color scheme, we tried to break it up a little.

No! That idea did not work.

play_store_icon_test_6

  1. Test 7 – Okay, so then we tried to elevate the icon by adding a winner’s badge. I mean, everybody loves a winner, right?

Wrong!

play_store_icon_test_7

  1. Test 8 – For our last attempt we went with a round background with the 3D icon which worked in our second test and added a white border.

We had a clear winner! The results showed an overwhelmingly positive response.

2016-12-18_12-02-43

 

play_store_icon_test_8

 

 

Conclusion

 

There are no clear conclusions as to what works and what doesn’t. but with experiments you get a chance to use data to decide what works and what doesn’t, what I can tell you is that you need to implement some innovation and keep on testing all the ideas, no matter how big or small the ideas may be.

What was missing? Possibility to perform an experiment by country and not just by language is essential because optimization and localization should be by country. For example,

Spanish or French is spoken in dozens of countries, with different cultural and geo. 

Two useful practices about running experiments are testing one thing at a time and conducting hypothesis-based testing. Google provides you with great tools, but don’t forget the methodology as even A/B testing can be misleading, especially if you don’t follow the rules.

 

 

Liron Leshem – VP product at CallApp