App Quality Dashboard

CT Sessions

2.2 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Medium  Risk

/5

High Risk

/5

#

 

Category

Rank

  • Install time: 16.86 Sec
  • Launch time: 0.82 Sec
  • Application size : 20.04 MB
  • Last tested on : 20/03/2017
  • Build ID
    :   v2.2
  • Chhi Score
    :   2.2
  • Change Rate
    :   0%

What to fix?

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

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

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.

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.siemens.ctsessions PID: 29495 java.lang.NullPointerException... Users with phone manufactured by Asus might experience a crash on their phone!. Fix now!

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

Utilization of CPU is close to the threshold.

7 tests need immediate attention. View performance graph.

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

Network utilization on Samsung Duos Galaxy J7 exceeded 1024 KB, you might want to consider bringing it down

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

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

Network utilization on Karbonn Titanium Machfive exceeded 1024 KB, you might want to consider bringing it down

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!

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

58.83 MB of App Dalvik utilized by activity com.siemens.ctsessions.activities.StartActivity. View details

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

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

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

App makes 3072.68 KB of network requests. Moving this to a background thread will improve load speed. View details

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

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

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

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

Total Network data consumed was 3072.68KB in Samsung Duos Galaxy J7 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

Screen coverage

Test Flows Panasonic P55 Karbonn Titanium Machfive Zenfone 2 Laser Lenovo VIBE K4 Note Samsung Duos Galaxy J7 Motorola Moto E (2nd gen)

Install app

  • Success

  • Success

  • Success

  • Success

  • Success

  • Success

Scenario 1

  • Success

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 2

  • Risk

  • Crash

  • Risk

competition benchmark

This app is ranked #553 in Medical

548
549
550
551
552
back-to-top