App KPIs

Part
01
of one
Part
01

App Loading Speed KPIs

After conducting extensive research, we were unable to identify KPIs or best-practice metrics for cold, warm, and hot startups for apps, as the information is not publicly available. However, we found that 48% of consumers uninstall or stop using an app due to slow speeds. Provided below are some helpful findings, as well as research strategies that explain why the requested information is unavailable.

HELPFUL FINDINGS

  • App users expect the startup time for an app to be fast. Slow load times are disappointing to the users and could lead to lousy app ratings and abandonment.
  • According to an Apteligent report, 48% of consumers uninstall or stop app-use due to slow speeds.
  • Optimizing the start time of an app based on the assumption of a cold startup can improve the performance of hot and warm startups.
  • Cold app startups pose the most significant challenge in minimizing startup time.
  • When a cold startup takes 5 seconds or longer, a warm startup take 2 seconds or longer, or hot startup take 1.5 seconds or longer, Android vitals considers the app startup to be slow.

KEY APP PERFORMANCE METRICS

  • The ANR rate, crash rate, render time (16ms and 700ms), battery wake locks, wakeups, startup time, permission denials, and app size are metrics which help to identify and correct lousy app behaviors which affect user experience.
  • Analyzing the startup time of an app helps to assess the "percentage of sessions during which users experienced slow cold, warm, or hot startup times. Slow startups can be caused by a range of issues but usually indicate the execution of heavy workloads or complex logic when initializing the app."

BEST PRACTICES TO IMPROVE APP PERFORMANCE

  • Brainstorm lousy app behaviors and eliminate them.
  • Use Android vitals to assess new app versions.
  • Identify faulty devices.
  • Identify faulty Android versions.
  • Determine and trace crashes and ANRs using crash reporting tools.
  • Prevent wake-locks and wakeups by using JobScheduling APIs.
  • Identify slow render times using FrameMetrics APIs.
  • Follow permission requests' best practices.
  • Use pre-launch reports.
  • Use Android App Bundle.

RESEARCH STRATEGY

We began our research by trying to establish an understanding of cold, warm, and hot startup of apps, which we obtained from this report. After getting familiar with this concept, we had a better understanding of the question. As such, we proceeded to identify the potential KPIs or best-practice metrics for cold, warm, and hot app startups, with a focus on gaming apps.

We did a general search for the KPIs/best practices regarding the effect of app startup speeds on bounce rates, gameplay duration, return rates, and uninstall rates of apps, to identify the availability of the information. However, we could not find any data regarding app startup speed. All the information obtained from this search was regarding the effect of page loading speeds for websites rather than apps.

We searched for the performance metrics and best practices regarding the three app startup states (cold, warm, and hot) from Google Analytics, News, and Cloud. Majority of mobile apps use the Android OS, and Google developed it, so we hoped to find this information from Google servers. However, the Analytics site only provided statistics for website traffic. In the support section, we found information about Google Analytics Goals and Ecommerce Reports (systems which can be used to track/monitor app data). From Google Cloud, we found information for KPIs for APIs, but none for app startup speeds. Thus, we abandoned this strategy, as it failed to provide any relevant findings.

Next, we searched for the requested information from tech and app development sites such as Android Developers, TechBeacon, Clearbridge Mobile, and Appery.io, among others. We found some information regarding key performance metrics for Android apps, and the best practices to improve app performance. However, the findings were not specific to gaming apps or app startup speeds. As such, we could not conclude that they were best practices for cold, warm, and hot app startups, but we included the data as part of the helpful findings. We also found metrics to improve processes and production environments, but as this was not relevant to the request in any way, we excluded it from our findings.

As a last resort, we changed our focus to finding out how to improve the bounce rates, gameplay duration, return rates, and uninstall rates of apps. We hoped to establish a trend for how the startup speed of the apps was affecting user experience, and identify potential KPIs or best-practice metrics for the same. We searched the blogs of app development companies such as Apteligent, Clearbridge Mobile, and tech news websites such as TechCrunch, Wired, and The Verge. From this search, we found methods of increasing app engagement and user retention for reducing app bugs and crashes. However, we found no information regarding the startup speeds of apps, except for a 2015 report which stated the impact of latency on user experience.
Sources
Sources