App Quality Dashboard

Ghost Talk

2.5 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 16.25 Sec
  • Launch time: Icon 2.37 Sec
  • Application size: Icon 9.11 MB
  • Last tested on : 04/05/2017
  • Build ID
    :   v3.3.1
  • Chhi Score
    :   2.5
  • Change Rate
    :   +92.31 %

What to fix?

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

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

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

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.

9 tests need immediate attention. View performance graph.

The app's CPU score has improved by 31.25% compared to build v3.2! Good job!

Utilization of CPU is close to the threshold.

The app's Memory score has improved by 22.22% compared to build v3.2! Good job!

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

57.02 MB of App Dalvik utilized by activity com.dbd.ghosttalk.ui.MainActivity. View details

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

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

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

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

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.

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

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

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

Well done, Network consumption has come down by 55.8 % compared to build v3.2

The app's Network score has improved by 15% compared to build v3.2! Good job!

competition benchmark

This app is ranked #564 in Music & Audio

559
560
561
562
563
back-to-top