App Quality Dashboard

Twitter

0.1 / 5

Chhi Score

This app is performing

Poor

Memory

CPU

High  Risk

/5

network

#

 

Category

Rank

  • Install time: Icon 8.00 Sec
  • Launch time: --- 0.00 Sec
  • Application size: Icon 34.30 MB
  • Last tested on : 10/10/2017
  • Build ID
    :   v7.16.0
  • Chhi Score
    :   0.1
  • Change Rate
    :   -97.44 %

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

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

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!

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 v6.39.0, Memory score was 4.1

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

Consider re-merging the code from build v6.39.0, CPU score was 2.4

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

Consider re-merging the code from build v6.39.0, Network score was 4.9

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

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

435 apps having similar CPU load have low Chhi Scores

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

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

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

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

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

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

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

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

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.

Caching: Use LruCache for data caching to optimize memory usage

competition benchmark

This app is ranked #1423 in News & Magazines

1418
1419
1420
1421
1422
back-to-top