App Quality Dashboard

Full Body Fat Burning Workout!

2.8 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: 16.44 Sec
  • Launch time: 1.61 Sec
  • Application size : 30.64 MB
  • Last tested on : 04/05/2017
  • Build ID
    :   v1.0
  • Chhi Score
    :   2.8
  • Change Rate
    :   0%

What to fix?

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

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

4 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 4 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.

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

7 tests need immediate attention. View performance graph.

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

Utilization of CPU is close to the threshold.

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

57.31 MB of App Dalvik utilized by activity com.template.activities.MainActivity. View details

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.

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

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

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

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

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

Screen coverage

Test Flows Panasonic P55 LYF-WATER Micromax Canvas AQ4502 Lenovo VIBE K4 Note Samsung Galaxy J7 Motorola Moto E (2nd gen)

Install app

  • Risk

  • Success

  • Success

  • Success

  • Success

  • Risk

Scenario 1

  • Risk

  • Success

  • Failure

  • Failure

  • Risk

  • Risk

Scenario 2

  • Risk

  • Failure

  • Failure

  • Risk

competition benchmark

This app is ranked #808 in Health & Fitness

803
804
805
806
807
back-to-top