App Quality Dashboard

CloudProfessor

2.3 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 27.00 Sec
  • Launch time: Icon 1.30 Sec
  • Application size: Icon 13.05 MB
  • Last tested on : 14/05/2017
  • Build ID
    :   v2.00.2005
  • Chhi Score
    :   2.3
  • Change Rate
    :   -11.54 %

Insights (24)

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.
1 Risk(s) are due to Threads in CPU exceeding the threshold.
App launch time went up by 165.31% initlizate network calls after few seconds of loading the resources. View details
Build v1.06.2006 did better in Memory . Spikes in Memory contributed to score drop by 8.33%
The app has a high performance risk for the phone manufacturer(s) Lenovo, Karbonn. Check coverage report for more details.
The app's CPU score has improved by 6.25% compared to build v1.06.2006! Good job!
7 tests need immediate attention. View performance graph.
Utilization of CPU is close to the threshold.
The app's memory score is 2.2 due to high memory utilization. Needs to be fixed as priority.
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
Your average App Dalvik usage surged by 24.85%, Your memory score is 2.2
Printing logs on callbacks would make debugging easy for tests run in our platform
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
105.68 MB of App Dalvik utilized by activity com.facebook.FacebookActivity. View details
Caching: Use LruCache for data caching to optimize memory usage
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Testability: Providing login / sign-up details could very well improve depth of bot clicks
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!
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #1717 in Education

1712
1713
1714
1715
1716
back-to-top