App Quality Dashboard

Tagged

3.2 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 53.90 Sec
  • Launch time: Icon 2.41 Sec
  • Application size: Icon 41.58 MB
  • Last tested on : 08/05/2017
  • Build ID
    :   v7.3.4
  • Chhi Score
    :   3.2
  • Change Rate
    :   +3.23 %

What to fix?

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.

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

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

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

Build v7.0 did better in CPU . Spikes in CPU contributed to score drop by 11.54%

15 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

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

The app's Memory score has improved by 3.45% compared to build v7.0! Good job!

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

43.56 MB of App Dalvik utilized by activity com.tagged.activity.AuthenticationActivity. View details

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

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

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

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

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

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

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

Well done, Network consumption has come down by 76.44 % compared to build v7.0

The app's Network score has improved by 11.63% compared to build v7.0! Good job!

Screen Coverage

competition benchmark

This app is ranked #426 in Social

421
422
423
424
425
back-to-top