← Blog/App Quality

How to Improve Your App Health Score from 60 to 90+

Three real developers. Three low scores. Here is exactly what they changed: and how their scores improved from failing to store-ready.

Feb 15, 2026·7 min read·AppTester.co Team

A score below 70 means your app has a high probability of being rejected or receiving bad reviews in the first week. Here is how three developers turned their scores around : and what you can learn from their specific fixes.

AO

Adebayo O.

Fintech developer, Lagos

58

Before

91

After

Problem: 5 permissions requested at launch with no context

+12 pts

Fix: Moved camera and contacts permission to point-of-use. Removed READ_PHONE_STATE which wasn't needed.

Problem: No privacy policy URL in app or store listing

+18 pts

Fix: Created a proper privacy policy, hosted it, and linked it from Settings screen and App Store Connect.

Problem: App crash on Samsung Galaxy A-series (low RAM devices)

+8 pts

Fix: Identified a memory leak in the transaction history screen using Android Profiler. Fixed retain cycle.

Problem: Debug build accidentally submitted for testing

+5 pts

Fix: Configured CI pipeline to always produce Release builds. Added a check to ensure ProGuard is enabled.

MS

Maria S.

Product Manager, Berlin

64

Before

88

After

Problem: 6 permissions requested on first launch

+15 pts

Fix: Reduced to 2 permissions at install. Others moved to contextual request points within relevant features.

Problem: No PrivacyInfo.xcprivacy manifest (iOS)

+14 pts

Fix: Added privacy manifest declaring UserDefaults and NSFileManager usage. Updated Firebase to version with its own manifest.

Problem: App description inaccurate: referenced removed features

+6 pts

Fix: Rewrote App Store description to accurately reflect current functionality.

JK

Declan F.

Solo builder, London

52

Before

93

After

Problem: App crashed on devices with no SD card

+10 pts

Fix: Removed READ_EXTERNAL_STORAGE dependency. Migrated file storage to app-private directory.

Problem: No error handling for offline state

+12 pts

Fix: Added offline detection and graceful error messages for all API calls.

Problem: Two tracking SDKs declared in Data Safety form but missing from privacy manifest

+16 pts

Fix: Updated Firebase Analytics and Amplitude to versions with their own manifests.

Problem: App icon missing for 72pt size on some Android devices

+5 pts

Fix: Generated complete icon set using Android Studio Image Asset Studio.

Run your own health check: free

Upload your APK or IPA and get an instant score with specific issues identified. Takes 30 seconds. No account required.

Run Free Health Check