App Quality Dashboard

Xploree Keyboard

2.9 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 29.15 Sec
  • Launch time: Icon 0.96 Sec
  • Application size: Icon 23.99 MB
  • Last tested on : 26/02/2017
  • Build ID
    :   vV2.3.2
  • Chhi Score
    :   2.9
  • Change Rate
    :   -9.38 %

What to fix?

Build V2.3.1 did better in Memory . Spikes in Memory contributed to score drop by 10%

4 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.

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

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

Utilization of CPU is close to the threshold.

The app's CPU score has improved by 4.35% compared to build V2.3.1! Good job!

9 tests need immediate attention. View performance graph.

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

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

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

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

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.

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

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 3.96%, Your memory score is 2.7

Caching: Use LruCache for data caching to optimize memory usage

53.85 MB of App Dalvik utilized by activity com.kpt.xploree.activity.SetupWizardActivity. View details

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

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

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

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

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

Well done, Network consumption has come down by 28.02 % compared to build V2.3.1

Screen Coverage

competition benchmark

This app is ranked #1725 in Lifestyle