App Quality Dashboard

अमीर कैसे बने

1.8 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk


Medium  Risk


Medium Risk






  • Install time: Icon 6.25 Sec
  • Launch time: Icon 0.56 Sec
  • Application size: --- 2.50 MB
  • Last tested on : 30/04/2017
  • Build ID
    :   v1.2
  • Chhi Score
    :   1.8
  • Change Rate
    :   0%

What to fix?

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

Build v1.3 did better in Memory . Spikes in Memory contributed to score drop by 17.07%

Fixing CPU risks could drastically improve Chhi Score. There are 4 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.

Build v1.3 did better in Network . Spikes in Network contributed to score drop by 64%

Build v1.3 did better in CPU . Spikes in CPU contributed to score drop by 31.71%

Must fix: App crashed because of 1233): FATAL EXCEPTION: main 1233): Process: com.coralandroid.aamirkaisebane PID: 1233 1233):... Users with phone manufactured by Micromax might experience a crash on their phone!. Fix now!

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

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

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

Consider re-merging the code from build v1.3, Network score was 5.0

Consider re-merging the code from build v1.3, CPU score was 4.1

Consider re-merging the code from build v1.3, Memory score was 4.1

Panasonic P55, Micromax Canvas A1, LYF has moved from Good to Medium risk due to RISK . View details

4 tests need immediate attention. View performance graph.

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

Network utilization on LYF exceeded 1024 KB, you might want to consider bringing it down

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

Total Network data consumed was 1448.61KB in LYF , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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.

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

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

Your average App Dalvik usage surged by 46.54%, Your memory score is 3.4

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

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

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

33.06 MB of App Dalvik utilized by activity com.coralandroid.aamirkaisebane.MainActivity. View details

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

competition benchmark

This app is ranked #1775 in Entertainment