App Quality Dashboard

Passport DL

2.9 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 10.20 Sec
  • Launch time: Icon 3.80 Sec
  • Application size: --- 3.48 MB
  • Last tested on : 17/05/2017
  • Build ID
    :   v1.5
  • Chhi Score
    :   2.9
  • Change Rate
    :   +3.57 %

What to fix?

App launch time went up by 1010% initlizate network calls after few seconds of loading the resources. View details

Build v1.3 did better in CPU . Spikes in CPU contributed to score drop by 5.26%

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

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

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

The app's Memory score has improved by 4% compared to build v1.3! Good job!

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

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

Utilization of CPU is close to the threshold.

Utilization of Memory is close to the threshold.

13 tests need immediate attention. View performance graph.

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

52.77 MB of App Dalvik utilized by activity com.krishna.india.NavDrawerActivity. View details

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

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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

Well done, Network consumption has come down by 18.08 % compared to build v1.3

The app's Network score has improved by 5.41% compared to build v1.3! Good job!

Screen coverage

Test Flows Lava Iris X8 Panasonic P55 LYF Karbonn Titanium Machfive Lenovo VIBE K4 Note Lenovo A6000 Samsung Duos Galaxy J7

Install app

  • Success

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Success

Scenario 1

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 2

  • Risk

  • Risk

  • Risk

competition benchmark

This app is ranked #450 in Communication

445
446
447
448
449
back-to-top