App Quality Dashboard

Dropbox

2.2 / 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 56.29 Sec
  • Launch time: Icon 10.00 Sec
  • Application size: Icon 52.90 MB
  • Last tested on : 24/10/2017
  • Build ID
    :   v64.2.2
  • Chhi Score
    :   2.2
  • Change Rate
    :   -43.59 %

Insights (25)

What to fix?

Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Fixing CPU risks could drastically improve Chhi Score. There are 14 CPU risks.
14 Risk(s) are due to Threads in CPU exceeding the threshold.
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.
16 tests need immediate attention. View performance graph.
Utilization of CPU is close to the threshold.
The app took 10.00 seconds to load on Android OS version 6.0. Usually anything more than 3.2 seconds results in user drops. View details
6 Risk(s) are due to CPU Load in CPU exceeding the threshold.
The app has a high performance risk for the phone manufacturer(s) Micromax, Lenovo, Karbonn, Motorola, Samsung, YU. Check coverage report for more details.
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
34.02 MB of App Dalvik utilized by activity com.google.android.gms.auth.api.signin.internal.SignInHubActivity. View details
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
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.
There is high probability of identifying risks running the apps with conditions
Caching: Use LruCache for data caching to optimize memory usage
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Printing logs on callbacks would make debugging easy for tests run in our platform
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
Testability: Providing login / sign-up details could very well improve depth of bot clicks
The app's Network score has improved by 4.26% compared to build v44.2.2! Good job!
Well done, Network consumption has come down by 55.3 % compared to build v44.2.2
Unlock more fixes
competition benchmark

This app is ranked #913 in Productivity

908
909
910
911
912

Dive Deeper With Performance

App Speed Report

Top 5 slow methods, High CPU Activities...

Memory Report

GC Triggers, Large Objects...

Network Report

Slow Requests, Large data transfers...
back-to-top