> The tough part is that there are so many games to support that it won't scale to show every game, so some sort of search/typeahead is necessary. On the other

> The tough part is that there are so many games to support that it won't scale to show every game, so some sort of search/typeahead is necessary. On the other hand, the most popular 4-5 games (I imagine) will get the majority of the volume, so it might make sense to have a hybrid approach if we don't know what game you play already (show most common 'n' games as buttons, allow search as well). I'd have to experiment with that. Fair points. One strategy we've done is show the more important games _to the user_ first and sort appropriately (pre-orders, installed, played, etc) but that data is likely difficult to get, at least for a new user. But you could show the games they own / primarily use first and go from there and / or popular ones like you were suggesting. You're a web app so drop downs are not as awkward as, say, on a console but I still try to see if there are creative but intuitive ways to avoid them :)