App Quality Dashboard

baca

1.2 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 14.00 Sec
  • Launch time: Icon 0.19 Sec
  • Application size: --- 5.62 MB
  • Last tested on : 27/05/2017
  • Build ID
    :   v3.0.7.2
  • Chhi Score
    :   1.2
  • Change Rate
    :   0%

What to fix?

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

Fixing CPU risks could drastically improve Chhi Score. There are 8 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.

Build v3.0.7.1 did better in Network . Spikes in Network contributed to score drop by 10.81%

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

8 tests need immediate attention. View performance graph.

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

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

435 apps having similar CPU load have low Chhi Scores

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

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

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

75.92 MB of App Dalvik utilized by activity com.jakata.baca.activity.MainActivity. View details

Caching: Use LruCache for data caching to optimize memory usage

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!

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

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

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

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.

The app's Memory score has improved by 2.7% compared to build v3.0.7.1! Good job!

Screen coverage

Test Flows Panasonic P55 LYF Lenovo VIBE K4 Note

Install app

  • Risk

  • Risk

  • Risk

Scenario 1

  • Risk

  • Risk

Scenario 2

  • Risk

  • Risk

  • Risk

competition benchmark

This app is ranked #1238 in News & Magazines

1233
1234
1235
1236
1237
back-to-top