App Quality Dashboard

ClevCalc

3.1 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 10.96 Sec
  • Launch time: Icon 2.34 Sec
  • Application size: Icon 4.49 MB
  • Last tested on : 12/06/2017
  • Build ID
    :   v2.13.10
  • Chhi Score
    :   3.1
  • Change Rate
    :   0%

What to fix?

Build 2.13.9 did better in Memory . Spikes in Memory contributed to score drop by 3.45%

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

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

Build 2.13.9 did better in CPU . Spikes in CPU contributed to score drop by 17.39%

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

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

22 tests need immediate attention. View performance graph.

Build 2.13.9 did better in Network . Spikes in Network contributed to score drop by 4.55%

Utilization of CPU is close to the threshold.

Utilization of Memory is close to the threshold.

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

64.96 MB of App Dalvik utilized by activity com.dencreak.dlcalculator.DLCalculatorActivity. View details

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

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

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

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

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 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!

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

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

Caching: Use LruCache for data caching to optimize memory usage

Your average App Dalvik usage surged by 21.72%, Your memory score is 2.8

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

Screen coverage

competition benchmark

This app is ranked #742 in Productivity

737
738
739
740
741
back-to-top