App Quality Dashboard

RATP

3.0 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 30.83 Sec
  • Launch time: Icon 6.88 Sec
  • Application size: Icon 19.97 MB
  • Last tested on : 06/03/2017
  • Build ID
    :   v4.0.6.4
  • Chhi Score
    :   3.0
  • Change Rate
    :   +66.67 %

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.

10 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 10 High Risk(s).

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

Build 4.0.5.7 did better in Memory . Spikes in Memory contributed to score drop by 6.9%

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

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

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

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

The app's CPU score has improved by 11.76% compared to build 4.0.5.7! Good job!

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

12 tests need immediate attention. View performance graph.

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

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

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

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

56.84 MB of App Dalvik utilized by activity com.fabernovel.ratp.activities.ResearchPointRiActivity. View details

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

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

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

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

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.

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

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

The app's Network score has improved by 4.76% compared to build 4.0.5.7! Good job!

Well done, Network consumption has come down by 21.64 % compared to build 4.0.5.7

Screen coverage

Test Flows YU Yuphoria Karbonn Titanium Machfive Zenfone 2 Laser Micromax Canvas A1 AQ4502 Lenovo VIBE K4 Note Lenovo A6000

Install app

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 1

  • Risk

Scenario 2

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

competition benchmark

This app is ranked #312 in Maps & Navigation

307
308
309
310
311
back-to-top