App Quality Dashboard

Flamp

3.9 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 47.93 Sec
  • Launch time: Icon 3.31 Sec
  • Application size: Icon 53.87 MB
  • Last tested on : 28/04/2017
  • Build ID
    :   v3.0.5
  • Chhi Score
    :   3.9
  • Change Rate
    :   -2.5 %

What to fix?

Build v4.1.0 did better in Network . Spikes in Network contributed to score drop by 28.95%

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.

13 Risk(s) are due to Threads in CPU exceeding the threshold.

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

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

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

Consider re-merging the code from build v4.1.0, Network score was 3.8

The app's CPU score has improved by 4.55% compared to build v4.1.0! Good job!

13 tests need immediate attention. View performance graph.

Utilization of Memory is close to the threshold.

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

App size increased by 48.32% See how to optimize.

Utilization of CPU is close to the threshold.

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

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

Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down

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

Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down

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

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

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

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.

61.26 MB of App Dalvik utilized by activity com.flamp.mobile.ui.activities.MainActivity. View details

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

Total Network data consumed was 1564.95KB in Motorola Moto E (2nd gen) , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps

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.

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

The app's Memory score has improved by 2.63% compared to build v4.1.0! Good job!

Screen coverage

competition benchmark

This app is ranked #252 in Travel & Local

247
248
249
250
251
back-to-top