App Quality Dashboard

Tata Motors Connect

1.5 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Good

/5

High  Risk

/5

Good

/5

#

 

Category

Rank

  • Install time: 13.13 Sec
  • Launch time: 2.11 Sec
  • Application size : 6.87 MB
  • Last tested on : 09/03/2017
  • Build ID
    :   v3.3.1
  • Chhi Score
    :   1.5
  • Change Rate
    :   0%

What to fix?

Oops!, The app crashed on Panasonic P55, Samsung Duos Galaxy J7 & more devices. View details

Must fix: App crashed because of 8274): FATAL EXCEPTION: main 8274): Process: com.tatamotors.tatatouch PID: 8274 8274): java.lan... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!

Panasonic P55 crashed attached to window manager 9806): at android.view.WindowManagerGlobal.findViewLocked(WindowManagerGlobal.java:448) View details

Must fix: App crashed because of 8274): FATAL EXCEPTION: main 8274): Process: com.tatamotors.tatatouch PID: 8274 8274): java.lan... Users with phone manufactured by Samsung might experience a crash on their phone!. Fix now!

Samsung Duos Galaxy J7 crashed attached to window manager 8538): at android.view.WindowManagerGlobal.findViewLocked(WindowManagerGlobal.java:454) View details

Must fix: App crashed because of 8274): FATAL EXCEPTION: main 8274): Process: com.tatamotors.tatatouch PID: 8274 8274): java.lan... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!

Utilization of Memory is close to the threshold.

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

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

56.37 MB of App Dalvik utilized by activity com.tatamotors.tatatouch.MainActivity. View details

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

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

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

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

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.

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

Screen coverage

competition benchmark

This app is ranked #1170 in Business

1165
1166
1167
1168
1169
back-to-top