App Quality Dashboard


3.4 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 38.90 Sec
  • Launch time: Icon 1.30 Sec
  • Application size: Icon 33.46 MB
  • Last tested on : 23/04/2017
  • Build ID
    :   v4.3.5
  • Chhi Score
    :   3.4
  • Change Rate
    :   -17.07 %

What to fix?

Build v4.2.9 did better in CPU . Spikes in CPU contributed to score drop by 24.39%

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

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

Build v4.2.9 did better in Memory . Spikes in Memory contributed to score drop by 19.51%

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 v4.2.9 did better in Network . Spikes in Network contributed to score drop by 2%

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

Consider re-merging the code from build v4.2.9, Memory score was 4.1

Consider re-merging the code from build v4.2.9, CPU score was 4.1

1 tests need immediate attention. View performance graph.

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

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

Your average App Dalvik usage surged by 20.87%, Your memory score is 3.3

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

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

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

31.84 MB of App Dalvik utilized by activity com.smule.singandroid.StartupActivity_. View details

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

Screen coverage

Test Flows YU Yuphoria Lava Iris X8 Panasonic P55 LYF Zenfone 2 Laser Micromax Canvas A1 Lenovo VIBE K4 Note Lenovo A6000 Motorola Moto E (2nd gen)

Install app

  • Success

  • Success

  • Success

  • Success

  • Risk

  • Success

  • Success

  • Success

  • Success

Scenario 1

  • Success

competition benchmark

This app is ranked #280 in Music & Audio