App Quality Dashboard

Birthday

0.8 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 11.86 Sec
  • Launch time: Icon 0.42 Sec
  • Application size: Icon 3.17 MB
  • Last tested on : 20/05/2017
  • Build ID
    :   v1.1.5
  • Chhi Score
    :   0.8
  • Change Rate
    :   -55.56 %

What to fix?

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

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

Potential risk in CPU: Utilization has gone up by 41.18% compared to build v1.1.3

Build v1.1.3 did better in Memory . Spikes in Memory contributed to score drop by 22.22%

App launch time went up by INF% 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.

Potential risk in Network: Utilization has gone up by71.43% compared to build v1.1.3

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

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

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

Consider re-merging the code from build v1.1.3, Memory score was 2.7

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

Utilization of CPU is close to the threshold.

Consider re-merging the code from build v1.1.3, CPU score was 1.7

7 tests need immediate attention. View performance graph.

Consider re-merging the code from build v1.1.3, Network score was 4.2

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!

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

213 apps having similar CPU load have low Chhi Scores

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

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

Your average App Dalvik usage surged by 48.8%, Your memory score is 2.1

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

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

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

Total Network data consumed was 1937.10KB 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

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

Network utilization on Karbonn Titanium Machfive exceeded 1024 KB, you might want to consider bringing it down

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

61.83 MB of App Dalvik utilized by activity com.emojifamily.emoji.keyboard.art.love.MainActivity. View details

Screen Coverage

competition benchmark

This app is ranked #750 in Social

745
746
747
748
749
back-to-top