App Quality Dashboard

inshorts

1.1 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 25.67 Sec
  • Launch time: Icon 2.86 Sec
  • Application size: Icon 13.86 MB
  • Last tested on : 09/05/2017
  • Build ID
    :   v4.0.7
  • Chhi Score
    :   1.1
  • Change Rate
    :   -71.79 %

What to fix?

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

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

Potential risk in CPU: Utilization has gone up by 50% compared to build v4.0.3

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

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

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 v4.0.3 did better in Network . Spikes in Network contributed to score drop by 6.38%

Consider re-merging the code from build v4.0.3, CPU score was 2.0

Build v4.0.3 did better in Memory . Spikes in Memory contributed to score drop by 7.69%

Utilization of Memory is close to the threshold.

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

Utilization of CPU is close to the threshold.

27 tests need immediate attention. View performance graph.

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

51.02 MB of App Dalvik utilized by activity com.nis.app.ui.activities.HomeActivity. View details

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

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

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

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

435 apps having similar CPU load have low Chhi Scores

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

Your average App Dalvik usage surged by 11.64%, Your memory score is 3.6

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.

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

Screen coverage

Test Flows YU Yuphoria Lava Iris X8 Panasonic P55 LYF Karbonn Titanium Machfive Zenfone 2 Laser Lenovo VIBE K4 Note Lenovo A6000 Motorola Moto E (2nd gen)

Install app

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 1

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 2

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

competition benchmark

This app is ranked #1271 in News & Magazines

1266
1267
1268
1269
1270
back-to-top