App Quality Dashboard

Parallel Space

1.2 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 12.27 Sec
  • Launch time: Icon 2.31 Sec
  • Application size: Icon 5.27 MB
  • Last tested on : 07/03/2017
  • Build ID
    :   v3.5.7480
  • Chhi Score
    :   1.2
  • Change Rate
    :   +9.09 %

What to fix?

Potential risk in Network: Utilization has gone up by40.91% compared to build v3.1.7298

Fixing Network risks could drastically improve Chhi Score. There are 3 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

11 Risk(s) are due to Threads in CPU 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.

Fixing CPU risks could drastically improve Chhi Score. There are 11 CPU risks.

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

App launch time went up by 32% initlizate network calls after few seconds of loading the resources. View details

11 tests need immediate attention. View performance graph.

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

Utilization of Network is close to the threshold.

Utilization of Memory is close to the threshold.

Consider re-merging the code from build v3.1.7298, Network score was 2.2

Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down

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

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

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

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 Zenfone 2 Laser 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

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

65.08 MB of App Dalvik utilized by activity com.lbe.parallel.ui.lockscreen.SmartLockGuideActivity. View details

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

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

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

Total Network data consumed was 1773.70KB in Zenfone 2 Laser , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

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

6 apps having similar CPU load have low Chhi Scores

Caching: Use LruCache for data caching to optimize memory usage

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

The app's Memory score has improved by 8.57% compared to build v3.1.7298! Good job!

Screen coverage

Test Flows YU Yuphoria Panasonic P55 LYF Zenfone 2 Laser Lenovo A6000

Install app

  • Risk

  • Risk

  • Risk

Scenario 1

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 2

  • Risk

  • Risk

  • Risk

competition benchmark

This app is ranked #3 in Personalisation

1
2
back-to-top