App Quality Dashboard

Fake Location

0.8 / 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.50 Sec
  • Launch time: Icon 2.53 Sec
  • Application size: Icon 3.86 MB
  • Last tested on : 26/04/2017
  • Build ID
    :   v3.610
  • Chhi Score
    :   0.8
  • Change Rate
    :   -42.86 %

What to fix?

Potential risk in CPU: Utilization has gone up by 23.08% compared to build v3.609

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

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

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

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

Potential risk in Network: Utilization has gone up by70% compared to build v3.609

Build v3.609 did better in Memory . Spikes in Memory contributed to score drop by 5%

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

Consider re-merging the code from build v3.609, Network score was 4.0

24 tests need immediate attention. View performance graph.

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

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

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

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!

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

Total Network data consumed was 2489.09KB in Motorola Moto E (2nd gen) , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

347 apps having similar CPU load have low Chhi Scores

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

Network utilization on Karbonn Titanium Machfive 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

Your average App Dalvik usage surged by 4.07%, Your memory score is 1.9

53.55 MB of App Dalvik utilized by activity com.fakegps.mock.activities.MainActivity. View details

Screen Coverage

competition benchmark

This app is ranked #1867 in Tools

1862
1863
1864
1865
1866
back-to-top