If your store console shows plenty of product page views but few installs, people are interested enough to look — and something on the page is stopping them. The good news is that the causes are usually identifiable.
The visitor doesn't understand the app quickly enough
Visitors spend seconds on a listing. If the title, icon and first screenshots don't answer 'what is this and why should I care?', they move on. Test your listing by showing it to someone unfamiliar with the app for five seconds and asking what it does.
The listing doesn't match where they came from
Someone who clicked an ad about budgeting, then lands on screenshots about investment tracking, will feel misled. Check that each traffic source — ads, social posts, search terms — leads to a listing that continues the same message. Both stores support custom product pages or store listings for this purpose.
Social proof raises doubts
- A low average rating or a run of recent negative reviews.
- Very few ratings, which makes the app feel unproven.
- Developer replies that are missing, defensive, or copy-pasted.
The value isn't clear before the commitment
Subscriptions, sign-up walls and permissions all add friction. If the listing doesn't establish value first, the perceived cost of trying the app feels too high. Make it clear what users get for free, and what the paid tier adds.
Technical and practical blockers
- Large download size on mobile data.
- Outdated 'last updated' dates that suggest an abandoned app.
- Missing localization for key markets.
- Device or OS compatibility issues.
How to work out which problem you have
Compare conversion by traffic source and by country in your store console. A problem across every source points to the listing itself; a problem in one source points to a mismatch between that channel and the page. Then change one major element at a time — ideally through the stores' built-in experiments — and compare against your baseline.