App Quality Dashboard

Calculator

1.1 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

High  Risk

/5

High Risk

/5

#

 

Category

Rank

  • Install time: 13.33 Sec
  • Launch time: 3.52 Sec
  • Application size : 3.74 MB
  • Last tested on : 16/05/2017
  • Build ID
    :   v1.1
  • Chhi Score
    :   1.1
  • Change Rate
    :   0%

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.

Must fix: App crashed because of FATAL EXCEPTION: main Process: intelisenze.citizen.casio.calculator PID: 17559 java.lang.Illega... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!

9 Risk(s) are due to Threads in CPU exceeding the threshold.

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

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

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: intelisenze.citizen.casio.calculator PID: 17559 java.lang.Illega... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!

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

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

Utilization of CPU is close to the threshold.

9 tests need immediate attention. View performance graph.

39.61 MB of App Dalvik utilized by activity intelisenze.citizen.casio.calculator.MainActivity. View details

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

Network utilization on Lenovo A6000 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

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

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

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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

4 Tests crashed out of 9 Tests. Check where the app crashed. View details

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

347 apps having similar CPU load have low Chhi Scores

Total Network data consumed was 2985.66KB 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

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

competition benchmark

This app is ranked #1811 in Tools

1806
1807
1808
1809
1810
back-to-top