Instagram

0.1 / 5

Chhi Score

This app is performing

Poor

Memory

CPU

High  Risk

/5

network

#

 

Category

Rank

  • Install time: Icon 11.00 Sec
  • Launch time: Icon 0.00 Sec
  • Application size: Icon 31.29 MB
  • Last tested on : 10/10/2017
  • Build ID
    :   v17.0.0.15.91
  • Chhi Score
    :   0.1
  • Change Rate
    :   -97.56 %

Testing depth

Covered

37%

Uncovered

63%

Depth Details

What to fix?

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

Must fix: App crashed because of 1647): java.lang.RuntimeException 1647): at android.provider.Settings$NameValueCache.putStrin... Users with phone manufactured by InFocus might experience a crash on their phone!. Fix now!

Your App Memory 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

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.

Consider re-merging the code from build v10.19.1, Network score was 5.0

App size increased by 17.02% See how to optimize.

Consider re-merging the code from build v10.19.1, Memory score was 4.1

InFocus, InFocus, InFocus has moved from Good to Medium risk due to FAIL . View details

Consider re-merging the code from build v10.19.1, CPU score was 4.1

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

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

213 apps having similar CPU load have low Chhi Scores

The app has crashed on few device(s)! View details

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

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

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

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

5 Tests crashed out of 5 Tests. Check where the app crashed. View details

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

competition benchmark

This app is ranked #777 in Social

772
773
774
775
776
back-to-top