App Quality Dashboard

FlightAware

1.0 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: 17.50 Sec
  • Launch time: 1.77 Sec
  • Application size : 8.43 MB
  • Last tested on : 03/03/2017
  • Build ID
    :   v5.2.138
  • Chhi Score
    :   1.0
  • Change Rate
    :   0%

What to fix?

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

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

Your App CPU is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage

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

14 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

Utilization of Memory is close to the threshold.

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

179 apps having similar CPU load have low Chhi Scores

56.49 MB of App Dalvik utilized by activity com.flightaware.android.liveFlightTracker.activities.MainActivity. View details

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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!

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.

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

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.

Screen coverage

Test Flows YU Yuphoria Karbonn Titanium Machfive Zenfone 2 Laser Micromax Canvas A1 Lenovo VIBE K4 Note Lenovo A6000

Install app

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 1

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 2

  • Risk

  • Risk

competition benchmark

This app is ranked #1112 in Travel & Local

1107
1108
1109
1110
1111
back-to-top