App Quality Dashboard

Wickr SCIF

3.3 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

network

#

 

Category

Rank

  • Install time: Icon 33.75 Sec
  • Launch time: Icon 0.66 Sec
  • Application size: Icon 34.90 MB
  • Last tested on : 20/03/2017
  • Build ID
    :   v1.1.6
  • Chhi Score
    :   3.3
  • Change Rate
    :   -5.71 %

What to fix?

2 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 2 High Risk(s).

Build v1.0.11 did better in Memory . Spikes in Memory contributed to score drop by 9.09%

2 tests need immediate attention. View performance graph.

1 Risk(s) are due to App Total in Memory exceeding the threshold.

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

Build v1.0.11 did better in CPU . Spikes in CPU contributed to score drop by 2.44%

Your average App Dalvik usage surged by 9.57%, Your memory score is 3.0

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

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

55.01 MB of App Dalvik utilized by activity com.wickr.enterprise.login.RoutingActivity. View details

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

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.

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

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

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

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

Fix & Optimize launch time using Flatbuffers for storage and rendering 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

Screen coverage

competition benchmark

This app is ranked #742 in Business

737
738
739
740
741
back-to-top