Apple's App Store now explains why it's recommending an app — discovery is shifting from popularity to personalisation

Apple's Personalized Collections and App Notes, live in the US since June 2026 and expanding to more regions, use on-device intelligence to recommend apps based on individual usage patterns and explain the reasoning — a real shift for anyone relying on 'app development cost' style discovery through broad App Store popularity.

Apple has started rolling out Personalized Collections and App Notes across the App Store’s Apps, Games and Search tabs — first announced at WWDC 2026 and live in English in the US since June, with wider regional and language rollout planned through the rest of the year. Instead of showing every user the same “Editor’s Choice” or top-charts list, on-device intelligence now recommends apps based on a person’s own download and usage history, and each recommendation carries an “App Note” explaining why it was shown — similar downloads, related interests, or usage patterns.

The practical effect: an app no longer needs to be broadly popular to get discovered. It needs to be a good match for a narrower slice of users who already behave in ways that predict they’ll want it. That’s a different optimisation target than the one most app store listings were built for.

Why this matters for app strategy, not just marketing

For years, App Store optimisation was mostly about keywords, screenshots, and chart position — get enough downloads and the algorithm rewards you with more visibility. Personalisation breaks that loop. A well-targeted niche app with a smaller but well-matched user base can now surface to exactly the right people, while a generic app with broad but shallow appeal may get recommended to no one in particular. Metadata, category accuracy, and how clearly an app signals what kind of user it’s for all start to matter more than raw download volume.

So what

If you’re commissioning a consumer-facing iOS app, this is a reason to be precise about who the app is for and what behavioural signals define that audience — that positioning now feeds directly into how Apple’s on-device model decides who to show it to. It’s a conversation worth having at the product definition stage, not after launch. See our iOS & Android development services or get in touch to talk through positioning as part of the build.

← All research

More research.

GitHub's Copilot metrics now count OpenCode and Claude Code traffic: who really uses which AI coding tool

On 23 October 2026 GitHub added a per-tool breakdown to the Copilot usage metrics API, so tools such as OpenCode and Claude Code are counted even without editor telemetry. It shows how mixed the AI coding tool stack inside software teams has become.

Read ›

GitHub Copilot retires Claude Opus 5 and GPT-5.6 Terra on 16 November: the model-churn bill for buyers

GitHub has announced that Claude Opus 4.8, Claude Opus 5 and GPT-5.6 Terra leave every Copilot experience on 16 November 2026. For anyone commissioning AI-assisted development, model retirement is now a monthly event to plan around.

Read ›

GitHub Copilot now benchmarks how 'agent-first' your developers are against your industry

On 22 October 2026 GitHub added opt-in industry comparisons to its Copilot impact dashboard, ranking firms by share of agent-first developers and by the merge rate of agentic pull requests. Here is how to read the numbers when you are buying software.

Read ›

Apple's new bait-and-switch rule 2.5.19: what it means for AI-built and fast-shipped apps

On 16 October 2026 Apple updated its App Review Guidelines: apps that change after approval can be removed from the App Store and the Developer Program, and AI-generated intimate imagery is now explicitly covered. Here is what founders commissioning an iOS app should check.

Read ›

GitHub Copilot agentic autofix is generally available: AI now fixes security alerts, and bills for it

GitHub made agentic autofix for code scanning alerts generally available on 15 October 2026. Copilot can now fix up to 25 security alerts in one pull request, using AI credits your supplier or your team pays for.

Read ›

GitHub AI Scan for pull requests goes GA: AI security checks for PHP, Terraform and Dockerfiles

GitHub's AI Scan for pull requests became generally available on 15 October 2026, checking languages the standard scanner misses. Findings are advisory and cannot block a merge, which matters when you buy software.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work