App Quality Dashboard

Trafi

1.7 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 19.25 Sec
  • Launch time: Icon 2.75 Sec
  • Application size: Icon 14.58 MB
  • Last tested on : 05/04/2017
  • Build ID
    :   v4.6.0
  • Chhi Score
    :   1.7
  • Change Rate
    :   -58.54 %

What to fix?

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

Build v4.5.0 did better in Memory . Spikes in Memory contributed to score drop by 34.15%

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.

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

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

Potential risk in CPU: Utilization has gone up by 63.41% compared to build v4.5.0

Build v4.5.0 did better in Network . Spikes in Network contributed to score drop by 31.25%

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

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

Utilization of CPU is close to the threshold.

Consider re-merging the code from build v4.5.0, Network score was 4.8

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

12 tests need immediate attention. View performance graph.

Consider re-merging the code from build v4.5.0, CPU score was 4.1

Consider re-merging the code from build v4.5.0, Memory score was 4.1

The app's memory score is 2.7 due to high memory utilization. Needs to be fixed as priority.

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

Network utilization on YU Yuphoria 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

41.67 MB of App Dalvik utilized by activity com.trafi.android.ui.activities.MainActivity. View details

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

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

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

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

Your average App Dalvik usage surged by 64.07%, Your memory score is 2.7

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

Network utilization on Lava Iris X8 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!

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

Caching: Use LruCache for data caching to optimize memory usage

App makes 1215.78 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

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

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

120 apps having similar CPU load have low Chhi Scores

Screen Coverage

competition benchmark

This app is ranked #418 in Maps & Navigation

413
414
415
416
417
back-to-top