App Quality Dashboard

GO Keyboard

2.4 / 5

Chhi Score

This app is performing


Medium Risk


High Risk




Medium Risk






  • Install time: Icon 37.93 Sec
  • Launch time: Icon 2.71 Sec
  • Application size: Icon 19.92 MB
  • Last tested on : 18/05/2017
  • Build ID
    :   v3.15
  • Chhi Score
    :   2.4
  • Change Rate
    :   0%

What to fix?

2 Risk(s) are due to Data Sent/Received in Network 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.

Potential risk in CPU: Utilization has gone up by 6.67% compared to build v3.13

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

Build v3.13 did better in Network . Spikes in Network contributed to score drop by 41.46%

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

Fixing CPU risks could drastically improve Chhi Score. There are 7 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

8 tests need immediate attention. View performance graph.

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

Build v3.13 did better in Memory . Spikes in Memory contributed to score drop by 2.56%

Consider re-merging the code from build v3.13, Network score was 4.1

Utilization of CPU is close to the threshold.

Network utilization on Micromax Canvas AQ4502 exceeded 1024 KB, you might want to consider bringing it down

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

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

App makes 3993.85 KB of network requests. Moving this to a background thread will improve load speed. View details

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

Network utilization on YU Yuphoria exceeded 1024 KB, you might want to consider bringing it down

53.34 MB of App Dalvik utilized by activity com.jb.gokeyboard.preferences.KeyboardEnableGKActivity. View details

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

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

Your average App Dalvik usage surged by 9.93%, Your memory score is 3.8

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

347 apps having similar CPU load have low Chhi Scores

Total Network data consumed was 3993.85KB in YU Yuphoria , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

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

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

Screen Coverage

competition benchmark

This app is ranked #1480 in Tools