Awesome work, Stephen!
Thanks, Daniel! :)
iTunes Instant, Solve 2 Huge iTunes Problems: Cluster Interface & Slow Search
11–20 of 38 posts
Re: iTunes Instant, Solve 2 Huge iTunes Problems: Cluster Interface & Slow Search
#12From what I'm hearing, Android Market is the one that needs help with their search.
Also, I've been thinking to make a more mobile-optimized version of the site right now.
Re: iTunes Instant, Solve 2 Huge iTunes Problems: Cluster Interface & Slow Search
#13Earlier quoted context omitted.
Yes. Check out Marco Arment's preview.fm. He had a similar web app that allows you to preview album.
Oh yeah, I've heard about it before. I will definitely implement it using if it doesn't heavily affect loadtime.
Definitely man! That feature will be quite useful.
Re: iTunes Instant, Solve 2 Huge iTunes Problems: Cluster Interface & Slow Search
#14All of these jsonp / iframe based instantizers have to be putting load on servers (probably not in great volume, but still). There's a reason Google had to put special consideration into how to make the ajax-endpoints scale :)
In terms of scalability, YouTube Instant will encounter lots more problems than iTunes Instant. It's full-length video vs. 100x100 artwork image.
Re: iTunes Instant, Solve 2 Huge iTunes Problems: Cluster Interface & Slow Search
#15All of these jsonp / iframe based instantizers have to be putting load on servers (probably not in great volume, but still). There's a reason Google had to put special consideration into how to make the ajax-endpoints scale :)
In terms of scalability, YouTube Instant will encounter lots more problems than iTunes Instant. It's full-length video vs. 100x100 artwork image.
For Youtube Instant, the actual search terms are hitting suggestqueries.google.com for the autocompletion, which is what is powering google.com.
The actual video coming through is likely from a CDN, which are already built upon an infrastructure for scaling. Probably not as big of a deal as you think. Bandwidth wise it's unlikely that somebody watches the entire video as much as they rapidly hit different videos.
Re: iTunes Instant, Solve 2 Huge iTunes Problems: Cluster Interface & Slow Search
#16Awesome work man! To make it fully Google Instant, you would want to run the query against the first result in suggest. For instance, if you type in "la" you would get "lady gaga" instead of "L.A". Keep up the great work. :)
Re: iTunes Instant, Solve 2 Huge iTunes Problems: Cluster Interface & Slow Search
#17Re: iTunes Instant, Solve 2 Huge iTunes Problems: Cluster Interface & Slow Search
#18Awesome work man! To make it fully Google Instant, you would want to run the query against the first result in suggest. For instance, if you type in "la" you would get "lady gaga" instead of "L.A". Keep up the great work. :)
Hm. I am not sure if that's possible through Apple's API. I will take a look.
Re: iTunes Instant, Solve 2 Huge iTunes Problems: Cluster Interface & Slow Search
#19Awesome work man! To make it fully Google Instant, you would want to run the query against the first result in suggest. For instance, if you type in "la" you would get "lady gaga" instead of "L.A". Keep up the great work. :)
Hm. I am not sure if that's possible through Apple's API. I will take a look.
Though not specific to music (and would have mostly non-music suggestions), you could hit suggestqueries.google.com with a jsonp-formed request. (maybe throw "music" in front of the typed query or something to apply filtering).
Re: iTunes Instant, Solve 2 Huge iTunes Problems: Cluster Interface & Slow Search
#20$.post("/itunes/ajax", {'q': q, 'hell_yeah': 52012} <-- Hell yeah? :P