App Quality Dashboard

Talking James Squirrel

1.1 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Medium  Risk

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 48.43 Sec
  • Launch time: Icon 5.58 Sec
  • Application size: Icon 68.27 MB
  • Last tested on : 25/03/2017
  • Build ID
    :   v4.20.0
  • Chhi Score
    :   1.1
  • Change Rate
    :   -8.33 %

What to fix?

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

Fixing Network risks could drastically improve Chhi Score. There are 14 Network risks.

Your App CPU is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage

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

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.

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.kauf.talking.baum.TalkingJamesSquirrel PID: 28484 android.co... Users with phone manufactured by YU might experience a crash on their phone!. Fix now!

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.kauf.talking.baum.TalkingJamesSquirrel PID: 28484 android.co... Users with phone manufactured by Lava might experience a crash on their phone!. Fix now!

14 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.kauf.talking.baum.TalkingJamesSquirrel PID: 28484 android.co... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!

Utilization of CPU is close to the threshold.

20 tests need immediate attention. View performance graph.

3 Risk(s) are due to CPU Load in CPU exceeding the threshold.

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

Build v4.17.0 did better in Memory . Spikes in Memory contributed to score drop by 7.5%

The app took 5.58 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details

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

508 apps having similar CPU load have low Chhi Scores

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

53.86 MB of App Dalvik utilized by activity com.google.android.gms.ads.AdActivity. View details

4 Tests crashed out of 21 Tests. Check where the app crashed. View details

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

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

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

Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down

Caching: Use LruCache for data caching to optimize memory usage

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

App makes 11572.04 KB of network requests. Moving this to a background thread will improve load speed. View details

Network utilization on Zenfone 2 Laser exceeded 1024 KB, you might want to consider bringing it down

Total Network data consumed was 11572.04KB in Lenovo A6000 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

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

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

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

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.

competition benchmark

This app is ranked #2243 in Entertainment

2238
2239
2240
2241
2242
back-to-top