App Quality Dashboard


3.6 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




Medium Risk






  • Install time: Icon 8.80 Sec
  • Launch time: Icon 2.46 Sec
  • Application size: Icon 2.90 MB
  • Last tested on : 14/02/2017
  • Build ID
    :   1.10
  • Chhi Score
    :   3.6
  • Change Rate
    :   +89.47 %

What to fix?

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

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

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

Build 1.01 did better in Network . Spikes in Network contributed to score drop by 38.1%

5 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 5 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 has a high performance risk for the phone manufacturer(s) Lenovo, Karbonn, Micromax, Lava, YU. Check coverage report for more details.

Utilization of Memory is close to the threshold.

The app's Memory score has improved by 13.79% compared to build 1.01! Good job!

The app's CPU score has improved by 11.76% compared to build 1.01! Good job!

13 tests need immediate attention. View performance graph.

App size increased by 13.73% See how to optimize.

Consider re-merging the code from build 1.01, Network score was 4.2

Utilization of CPU is close to the threshold.

Network utilization on YU Yuphoria exceeded 1024 KB, you might want to consider bringing it down

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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

App makes 1554.06 KB of network requests. Moving this to a background thread will improve load speed. 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

37.89 MB of App Dalvik utilized by activity com.piapps.apkshare.apps.TabsMainActivity. View details

Screen coverage

Test Flows YU Yuphoria Lava Iris X8 Karbonn Titanium Machfive Micromax Canvas A1 AQ4502 Lenovo A6000

Install app

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 1

  • Risk

  • Success

  • Risk

  • Risk

  • Risk

Scenario 2

  • Risk

  • Success

  • Risk

  • Risk

  • Risk

competition benchmark

This app is ranked #539 in Productivity