App Quality Dashboard

Alarmy

3.9 / 5

Chhi Score

This app is performing

Average

Good

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 22.13 Sec
  • Launch time: Icon 0.92 Sec
  • Application size: Icon 11.23 MB
  • Last tested on : 04/05/2017
  • Build ID
    :   v23.3
  • Chhi Score
    :   3.9
  • Change Rate
    :   0%

What to fix?

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

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

1 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.

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

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's CPU score has improved by 4.17% compared to build v23.2! Good job!

Build v23.2 did better in Network . Spikes in Network contributed to score drop by 2.38%

Utilization of CPU is close to the threshold.

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

Utilization of Memory is close to the threshold.

8 tests need immediate attention. View performance graph.

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

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.

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

44.09 MB of App Dalvik utilized by activity droom.sleepIfUCan.activity.SetAlarmActivity. View details

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

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!

Network utilization on Micromax Canvas A1 exceeded 1024 KB, you might want to consider bringing it down

Caching: Use LruCache for data caching to optimize memory usage

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

App makes 1372.22 KB of network requests. Moving this to a background thread will improve load speed. View details

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

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

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

Screen coverage

competition benchmark

This app is ranked #535 in Lifestyle

530
531
532
533
534
back-to-top