Website content suffers from a lack of clarity around what we mean and present in terms of "local content," generally with regard to language and region (often talked about as "interest"). This often comes up in conversations about filtering content based on various data: What language does the site support? Does it support a language based on user pref or by detected region? What does it mean to "support" a language? Does the site provide content specific to a region? Does the site's URL change based on language? on region? Does the site block a consumer's access based on the consumer's detected region (like, bbc tv)? What localizations of the website listing data (on Marketplace) should we show? How should we maintain that data, since the website may update itself without us knowing?

We should confirm this with the UI side, but the idea is that the UI would request in whatever language the device is operating. If we can return data in that language, we should; if we can't, we should return in English (default).

In other words, this should be handled just as we currently do for webapps.

This is unchanged. Resolved until verified by QA (once we have data).