App Quality Dashboard

25 First Alert

0.9 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 43.86 Sec
  • Launch time: Icon 9.75 Sec
  • Application size: Icon 29.53 MB
  • Last tested on : 12/04/2017
  • Build ID
    :   v4.4.800
  • Chhi Score
    :   0.9
  • Change Rate
    :   -52.63 %

What to fix?

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

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

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

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

Build 4.4.300 did better in Memory . Spikes in Memory contributed to score drop by 16.13%

Potential risk in CPU: Utilization has gone up by 41.18% compared to build 4.4.300

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.

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

6 tests need immediate attention. View performance graph.

Consider re-merging the code from build 4.4.300, Memory score was 3.1

Consider re-merging the code from build 4.4.300, CPU score was 1.7

Build 4.4.300 did better in Network . Spikes in Network contributed to score drop by 2.04%

The app took 9.75 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 CPU is close to the threshold.

Utilization of Memory is close to the threshold.

163.52 MB of App Dalvik utilized by activity com.wsi.android.weather.ui.MasterActivity. View details

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

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

Fix & Optimize launch time using Flatbuffers for storage and rendering performance.

Your average App Dalvik usage surged by 28.54%, Your memory score is 2.6

Testability: Providing login / sign-up details could very well improve depth of bot clicks

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

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

130 apps having similar CPU load have low Chhi Scores

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

Screen coverage

Test Flows YU Yuphoria LYF Micromax Canvas A1 AQ4502 Lenovo VIBE K4 Note Lenovo A6000

Install app

  • Risk

  • Risk

  • Risk

  • Risk

  • Success

Scenario 2

  • Risk

  • Risk

competition benchmark

This app is ranked #430 in Weather

425
426
427
428
429
back-to-top