App Quality Dashboard

FRINWO

1.6 / 5

Chhi Score

This app is performing

Poor

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

High  Risk

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 24.50 Sec
  • Launch time: Icon 0.43 Sec
  • Application size: Icon 34.56 MB
  • Last tested on : 28/05/2017
  • Build ID
    :   v2.8
  • Chhi Score
    :   1.6
  • Change Rate
    :   -42.86 %

Insights (23)

What to fix?

Must fix: App crashed because of 2755): FATAL EXCEPTION: AsyncTask #3 2755): Process: com.frinwo.mobile.frinwo PID: 2755 2755): ... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!
The app's Memory score has improved by 13.33% compared to build v2.1! Good job!
Utilization of CPU is close to the threshold.
The app has a high performance risk for the phone manufacturer(s) Motorola. Check coverage report for more details.
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Optimize the app to render elements at 60 FPS for buttery smooth experience.
The app has crashed on few device(s)! View details
Testability: Providing login / sign-up details could very well improve depth of bot clicks
Caching: Use LruCache for data caching to optimize memory usage
30.30 MB of App Dalvik utilized by activity com.nubblertech.mobile.peertree._activities.FrinwoMainActivity. View details
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.
3 Tests crashed out of 6 Tests. Check where the app crashed. View details
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
Printing logs on callbacks would make debugging easy for tests run in our platform
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Well done, Network consumption has come down by 81.81 % compared to build v2.1
The app's Network score has improved by 13.95% compared to build v2.1! Good job!
The app's CPU score has improved by 42.86% compared to build v2.1! Good job!
Unlock more fixes
competition benchmark

This app is ranked #1702 in Tools

1697
1698
1699
1700
1701
back-to-top