App Quality Dashboard

NET

3.6 / 5

Chhi Score

This app is performing

Average

Memory

Good

/5

CPU

Medium Risk

/5

crash

Medium  Risk

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: 14.94 Sec
  • Launch time: 1.06 Sec
  • Application size : 5.25 MB
  • Last tested on : 19/06/2017
  • Build ID
    :   v4.5.2
  • Chhi Score
    :   3.6
  • Change Rate
    :   0%

Insights (22)

What to fix?

Must fix: App crashed because of 7532): FATAL EXCEPTION: main 7532): Process: br.com.net.netapp PID: 7532 7532): java.lang.NullP... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!
Must fix: App crashed because of 7532): FATAL EXCEPTION: main 7532): Process: br.com.net.netapp PID: 7532 7532): java.lang.NullP... Users with phone manufactured by Micromax might experience a crash on their phone!. Fix now!
Must fix: App crashed because of 7532): FATAL EXCEPTION: main 7532): Process: br.com.net.netapp PID: 7532 7532): java.lang.NullP... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!
Must fix: App crashed because of 7532): FATAL EXCEPTION: main 7532): Process: br.com.net.netapp PID: 7532 7532): java.lang.NullP... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!
The app has a high performance risk for the phone manufacturer(s) Micromax, Motorola, Panasonic, LYF. Check coverage report for more details.
1 tests need immediate attention. View performance graph.
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
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
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.
4 Tests crashed out of 18 Tests. Check where the app crashed. View details
There is high probability of identifying risks running the apps with conditions
39.41 MB of App Dalvik utilized by activity br.com.net.netapp.activities.SelecaoCidadeActivity_. View details
Caching: Use LruCache for data caching to optimize memory usage
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
Testability: Providing login / sign-up details could very well improve depth of bot clicks
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
The app has crashed on few device(s)! View details
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #583 in Entertainment

578
579
580
581
582
back-to-top