App Quality Dashboard

My First Words:24+ Months

1.5 / 5

Chhi Score

This app is performing


Medium Risk


High Risk










  • Install time: Icon 11.54 Sec
  • Launch time: Icon 6.39 Sec
  • Application size: Icon 11.44 MB
  • Last tested on : 27/04/2017
  • Build ID
    :   v1.3
  • Chhi Score
    :   1.5
  • Change Rate
    :   -60.53 %

What to fix?

Build 1.2 did better in Memory . Spikes in Memory contributed to score drop by 38.89%

Potential risk in CPU: Utilization has gone up by 33.33% compared to build 1.2

App launch time went up by 20.11% initlizate network calls after few seconds of loading the resources. View details

Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps

Fixing CPU risks could drastically improve Chhi Score. There are 13 CPU risks.

Your App CPU is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage

13 Risk(s) are due to Threads in CPU exceeding the threshold.

Test more often so that you don't break the CPU handling further in your next builds. CPU Score is in danger zone. Heavy battery consumption expected.

The app has a high performance risk for the phone manufacturer(s) Motorola, OnePlus, Coolpad, YU, Spice, Karbonn. Check coverage report for more details.

App size increased by 15.79% See how to optimize.

Consider re-merging the code from build 1.2, Memory score was 3.6

Build 1.2 did better in Network . Spikes in Network contributed to score drop by 14.58%

Consider re-merging the code from build 1.2, CPU score was 2.1

The app took 6.39 seconds to load on Android OS version 6.0. Usually anything more than 3.2 seconds results in user drops. View details

13 tests need immediate attention. View performance graph.

Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!

Testability: Providing login / sign-up details could very well improve depth of bot clicks

There is high probability of identifying risks running the apps with conditions

Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks

65.09 MB of App Dalvik utilized by activity com.androbaby.myfirstwords3.MainActivity. View details

Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance

Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2

282 apps having similar CPU load have low Chhi Scores

Printing logs on callbacks would make debugging easy for tests run in our platform

Optimize the app to render elements at 60 FPS for buttery smooth experience.

Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps

Caching: Use LruCache for data caching to optimize memory usage

Follow simple UI hierarchy by reducing nested layouts to Relative layouts.

Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.

Your average App Dalvik usage surged by 29.99%, Your memory score is 2.2

Fix & Optimize launch time using Flatbuffers for storage and rendering performance.

Screen Coverage

competition benchmark

This app is ranked #2164 in Education