App Quality Dashboard

Sugama Tourist

2.2 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 9.00 Sec
  • Launch time: Icon 0.87 Sec
  • Application size: Icon 7.34 MB
  • Last tested on : 02/05/2017
  • Build ID
    :   v1.3
  • Chhi Score
    :   2.2
  • Change Rate
    :   -37.14 %

What to fix?

Build v1.2 did better in CPU . Spikes in CPU contributed to score drop by 18.75%

Build v1.2 did better in Memory . Spikes in Memory contributed to score drop by 42.86%

7 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 7 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.

7 tests need immediate attention. View performance graph.

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

App size increased by 85.82% See how to optimize.

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.

Build v1.2 did better in Network . Spikes in Network contributed to score drop by 2.04%

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

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

Utilization of CPU is close to the threshold.

Consider re-merging the code from build v1.2, Memory score was 3.5

Consider re-merging the code from build v1.2, CPU score was 3.2

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

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

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

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

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

31.10 MB of App Dalvik utilized by activity com.bitla.mba.sugamatourist.MainActivity. View details

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

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

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

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

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

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!

Screen Coverage

competition benchmark

This app is ranked #901 in Travel & Local

896
897
898
899
900
back-to-top