App Quality Dashboard

iReff

3.3 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 18.60 Sec
  • Launch time: Icon 1.05 Sec
  • Application size: Icon 6.70 MB
  • Last tested on : 18/05/2017
  • Build ID
    :   v2.3.14
  • Chhi Score
    :   3.3
  • Change Rate
    :   +6.45 %

What to fix?

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.

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

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

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

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

Build v2.3.8 did better in CPU . Spikes in CPU contributed to score drop by 8%

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

2 tests need immediate attention. View performance graph.

The app's Memory score has improved by 10.34% compared to build v2.3.8! Good job!

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

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

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

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

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

Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.

60.89 MB of App Dalvik utilized by activity o.ﯿ. View details

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

The app's Network score has improved by 2.04% compared to build v2.3.8! Good job!

Well done, Network consumption has come down by 37.72 % compared to build v2.3.8

Screen coverage

Test Flows Lenovo VIBE K4 Note Lenovo A6000

Install app

  • Risk

  • Success

Scenario 1

  • Risk

  • Success

Scenario 2

  • Success

competition benchmark

This app is ranked #374 in Shopping

369
370
371
372
373
back-to-top