App Quality Dashboard

CE Magazine

1.9 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

High Risk

/5

Competition

#

 

Category

Rank

  • Install time: Icon 13.40 Sec
  • Launch time: Icon 0.77 Sec
  • Application size: Icon 9.30 MB
  • Last tested on : 07/05/2017
  • Build ID
    :   v32.0
  • Chhi Score
    :   1.9
  • Change Rate
    :   +26.67 %

Insights (28)

What to fix?

Fixing Network risks could drastically improve Chhi Score. There are 3 Network 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.
3 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.
Build v27.0 did better in CPU . Spikes in CPU contributed to score drop by 3.57%
Potential risk in Network: Utilization has gone up by20% compared to build v27.0
Utilization of CPU is close to the threshold.
The app has a high performance risk for the phone manufacturer(s) HTC, Motorola, InFocus. Check coverage report for more details.
The app's Memory score has improved by 31.82% compared to build v27.0! Good job!
App size increased by 40.06% See how to optimize.
4 tests need immediate attention. View performance graph.
Printing logs on callbacks would make debugging easy for tests run in our platform
Caching: Use LruCache for data caching to optimize memory usage
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
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
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Network utilization on InFocus exceeded 1024 KB, you might want to consider bringing it down
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
Total Network data consumed was 1179.52KB in InFocus , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
90.40 MB of App Dalvik utilized by activity com.texterity.android.CivilEngineering.activities.TexterityTabActivity. View details
App makes 1179.52 KB of network requests. Moving this to a background thread will improve load speed. View details
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
Network utilization on HTC Desire 626 Dual SIM exceeded 1024 KB, you might want to consider bringing it down
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #966 in News & Magazines

961
962
963
964
965
back-to-top