App Quality Dashboard

OK Messages

4.0 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 18.36 Sec
  • Launch time: Icon 1.18 Sec
  • Application size: Icon 12.88 MB
  • Last tested on : 26/04/2017
  • Build ID
    :   v1.1.13
  • Chhi Score
    :   4.0
  • Change Rate
    :   +2.56 %

What to fix?

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

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

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.

8 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

Build v1.1.12 did better in Memory . Spikes in Memory contributed to score drop by 2.5%

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

Your average App Dalvik usage surged by 10.2%, Your memory score is 3.9

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

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

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

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

62.53 MB of App Dalvik utilized by activity ru.ok.messages.auth.ActAuth. View details

Caching: Use LruCache for data caching to optimize memory usage

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

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!

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

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

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

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

Well done, Network consumption has come down by 19.49 % compared to build v1.1.12

The app's Network score has improved by 2.08% compared to build v1.1.12! Good job!

Screen Coverage

competition benchmark

This app is ranked #203 in Communication