App Quality Dashboard

Learn Java

3.2 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 11.50 Sec
  • Launch time: Icon 3.24 Sec
  • Application size: Icon 4.14 MB
  • Last tested on : 24/03/2017
  • Build ID
    :   v2.0
  • Chhi Score
    :   3.2
  • Change Rate
    :   0%

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.0.0 did better in CPU . Spikes in CPU contributed to score drop by 4.17%

5 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 5 High Risk(s).

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

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

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

8 tests need immediate attention. View performance graph.

Utilization of Network is close to the threshold.

Build v1.0.0 did better in Network . Spikes in Network contributed to score drop by 2.63%

App size increased by 16.95% See how to optimize.

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

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

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

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

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

42.55 MB of App Dalvik utilized by activity com.LM.JAVA.activities.ActivitySplash. View details

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

Screen coverage

competition benchmark

This app is ranked #1000 in Education

995
996
997
998
999
back-to-top