App Quality Dashboard

True Key

2.7 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 33.00 Sec
  • Launch time: Icon 3.21 Sec
  • Application size: Icon 31.31 MB
  • Last tested on : 23/03/2017
  • Build ID
    :   v3.1.11.2
  • Chhi Score
    :   2.7
  • Change Rate
    :   +42.11 %

Insights (27)

What to fix?

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.
14 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 14 High Risk(s).
App launch time went up by 91.74% initlizate network calls after few seconds of loading the resources. View details
Build v3.1.11.1 did better in CPU . Spikes in CPU contributed to score drop by 8.82%
Zenfone 2 Laser health improved from High risk to Medium risk eliminating CRASH
The app's Memory score has improved by 18.18% compared to build v3.1.11.1! Good job!
The app has a high performance risk for the phone manufacturer(s) Lava, Asus, Lenovo, YU, Karbonn. Check coverage report for more details.
15 tests need immediate attention. View performance graph.
4 Risk(s) are due to App Total in Memory exceeding the threshold.
The app's memory score is 2.6 due to high memory utilization. Needs to be fixed as priority.
1 Risk(s) are due to CPU Load in CPU exceeding the threshold.
Utilization of CPU is close to the threshold.
Utilization of Memory is close to the threshold.
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
94.91 MB of App Dalvik utilized by activity com.truekey.intel.ui.authentication.SignUpActivity. View details
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 Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
Printing logs on callbacks would make debugging easy for tests run in our platform
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
Caching: Use LruCache for data caching to optimize memory usage
There is high probability of identifying risks running the apps with conditions
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Unlock more fixes

Screen coverage

competition benchmark

This app is ranked #840 in Productivity

835
836
837
838
839
back-to-top