App Quality Dashboard


2.3 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk


Medium  Risk








  • Install time: Icon 24.10 Sec
  • Launch time: Icon 2.59 Sec
  • Application size: --- 18.79 MB
  • Last tested on : 26/04/2017
  • Build ID
    :   v11.3.0
  • Chhi Score
    :   2.3
  • Change Rate
    :   -30.3 %

What to fix?

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

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

Build v11.2.0 did better in Memory . Spikes in Memory contributed to score drop by 18.75%

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.bravolang.german PID: 11480 java.lang.IllegalStateException:... Users with phone manufactured by Samsung might experience a crash on their phone!. Fix now!

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

6 Risk(s) are due to CPU Load in CPU exceeding the threshold.

Motorola Moto E (2nd gen), Zenfone 2 Laser , Samsung Duos Galaxy J7 has moved from Good to Medium risk due to FAIL . View details

Utilization of CPU is close to the threshold.

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

21 tests need immediate attention. View performance graph.

The app's CPU score has improved by 15.38% compared to build v11.2.0! Good job!

Consider re-merging the code from build v11.2.0, Memory score was 3.2

The app has crashed on few device(s)! View details

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

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

83.73 MB of App Dalvik utilized by activity com.bravolang.german.Phrasebook. View details

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

Your average App Dalvik usage surged by 3.87%, Your memory score is 2.6

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

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

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

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

Screen Coverage

competition benchmark

This app is ranked #1687 in Education