App Quality Dashboard

Hornet

3.9 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 24.33 Sec
  • Launch time: Icon 0.96 Sec
  • Application size: Icon 13.97 MB
  • Last tested on : 08/05/2017
  • Build ID
    :   v3.6.1-2
  • Chhi Score
    :   3.9
  • Change Rate
    :   0%

What to fix?

8 Risk(s) are due to Threads in CPU exceeding the threshold.

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

Build v3.4.1 did better in CPU . Spikes in CPU contributed to score drop by 4.76%

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) YU, Lava, Micromax. Check coverage report for more details.

8 tests need immediate attention. View performance graph.

Build v3.4.1 did better in Memory . Spikes in Memory contributed to score drop by 2.44%

App size increased by 27.7% See how to optimize.

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

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

26.69 MB of App Dalvik utilized by activity com.hornet.android.activity.SplashActivity_. View details

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

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

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

Your average App Dalvik usage surged by 0.7%, Your memory score is 4.0

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

Well done, Network consumption has come down by 21.02 % compared to build v3.4.1

Screen coverage

competition benchmark

This app is ranked #212 in Social

207
208
209
210
211
back-to-top