App Quality Dashboard

Counting In Filipino

0.3 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

Medium Risk

/5

High  Risk

/5

Good

/5

#

 

Category

Rank

  • Install time: 8.00 Sec
  • Launch time: 1.32 Sec
  • Application size : 3.88 MB
  • Last tested on : 17/05/2017
  • Build ID
    :   v1.2
  • Chhi Score
    :   0.3
  • Change Rate
    :   0%

What to fix?

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.baguiosfinest.android.countinginfilipino PID: 17807 java.l... Users with phone manufactured by Lava might experience a crash on their phone!. Fix now!

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 3 CPU risks.

Your App Memory 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

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.baguiosfinest.android.countinginfilipino PID: 17807 java.l... Users with phone manufactured by Asus might experience a crash on their phone!. Fix now!

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

The app's memory score is 1.1 due to high memory utilization. Needs to be fixed as priority.

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

Utilization of CPU is close to the threshold.

3 tests need immediate attention. View performance graph.

Make sure your App's PSS isn't too high. Freeing objects that aren't needed would reduce chances of getting unexpectedly killed by Android system.

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

Caching: Use LruCache for data caching to optimize memory usage

34.56 MB of App Dalvik utilized by activity com.baguiosfinest.android.countinginfilipino.MainActivity. View details

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

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

The app has crashed on few device(s)! View details

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

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

4 Tests crashed out of 6 Tests. Check where the app crashed. View details

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

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

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

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

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

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

Screen Coverage

competition benchmark

This app is ranked #2339 in Education

2334
2335
2336
2337
2338
back-to-top