App Quality Dashboard

1Tap Cleaner

2.9 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 9.82 Sec
  • Launch time: Icon 10.35 Sec
  • Application size: Icon 4.14 MB
  • Last tested on : 18/05/2017
  • Build ID
    :   v2.96
  • Chhi Score
    :   2.9
  • Change Rate
    :   -12.12 %

What to fix?

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

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

5 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.

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

Build v2.95 did better in Memory . Spikes in Memory contributed to score drop by 16.13%

Build v2.95 did better in CPU . Spikes in CPU contributed to score drop by 18.18%

8 tests need immediate attention. View performance graph.

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

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

Utilization of CPU is close to the threshold.

The app took 10.35 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details

Consider re-merging the code from build v2.95, Memory score was 3.1

Utilization of Memory is close to the threshold.

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

48.73 MB of App Dalvik utilized by activity com.a0soft.gphone.acc.wnd.DashboardWnd. View details

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

Your average App Dalvik usage surged by 39.52%, Your memory score is 2.6

Well done, Network consumption has come down by 50.04 % compared to build v2.95

The app's Network score has improved by 4.44% compared to build v2.95! Good job!

Screen coverage

Test Flows YU Yuphoria Panasonic P55 LYF-WATER Zenfone 2 Laser Micromax Canvas AQ4502 Lenovo VIBE K4 Note Lenovo A6000 Motorola Moto E (2nd gen)

Install app

  • Success

  • Success

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 1

  • Success

Scenario 2

  • Risk

  • Risk

  • Risk

competition benchmark

This app is ranked #1339 in Tools

1334
1335
1336
1337
1338
back-to-top