App Quality Dashboard

HR Exec Mag

2.3 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 17.90 Sec
  • Launch time: Icon 2.15 Sec
  • Application size: Icon 9.56 MB
  • Last tested on : 11/05/2017
  • Build ID
    :   v32.0
  • Chhi Score
    :   2.3
  • Change Rate
    :   0%

What to fix?

App launch time went up by 37.68% initlizate network calls after few seconds of loading the resources. View details

Build v27.0 did better in Network . Spikes in Network contributed to score drop by 13.04%

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.

Build v27.0 did better in CPU . Spikes in CPU contributed to score drop by 15.63%

Build v27.0 did better in Memory . Spikes in Memory contributed to score drop by 5%

Utilization of CPU is close to the threshold.

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

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

App size increased by 41.42% See how to optimize.

Consider re-merging the code from build v27.0, CPU score was 3.2

8 tests need immediate attention. View performance graph.

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

Your average App Dalvik usage surged by 14.61%, Your memory score is 1.9

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

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

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

79.66 MB of App Dalvik utilized by activity com.texterity.android.HumanResourceExecutive.activities.TexterityTabActivity. View details

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

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

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

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

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

Screen Coverage

competition benchmark

This app is ranked #1049 in Business

1044
1045
1046
1047
1048
back-to-top