App Quality Dashboard

TalkZapp Free

3.1 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Medium  Risk

/5

Good

/5

#

 

Category

Rank

  • Install time: 2.94 Sec
  • Launch time: 4.00 Sec
  • Application size : 0.39 MB
  • Last tested on : 21/04/2017
  • Build ID
    :   v1.01
  • Chhi Score
    :   3.1
  • Change Rate
    :   0%

What to fix?

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.abast.talkzappfree PID: 10862 java.lang.RuntimeException: ... Users with phone manufactured by Samsung might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.abast.talkzappfree PID: 10862 java.lang.RuntimeException: ... Users with phone manufactured by Lava might experience a crash on their phone!. Fix now!

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.

2 tests need immediate attention. View performance graph.

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

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

Utilization of Memory is close to the threshold.

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

28.69 MB of App Dalvik utilized by activity com.abast.talkzapp.MainActivity. View details

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

The app has crashed on few device(s)! View details

Screen coverage

competition benchmark

This app is ranked #432 in Communication

427
428
429
430
431
back-to-top