App Quality Dashboard

Life

1.1 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

High Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: 8.77 Sec
  • Launch time: 8.21 Sec
  • Application size : 3.26 MB
  • Last tested on : 12/06/2017
  • Build ID
    :   v1.4.3
  • Chhi Score
    :   1.1
  • Change Rate
    :   0%

What to fix?

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

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

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.

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

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

Your App Memory 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

Fixing Network risks could drastically improve Chhi Score. There are 9 Network risks.

9 Risk(s) are due to Data Sent/Received in Network 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

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.

25 tests need immediate attention. View performance graph.

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

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

The app has a high performance risk for the phone manufacturer(s) Motorola, LYF, YU, Micromax, Panasonic, Asus, Samsung, Lenovo. Check coverage report for more 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

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

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

Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down

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

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

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

Total Network data consumed was 10777.59KB in Motorola Moto E (2nd gen) , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

Caching: Use LruCache for data caching to optimize memory usage

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

Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down

347 apps having similar CPU load have low Chhi Scores

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

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

99.10 MB of App Dalvik utilized by activity com.emojifamily.emoji.keyboard.art.love.MainActivity. 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

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

Screen coverage

competition benchmark

This app is ranked #1810 in Tools

1805
1806
1807
1808
1809
back-to-top