App Quality Dashboard

Kili Josiyam -Tamil

0.6 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

Medium Risk

/5

Medium  Risk

/5

Good

/5

#

 

Category

Rank

  • Install time: 20.85 Sec
  • Launch time: 5.93 Sec
  • Application size : 9.41 MB
  • Last tested on : 10/05/2017
  • Build ID
    :   v1.0
  • Chhi Score
    :   0.6
  • Change Rate
    :   0%

What to fix?

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.tamilmalarapps.kilijosiyam_tamil PID: 30645 java.lang.Runt... Users with phone manufactured by Lava might experience a crash on their phone!. Fix now!

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

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

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

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

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

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

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

9 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

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.

3 Tests crashed out of 13 Tests. Check where the app crashed. View details

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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.

41.47 MB of App Dalvik utilized by activity com.tamilmalarapps.kilijosiyam_tamil.MainActivity. View details

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.

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

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

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

Screen coverage

Test Flows YU Yuphoria Lava Iris X8 Zenfone 2 Laser Lenovo A6000 Samsung Galaxy J7 Motorola Moto E (2nd gen)

Install app

  • Risk

  • Crash

  • Risk

  • Risk

  • Success

  • Risk

Scenario 1

  • Risk

  • Crash

Scenario 2

  • Risk

  • Crash

  • Risk

  • Risk

  • Risk

competition benchmark

This app is ranked #3430 in Lifestyle

3425
3426
3427
3428
3429
back-to-top