App Quality Dashboard

Travel to India

1.3 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

High  Risk

/5

Good

/5

#

 

Category

Rank

  • Install time: 9.83 Sec
  • Launch time: 1.69 Sec
  • Application size : 9.54 MB
  • Last tested on : 28/05/2017
  • Build ID
    :   v94.55.7
  • Chhi Score
    :   1.3
  • Change Rate
    :   0%

What to fix?

Must fix: App crashed because of 5406): FATAL EXCEPTION: main 5406): Process: com.lessiastar.traveltoindia PID: 5406 5406): java... Users with phone manufactured by Samsung might experience a crash on their phone!. Fix now!

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

Must fix: App crashed because of 5406): FATAL EXCEPTION: main 5406): Process: com.lessiastar.traveltoindia PID: 5406 5406): java... Users with phone manufactured by HTC might experience a crash on their phone!. Fix now!

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

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

4 tests need immediate attention. View performance graph.

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

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

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

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

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.

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

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

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

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

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

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

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

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

98.07 MB of App Dalvik utilized by activity com.lessiastar.traveltoindia.PhotoInfoMasterFragmentActivity. View details

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

Screen coverage

competition benchmark

This app is ranked #1089 in Travel & Local

1084
1085
1086
1087
1088
back-to-top