App Quality Dashboard

TkMixiViewer

3.9 / 5

Chhi Score

This app is performing

Average

Good

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 10.00 Sec
  • Launch time: Icon 2.32 Sec
  • Application size: --- 2.67 MB
  • Last tested on : 11/06/2017
  • Build ID
    :   v7.2.9
  • Chhi Score
    :   3.9
  • Change Rate
    :   +62.5 %

What to fix?

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

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

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 37.5% compared to build v7.2.8! Good job!

Utilization of Network is close to the threshold.

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

5 tests need immediate attention. View performance graph.

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

Printing logs on callbacks would make debugging easy for tests run in our platform

45.15 MB of App Dalvik utilized by activity jp.takke.android.tkmixiviewer.ui.LoginConfig. View details

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

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

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

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

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

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

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

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

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

The app's Network score has improved by 53.85% compared to build v7.2.8! Good job!

Well done, Network consumption has come down by 59.97 % compared to build v7.2.8

The app's Memory score has improved by 10.53% compared to build v7.2.8! Good job!

Screen Coverage

competition benchmark

This app is ranked #235 in Social

230
231
232
233
234
back-to-top