App Quality Dashboard

InstaSave for Instagram

2.8 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 9.50 Sec
  • Launch time: Icon 0.77 Sec
  • Application size: Icon 3.15 MB
  • Last tested on : 16/05/2017
  • Build ID
    :   v3.0.SJL
  • Chhi Score
    :   2.8
  • Change Rate
    :   -24.32 %

What to fix?

Build v2.9.HDXM did better in Memory . Spikes in Memory contributed to score drop by 22.86%

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

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

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

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.

1 Risk(s) are due to App Total in Memory exceeding the threshold.

2 tests need immediate attention. View performance graph.

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

Consider re-merging the code from build v2.9.HDXM, Memory score was 3.5

The app's CPU score has improved by 3.45% compared to build v2.9.HDXM! Good job!

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.

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

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

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

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

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

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

34.33 MB of App Dalvik utilized by activity com.digit64.instasaver.activity.MainActivity. View details

Your average App Dalvik usage surged by 43.44%, Your memory score is 2.7

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

Well done, Network consumption has come down by 46.74 % compared to build v2.9.HDXM

The app's Network score has improved by 20.59% compared to build v2.9.HDXM! Good job!

Screen coverage

competition benchmark

This app is ranked #1372 in Tools

1367
1368
1369
1370
1371
back-to-top