App Quality Dashboard

Startup

2.1 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Medium  Risk

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 16.65 Sec
  • Launch time: Icon 3.11 Sec
  • Application size: Icon 5.92 MB
  • Last tested on : 16/05/2017
  • Build ID
    :   v2.0.7
  • Chhi Score
    :   2.1
  • Change Rate
    :   -38.24 %

What to fix?

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.eniseistudio.startup PID: 14248 java.lang.RuntimeException: ... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.eniseistudio.startup PID: 14248 java.lang.RuntimeException: ... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!

Build v1.0.1 did better in Memory . Spikes in Memory contributed to score drop by 27.27%

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 v1.0.1 did better in CPU . Spikes in CPU contributed to score drop by 18.18%

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

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

Consider re-merging the code from build v1.0.1, Memory score was 3.3

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

Motorola Moto E (2nd gen), Lenovo A6000, Zenfone 2 Laser has moved from Good to Medium risk due to RISK . View details

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

16 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

Consider re-merging the code from build v1.0.1, CPU score was 3.3

86.19 MB of App Dalvik utilized by activity activity.ParentActivity. View details

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

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

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.

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

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

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

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

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

Your average App Dalvik usage surged by 36.66%, Your memory score is 2.4

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

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

The app's Network score has improved by 36.11% compared to build v1.0.1! Good job!

Well done, Network consumption has come down by 90.39 % compared to build v1.0.1

Screen coverage

competition benchmark

This app is ranked #904 in News & Magazines

899
900
901
902
903
back-to-top