App Quality Dashboard

Champak - Hindi

2.3 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




High Risk






  • Install time: Icon 23.06 Sec
  • Launch time: Icon 0.76 Sec
  • Application size: Icon 16.02 MB
  • Last tested on : 26/03/2017
  • Build ID
    :   v6.1
  • Chhi Score
    :   2.3
  • Change Rate
    :   +4.55 %

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.

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

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

Build v6.0 did better in CPU . Spikes in CPU contributed to score drop by 10%

7 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.

9 tests need immediate attention. View performance graph.

App size increased by 34.51% See how to optimize.

Utilization of CPU is close to the threshold.

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

Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down

Network utilization on Lava Iris X8 exceeded 1024 KB, you might want to consider bringing it down

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

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

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

Total Network data consumed was 4024.61KB in Motorola Moto E (2nd gen) , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

77.68 MB of App Dalvik utilized by activity com.magzter.champakhindi.MainActivity. View details

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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.

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

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

The app's Memory score has improved by 5.71% compared to build v6.0! Good job!

Well done, Network consumption has come down by 17.43 % compared to build v6.0

Screen Coverage

competition benchmark

This app is ranked #1567 in Entertainment