App Quality Dashboard

CBR Theorie

2.3 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 28.60 Sec
  • Launch time: Icon 0.93 Sec
  • Application size: Icon 49.20 MB
  • Last tested on : 12/05/2017
  • Build ID
    :   v1.29
  • Chhi Score
    :   2.3
  • Change Rate
    :   -28.13 %

What to fix?

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.

Build v1.28 did better in Memory . Spikes in Memory contributed to score drop by 25%

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

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

4 tests need immediate attention. View performance graph.

The app's memory score is 2.1 due to high memory utilization. Needs to be fixed as priority.

The app's CPU score has improved by 3.33% compared to build v1.28! Good job!

Consider re-merging the code from build v1.28, Memory score was 2.8

Your average App Dalvik usage surged by 20.04%, Your memory score is 2.1

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

38.66 MB of App Dalvik utilized by activity com.deepriverdev.theorytest.ui.main.MainActivity. View details

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

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

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

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

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

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

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

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.

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

competition benchmark

This app is ranked #1725 in Education