App Quality Dashboard

Flirchi

2.5 / 5

Chhi Score

This app is performing

Average

Good

/5

High Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: 28.50 Sec
  • Launch time: 0.40 Sec
  • Application size : 15.21 MB
  • Last tested on : 03/03/2017
  • Build ID
    :   v8.5
  • Chhi Score
    :   2.5
  • Change Rate
    :   0%

What to fix?

18 Risk(s) are due to Threads in CPU 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.

Your App CPU is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage

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

18 tests need immediate attention. View performance graph.

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

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.

49.44 MB of App Dalvik utilized by activity ru.flirchi.android.Activities.Autorization.RegistrationActivity_. View details

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

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

213 apps having similar CPU load have low Chhi Scores

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

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!

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

Caching: Use LruCache for data caching to optimize memory usage

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

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.

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

Screen coverage

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

Install app

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 1

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 2

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

competition benchmark

This app is ranked #543 in Social

538
539
540
541
542
back-to-top