App Quality Dashboard

Ameba

2.4 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

High Risk

/5

crash

Good 

/5

network

Medium Risk

/5

Competition

#

 

Category

Rank

  • Install time: Icon 26.38 Sec
  • Launch time: Icon 0.52 Sec
  • Application size: Icon 13.76 MB
  • Last tested on : 04/05/2017
  • Build ID
    :   v10.7.3
  • Chhi Score
    :   2.4
  • Change Rate
    :   0%

Insights (32)

What to fix?

Fixing CPU risks could drastically improve Chhi Score. There are 15 CPU risks.
Fixing Network risks could drastically improve Chhi Score. There are 5 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
5 Risk(s) are due to Data Sent/Received in Network 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.
15 Risk(s) are due to Threads in CPU exceeding the threshold.
Utilization of CPU is close to the threshold.
The app has a high performance risk for the phone manufacturer(s) Lenovo, Micromax, LYF, Samsung, Panasonic, Motorola. Check coverage report for more details.
The app's CPU score has improved by 23.08%
15 tests need immediate attention. View performance graph.
3 Risk(s) are due to CPU Load in CPU exceeding the threshold.
The app's Network score has improved by 94.12% compared to build v10.7.1! Good job!
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
40.03 MB of App Dalvik utilized by activity jp.ameba.activity.OnboardingActivity. View details
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Caching: Use LruCache for data caching to optimize memory usage
213 apps having similar CPU load have low Chhi Scores
Network utilization on Panasonic P55 exceeded 1024 KB, you might want to consider bringing it down
Printing logs on callbacks would make debugging easy for tests run in our platform
There is high probability of identifying risks running the apps with conditions
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
App makes 1086.88 KB of network requests. Moving this to a background thread will improve load speed. View details
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Total Network data consumed was 1086.88KB in Motorola Moto E (2nd gen) , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details
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
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Well done, Network consumption has come down by 48.14 % compared to build v10.7.1
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #575 in Social

570
571
572
573
574
back-to-top