App Quality Dashboard

izi.TRAVEL

3.9 / 5

Chhi Score

This app is performing

Average

Memory

Good

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 13.33 Sec
  • Launch time: Icon 0.78 Sec
  • Application size: Icon 8.74 MB
  • Last tested on : 09/05/2017
  • Build ID
    :   v4.2.1.388
  • Chhi Score
    :   3.9
  • Change Rate
    :   0%

Insights (24)

What to fix?

App launch time went up by INF% initlizate network calls after few seconds of loading the resources. View details
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.
Utilization of CPU is close to the threshold.
The app has a high performance risk for the phone manufacturer(s) InFocus. Check coverage report for more details.
The app's CPU score has improved by 26.09% compared to build v4.2.0.387! Good job!
1 tests need immediate attention. View performance graph.
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
56.29 MB of App Dalvik utilized by activity travel.opas.client.ui.main.MainActivity. View details
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.
There is high probability of identifying risks running the apps with conditions
Caching: Use LruCache for data caching to optimize memory usage
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
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!
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
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.
Printing logs on callbacks would make debugging easy for tests run in our platform
The app's Memory score has improved by 4.76% compared to build v4.2.0.387! Good job!
The app's Network score has improved by 6.98% compared to build v4.2.0.387! Good job!
Well done, Network consumption has come down by 38.27 % compared to build v4.2.0.387
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #255 in Travel & Local

250
251
252
253
254
back-to-top