App Quality Dashboard

SingaporeSocial

2.4 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 29.56 Sec
  • Launch time: Icon 2.39 Sec
  • Application size: Icon 23.21 MB
  • Last tested on : 09/05/2017
  • Build ID
    :   v1.5
  • Chhi Score
    :   2.4
  • Change Rate
    :   -14.29 %

What to fix?

Build v1.4 did better in Memory . Spikes in Memory contributed to score drop by 15.38%

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.

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

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

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

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

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

23 tests need immediate attention. View performance graph.

The app's CPU score has improved by 19.05% compared to build v1.4! Good job!

Build v1.4 did better in Network . Spikes in Network contributed to score drop by 12%

Make sure your App's PSS isn't too high. Freeing objects that aren't needed would reduce chances of getting unexpectedly killed by Android system.

Utilization of CPU is close to the threshold.

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

53.24 MB of App Dalvik utilized by activity com.mingle.twine.activities.SignUpActivity. View details

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

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

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

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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

Screen coverage

competition benchmark

This app is ranked #2300 in Lifestyle

2295
2296
2297
2298
2299
back-to-top