grigs

{
	"700554543387711": {
		"id": "700554543387711",
		"latest_version": {
			"id": "455210147987840",
			"article_canonical_url": "http:\/\/www.buzzfeed.com\/expresident\/steps-to-instantly-improve-your-day",
			"article_version_number": 2,
			"cover_media": {
				"__type__": {
					"name": "DocumentVideoElement"

grigs

{
	"672858856170909": {
		"id": "672858856170909",
		"latest_version": {
			"id": "994845887216565",
			"article_canonical_url": "http:\/\/www.theatlantic.com\/magazine\/archive\/2015\/06\/the-execution-of-clayton-lockett\/392069\/",
			"article_version_number": 78,
			"cover_media": {
				"__type__": {
					"name": "DocumentVideoElement"

grigs

// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console

grigs

I need to write this up in more detail soon, but in chatting with Patrick, it is clear that 140 chars isn't cutting it.

The way I've been thinking about the web on TVs and consoles is something like this:

• What are the design patterns and interaction models that would make for a successful experience?
• Can we build those experiences now? If not, what would need to change to make it possible?

In my mind, this starts with the basics of designing an interface that works well on a TV and can be interacted with using a remote control. Once we have the basics out of the way, we can proceed to multiscreen interactions.

A basic television layout

grigs

AC.AmbientVR = Class.create({
    __defaultOptions: {
        imageIndexOffset: 0,
        initialPos: 0,
        throwable: false,
        invert: false,
        infiniteAxis: false,
        grabRotateDistance: 780,
        allowMobileScroll: true,
        introSpins: 0,

grigs

if (typeof (AC) === "undefined") {
    AC = {}
}
AC.Detector = {
    getAgent: function () {
        return navigator.userAgent.toLowerCase()
    },
    isMac: function (c) {
        var d = c || this.getAgent();
        return !!d.match(/mac/i)