Better Inclusive Performance

DroidKeeper app is a performance application for Android devices that allows to clean up cache, optimize memory, and scan for viruses to speed up your phone.

Role: Product Designer
Team: 10+ Product Designers
Date: Summer 2017

The Goal

Identify the problem in app using Google Analytics and suggest possible solutions for fixing it.

Product Owner Interview > Deep dive into GA > Fails > The Problem > Suggestions (image)

Looking for a problem

As an entry point for this product our team had an interview with Product Owner and some other stakeholders in product team. (describe problems and goals for the team)

  • Add story about going through tons of data to identify what was the reason behind performance on different devices

To identify areas that might be improved I’ve went very deep into Google Analytics, I wasn’t looking at anything specifically rather trying to find a gaps. I went through more than ten different hypothesis around common reasons that might cause bugs or another experience issues: various screen resolutions, seasons, trends, mobile device models, etc.

For none of it I couldn’t get strong confirmation of the existing pattern, unless I’ve decided to check usability of Android versions from different angles. It appears that users with different Android versions have a remarkable difference in User Retention index. I looked at the cohort analysis for 3 user segments by weeks.

According to the chart, on the week 6 users with Android 6.x.x has 3 times higher user retention than users with Android 4.x.x, as well as 17 times higher than users with Android 5.x.x

 

Also it is clear that recession occurs on week 1, so I’ve looked at cohort analysis for this period by day. Now it’s clear that that issue happens almost immediately after install - during the first day of use.

To clarify the problem I researched users' behavior by checking existing events. It turned out that users interact more or less in the same way with the app, there was no unique usability patterns based on Android version. So there was another reason for them to drop off.

Since the issue is happing during 1st day of use I decided to check events connected to the 1st launch of an app on the device. As we might see the duration of the 1st scan on Android 4.x.x. is twice higher than on Android 6.x.x. and 3 times higher than on Android 5.x.x. We also might notice a significant difference in launching the app itself.

Possible solution

By decreasing the first launch time, we can build engaging relationships with users and prevent them from dropping off.

Currently, the layout of a home page is designed to include a lot of features and additional info about the device, so it takes a user to scroll for a while until everything is introduced to her. By limiting what’s available from the start and loading on a background some secondary functions, we can maintain the time it takes from launch to actual use of the app. The same approach might apply to the key feature - a quick fix. Then, instead of waiting for the complete analysis, we can show its progress with founded issues along the way.