4 ms·
As a user-side filter, this is actually not that difficult to implement (assuming the device caches the list of purchased app ids for the current iTunes account
by tehwalrus 13y ago
As a user-side filter, this is actually not that difficult to implement (assuming the device caches the list of purchased app ids for the current iTunes account, or even easier just the apps that are already installed on this device).
It means it'll take multiple requests to get all the results, sure, but if you weigh the initial request statistically (for the first 10, I think we'll need 12..) and so on, you can avoid even that.
- zimpenfish 13y agoMultiple requests that the client is paying for over a possibly flaky network connection and now you have to handle all sorts of edge cases and errors that you didn't before. Why bother?
- tehwalrus 13y agoThe app store (at least in the UK) has always been hideously slow and rubbish, even on a fast connection. I don't even try on cellular data anymore (to look at stuff, not even download/update.) As I said, this wouldn't involve much more in the way of data transfer than the current setup. I assume that 15 apps instead of 10 preloading is the same order of magnitude; the latency is the kicker, not the tiny bandwidth required for metadata and icons.