App Quality Dashboard

Aqualert

1.3 / 5

Chhi Score

This app is performing

Poor

Memory

Medium Risk

/5

CPU

High Risk

/5

crash

High  Risk

/5

network

Medium Risk

/5

Competition

#

 

Category

Rank

  • Install time: Icon 10.89 Sec
  • Launch time: Icon 9.85 Sec
  • Application size: Icon 7.83 MB
  • Last tested on : 26/04/2017
  • Build ID
    :   v7.28
  • Chhi Score
    :   1.3
  • Change Rate
    :   -45.83 %

Insights (49)

What to fix?

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.overseasolutions.waterapp.app PID: 13647 java.lang.IllegalSt... Users with phone manufactured by Samsung might experience a crash on their phone!. Fix now!
2 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.overseasolutions.waterapp.app PID: 13647 java.lang.IllegalSt... Users with phone manufactured by Asus might experience a crash on their phone!. Fix now!
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.overseasolutions.waterapp.app PID: 13647 java.lang.IllegalSt... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!
Build v7.24 did better in Memory . Spikes in Memory contributed to score drop by 8%
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Oops!, The app crashed on Lenovo A6000, Motorola Moto E (2nd gen) & more devices. View details
Fixing CPU risks could drastically improve Chhi Score. There are 25 CPU risks.
Lenovo A6000 crashed at android.app.FragmentManagerImpl.enqueueAction(FragmentManager.java:1350) View details
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.overseasolutions.waterapp.app PID: 13647 java.lang.IllegalSt... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!
25 Risk(s) are due to Threads in CPU exceeding the threshold.
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
Build v7.24 did better in Network . Spikes in Network contributed to score drop by 40.48%
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 FATAL EXCEPTION: main Process: com.overseasolutions.waterapp.app PID: 13647 java.lang.IllegalSt... Users with phone manufactured by Micromax might experience a crash on their phone!. Fix now!
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.overseasolutions.waterapp.app PID: 13647 java.lang.IllegalSt... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.overseasolutions.waterapp.app PID: 13647 java.lang.IllegalSt... Users with phone manufactured by YU might experience a crash on their phone!. Fix now!
Potential risk in CPU: Utilization has gone up by 26.32% compared to build v7.24
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.overseasolutions.waterapp.app PID: 13647 java.lang.IllegalSt... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.overseasolutions.waterapp.app PID: 13647 java.lang.IllegalSt... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!
Motorola Moto E (2nd gen) crashed at android.app.FragmentManagerImpl.enqueueAction(FragmentManager.java:1435) View details
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.overseasolutions.waterapp.app PID: 13647 java.lang.IllegalSt... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!
The app took 9.85 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details
Consider re-merging the code from build v7.24, Network score was 4.2
The app has a high performance risk for the phone manufacturer(s) Asus, LYF, Motorola, Lenovo, Micromax, YU, Karbonn, Panasonic, Samsung. Check coverage report for more details.
Consider re-merging the code from build v7.24, CPU score was 1.9
Utilization of CPU is close to the threshold.
26 tests need immediate attention. View performance graph.
254 apps having similar CPU load have low Chhi Scores
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.
Your average App Dalvik usage surged by 4.89%, Your memory score is 2.3
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
App makes 5122.00 KB of network requests. Moving this to a background thread will improve load speed. View details
Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down
Network utilization on Lenovo VIBE K4 Note exceeded 1024 KB, you might want to consider bringing it down
Caching: Use LruCache for data caching to optimize memory usage
10 Tests crashed out of 27 Tests. Check where the app crashed. View details
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Testability: Providing login / sign-up details could very well improve depth of bot clicks
73.47 MB of App Dalvik utilized by activity com.overseasolutions.waterapp.app.Home. View details
Total Network data consumed was 5122.00KB in Lenovo A6000 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details
Fix & Optimize launch time using Flatbuffers for storage and rendering 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
Printing logs on callbacks would make debugging easy for tests run in our platform
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #1231 in Health & Fitness

1226
1227
1228
1229
1230
back-to-top