App Quality Dashboard

Offender Search

1.6 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 30.32 Sec
  • Launch time: Icon 7.52 Sec
  • Application size: --- 24.42 MB
  • Last tested on : 05/05/2017
  • Build ID
    :   v13.6.0
  • Chhi Score
    :   1.6
  • Change Rate
    :   0%

What to fix?

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

22 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.

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

Your App CPU is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage

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

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

22 tests need immediate attention. View performance graph.

The app's Memory score has improved by 4% compared to build v13.4.0! Good job!

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

1 Risk(s) are due to App Total in Memory exceeding the threshold.

The app took 7.52 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details

Utilization of Memory is close to the threshold.

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

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

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

31 apps having similar CPU load have low Chhi Scores

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

70.24 MB of App Dalvik utilized by activity com.life360.android.first_user_experience.login_screens.CreateAccountPhoneActivity. View details

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

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

Screen coverage

Test Flows YU Yuphoria Lava Iris X8 Panasonic P55 LYF Karbonn Titanium Machfive Zenfone 2 Laser Lenovo VIBE K4 Note Lenovo A6000

Install app

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 1

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 2

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

competition benchmark

This app is ranked #75 in Parenting

70
71
72
73
74
back-to-top