App Quality Dashboard

IBM Watson Workspace

3.6 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 11.17 Sec
  • Launch time: --- 1.10 Sec
  • Application size: Icon 6.01 MB
  • Last tested on : 08/05/2017
  • Build ID
    :   v1.1.6
  • Chhi Score
    :   3.6
  • Change Rate
    :   -7.69 %

What to fix?

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

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

Utilization of CPU is close to the threshold.

Build v1.1.4 did better in CPU . Spikes in CPU contributed to score drop by 2.63%

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

1 tests need immediate attention. View performance graph.

Utilization of Memory is close to the threshold.

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

38.28 MB of App Dalvik utilized by activity com.lotus.android.common.ui.app.AboutAppActivity. View details

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

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

Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.

Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down

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

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

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

Follow simple UI hierarchy by reducing nested layouts to Relative layouts.

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

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

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

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

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

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

Screen coverage

competition benchmark

This app is ranked #590 in Business

585
586
587
588
589
back-to-top