App Quality Dashboard

My Jarvis

1.2 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

High  Risk

/5

High Risk

/5

#

 

Category

Rank

  • Install time: 31.29 Sec
  • Launch time: 7.34 Sec
  • Application size : 16.38 MB
  • Last tested on : 16/05/2017
  • Build ID
    :   v2.0.1
  • Chhi Score
    :   1.2
  • Change Rate
    :   0%

What to fix?

3 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.

Must fix: App crashed because of FATAL EXCEPTION: Thread-32221 Process: com.itsmylab.jarvis PID: 17178 java.lang.IllegalStateExc... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!

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

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

Must fix: App crashed because of FATAL EXCEPTION: Thread-32221 Process: com.itsmylab.jarvis PID: 17178 java.lang.IllegalStateExc... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: Thread-32221 Process: com.itsmylab.jarvis PID: 17178 java.lang.IllegalStateExc... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!

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

Fixing Network risks could drastically improve Chhi Score. There are 4 Network risks.

7 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

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

The app took 7.34 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details

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

Network utilization on Lenovo VIBE K4 Note 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

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

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

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

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

82.61 MB of App Dalvik utilized by activity com.itsmylab.jarvis.ui.MainActivity. View details

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.

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

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

3 Tests crashed out of 7 Tests. Check where the app crashed. View details

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

Caching: Use LruCache for data caching to optimize memory usage

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

The app has crashed on few device(s)! View details

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

Screen Coverage

competition benchmark

This app is ranked #1032 in Productivity

1027
1028
1029
1030
1031
back-to-top