App Quality Dashboard

Tukang Ramal

2.8 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: 7.29 Sec
  • Launch time: 1.36 Sec
  • Application size : 2.54 MB
  • Last tested on : 02/05/2017
  • Build ID
    :   v1.8(TR)
  • Chhi Score
    :   2.8
  • Change Rate
    :   0%

What to fix?

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

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

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

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.

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

Utilization of Memory is close to the threshold.

27 tests need immediate attention. View performance graph.

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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

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

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

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

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

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

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

39.23 MB of App Dalvik utilized by activity com.balimedia.ramalan.SplashActivity. View details

Screen coverage

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

Install app

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Success

  • Risk

Scenario 1

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 2

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

competition benchmark

This app is ranked #1895 in Lifestyle

1890
1891
1892
1893
1894
back-to-top