App Quality Dashboard

Sense V2 flip clock

2.5 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 18.77 Sec
  • Launch time: Icon 2.25 Sec
  • Application size: Icon 17.16 MB
  • Last tested on : 19/05/2017
  • Build ID
    :   v2.85.01
  • Chhi Score
    :   2.5
  • Change Rate
    :   -26.47 %

What to fix?

Build v2.81.01 did better in Memory . Spikes in Memory contributed to score drop by 33.33%

Build v2.81.01 did better in CPU . Spikes in CPU contributed to score drop by 25.93%

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

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.

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

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

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

Utilization of CPU is close to the threshold.

Utilization of Memory is close to the threshold.

Consider re-merging the code from build v2.81.01, CPU score was 2.7

19 tests need immediate attention. View performance graph.

Make sure your App's PSS isn't too high. Freeing objects that aren't needed would reduce chances of getting unexpectedly killed by Android system.

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

Consider re-merging the code from build v2.81.01, Memory score was 3.3

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

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

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

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

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

Your average App Dalvik usage surged by 27.11%, Your memory score is 2.2

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

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.

48.67 MB of App Dalvik utilized by activity com.droid27.weatherinterface.WeatherForecastActivity. View details

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

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

Well done, Network consumption has come down by 18.9 % compared to build v2.81.01

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

Screen coverage

competition benchmark

This app is ranked #295 in Weather

290
291
292
293
294
back-to-top