App Quality Dashboard

Translator

1.8 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

High Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: 11.00 Sec
  • Launch time: 0.92 Sec
  • Application size : 2.89 MB
  • Last tested on : 17/05/2017
  • Build ID
    :   v1.5
  • Chhi Score
    :   1.8
  • Change Rate
    :   0%

What to fix?

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

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.

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

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

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

3 tests need immediate attention. View performance graph.

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

Utilization of Memory is close to the threshold.

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

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

42.28 MB of App Dalvik utilized by activity laclaveganadora.translator.MainActivity. View details

347 apps having similar CPU load have low Chhi Scores

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

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

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

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

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.

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

Screen coverage

Test Flows Lenovo VIBE K4 Note

Install app

  • Risk

Scenario 1

  • Risk

Scenario 2

  • Risk

competition benchmark

This app is ranked #1604 in Tools

1599
1600
1601
1602
1603
back-to-top