Give it a try - deploy your iOS app with a totally unique name and let me know if you can find it.

It won't show in search results, no matter how many pages you scroll through.

Apple + The Web is a match made in hell.

All of their services that are network heavy (TV, iCloud, Apple Music, News, Safari Sync) are so slow and do huge full reloads of every bit of state, so you just constantly see loading spinners, or worse in iCloud, you see nothing and eventually it will pop all the new stuff in to view, with no way to force a refresh.

I get that CAP theorem exists, but other providers at least seems to understand opportunistic sync and do a job of making it work for the user, but Apple seems to think that inconsistent views over data can't be helped and that every user should understand eventual consistency.

Their SDKs for syncing data to iCloud have long been a joke in the developer community and I think there have been 3 attempts at getting CoreData -> iCloud working, with the last iteration NSPersistentCloudKitContainer often being used as the [butt of jokes, a case study on poor networking talent at Apple] among iOS developers.

I wouldn't be surprised if it's tuned based on what people tap after a query, popularity stats generally, or other similar stats, and so they rebuild it only every few days after accumulating more stats.

Establishing popularity at a point in time requires a window of time.

If I had to guess, they pick a window of a few days because if you did it every minute or even every hour, there might be wild fluctuation in the long tail of apps, depending on whether 8 or 0 people happened to download it in that time.

You could fix this by making window size inversely proportional to short-term popularity and running every 15 min, but that's just more effort to reason about and code and debug. It seems like something they absolutely should do, but I can see why it would be pushed down the backlog.

DNS records don't take days

DNS records take a minute or two to update

The CAP theorem.