App Quality Dashboard

Fix-it for Mi Band 2

2.1 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: 11.00 Sec
  • Launch time: 1.65 Sec
  • Application size : 5.71 MB
  • Last tested on : 17/05/2017
  • Build ID
    :   v1.4.0
  • Chhi Score
    :   2.1
  • Change Rate
    :   0%

What to fix?

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

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

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

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

Fixing CPU risks could drastically improve Chhi Score. There are 3 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 has a high performance risk for the phone manufacturer(s) Lenovo. Check coverage report for more details.

6 tests need immediate attention. View performance graph.

Utilization of Memory is close to the threshold.

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

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.

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

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

40.48 MB of App Dalvik utilized by activity com.apptracker.android.module.AppModuleActivity. View details

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

App makes 3648.21 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.

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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

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

Screen coverage

Test Flows Lenovo VIBE K4 Note Lenovo A6000

Install app

  • Risk

  • Risk

Scenario 1

  • Risk

  • Risk

Scenario 2

  • Risk

  • Risk

competition benchmark

This app is ranked #995 in Health & Fitness

990
991
992
993
994
back-to-top