App Quality Dashboard

Curofy

3.9 / 5

Chhi Score

This app is performing

Average

Good

/5

Medium Risk

/5

Medium  Risk

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 25.25 Sec
  • Launch time: Icon 1.01 Sec
  • Application size: Icon 16.63 MB
  • Last tested on : 07/05/2017
  • Build ID
    :   v2.7.16
  • Chhi Score
    :   3.9
  • 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.

Must fix: App crashed because of 3393): FATAL EXCEPTION: main 3393): Process: com.curofy PID: 3393 3393): java.lang.RuntimeExcep... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!

Utilization of CPU is close to the threshold.

The app's CPU score has improved by 3.57% compared to build v2.7.09! Good job!

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

Panasonic P55 has moved from Good to Medium risk due to FAIL . View details

26.20 MB of App Dalvik utilized by activity com.curofy.SignupActivity. View details

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

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

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

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

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

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

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.

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

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

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

Well done, Network consumption has come down by 98 % compared to build v2.7.09

The app's Memory score has improved by 2.38% compared to build v2.7.09! Good job!

The app's Network score has improved by 68.97% compared to build v2.7.09! Good job!

Screen Coverage

competition benchmark

This app is ranked #165 in Medical

160
161
162
163
164
back-to-top