App Quality Dashboard

Scale Ruler

3.1 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




Medium Risk






  • Install time: Icon 8.71 Sec
  • Launch time: Icon 0.80 Sec
  • Application size: --- 3.90 MB
  • Last tested on : 12/04/2017
  • Build ID
    :   v1.2
  • Chhi Score
    :   3.1
  • Change Rate
    :   +3.33 %

What to fix?

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

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

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

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

Build v1.1 did better in CPU . Spikes in CPU contributed to score drop by 9.38%

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.

Utilization of CPU is close to the threshold.

10 tests need immediate attention. View performance graph.

The app's Memory score has improved by 3.57% compared to build v1.1! Good job!

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

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

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

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

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

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

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

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.

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

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

54.74 MB of App Dalvik utilized by activity scaleruler.accurate.easy.activities.RulerActivity. View details

App makes 3288.12 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.

Well done, Network consumption has come down by 42.38 % compared to build v1.1

The app's Network score has improved by 38.46% compared to build v1.1! Good job!

Screen Coverage

competition benchmark

This app is ranked #1241 in Tools