In Eric Schmidt’s 2015, the web is very, very fast

Via Rex, here’s Eric Schmidt’s vision of news in 2015:

It’s the year 2015. The com­pact device in my hand deliv­ers me the world, one news story at a time. I flip through my favorite papers and mag­a­zines, the images as crisp as in print, with­out a mad­den­ing wait for each page to load.

Even bet­ter, the device knows who I am, what I like, and what I have already read. So while I get all the news and com­ment, I also see sto­ries tai­lored for my interests.

Two things: first, I just rewatched EPIC 2015 the other day and it’s still fun (and Matt’s nar­ra­tion is still, well, epic); sec­ond, the rel­a­tive tame­ness of this vision means there are still big oppor­tu­ni­ties for other play­ers to rein­vent news—to par­tic­i­pate in that rein­ven­tion. This is not gonna be Google’s game.

There is one thing worth not­ing in this op-ed. You’ll notice Schmidt hits the “magazine-like” metaphor sev­eral times. This is an idea you’re hear­ing a lot from GOOG lately. To para­phrase: You don’t have to wait for the pages of a mag­a­zine to load, right? Well, the web should be like that. When you click a link, or swipe your screen, the next page should sim­ply be there.

Now, this vision of a zero–load-time web is actu­ally pretty inter­est­ing. But is it truly transformational—the way, say, always-on broad­band was trans­for­ma­tional? I don’t know. What do you think?

12 Responses

    Tim Maly says:

    I was struck by this sec­tion of the piece as well because it seems to me like his bold vision for 2015 is Stum­ble­Upon reim­ple­mented with bet­ter screen res­o­lu­tion, Type­Kit and lay­out tools. Stum­ble­Upon (if you have the tool­bar in Fire­fox) already pre-caches your next stum­ble, so the expe­ri­ence of click­ing on the “next” but­ton is instantaneous.

    I’m still pissed that eInk turned out to mean a sin­gle page on a slab that flashes to refresh every time you change pages. When WIRED first talked about the tech years ago, there was a clear vision in my mind. And actual book (the eInk is paper! It’s flex­i­ble) that had at least a magazine’s worth of pages that got rewrit­ten that I could flip through. LIKE A MAGAZINE OR BOOK. Instead, we have dig­i­tal chalk slates.

    Tim Maly says:

    Part 2
    Part 2
    That said, truly instan­ta­neous mat­ters. One of the things that great about the iPhone is that scrolling is such that you feel like you are actu­ally phys­i­cally manip­u­lat­ing some­thing. That makes it fun to use. When you hit the bits where it’s slow (like load­ing maps and try­ing to go straight to typ­ing in your search but it’s hang­ing because it’s load­ing data) it alien­ates you a lit­tle from the tech. I think that’s impor­tant. Even now with always on broad­band, some­times things load slowly enough that I tab over to see what’s in another page and then by the time the page has loaded, I for­get exactly what I was there for. Just for an instant, but that’s enough to break flow.

    It is hard to enter into the state of flow on Inter­net Apps. It’s one of the huge prob­lems with Google Wave so far. By being in a web browser you lose all the short­cuts you are used to and var­i­ous parts of the inter­face don’t behave as I expect and it’s fid­dly enough that it makes it impos­si­ble to just go in there and type. Even now I’m typ­ing this in a reg­u­lar text edi­tor to paste into the snark com­ment box. 

    The Cana­dian equiv­a­lent of Barnes and Noble released an app for the iPhone called Short­cov­ers. It’s an ereader and it has page flip like Euca­lyp­tus or Clas­sics. Except that for one rea­son or another, it lags your fin­ger. You feel like you are giv­ing the pro­gram a com­mand, where in Euca­lyp­tus, you feel like you’re chang­ing a page. This matters.

    So yes, I grant a pos­si­bil­ity that truly instan­ta­neous page loads could be trans­for­ma­tional in ways we don’t quite expect.

    Tim Maly says:

    Part 3
    I think that finally being able to do real typog­ra­phy and lay­out will mat­ter even more. I mean it’s been how many years and there are still, what, 10 web-safe fonts? What a travesty!

    That’s the other half of magazine-like that is maybe implied and that’s some­thing I’d really like to see. It’s kind of a hard prob­lem when you are try­ing to be all things to all screen sizes. Except. Except that if some­one could start imple­ment­ing on big­ger screens the behav­iour of the good mobile brow­ers (such as Safari and pre­sum­ably the one on Droid) with effort­less zoom­ing and pan­ning and scrolling then we could start to see some good stuff. Dif­fer­ent sizes, pul­lquotes and lay­outs mat­ter. The visual queues that edi­tors use to tell us which sto­ries to bother with get lost on the web.

    Remem­ber in the photo synth demo when they showed non photo con­tent with zoom in to see the fine print? We need that.

    The new Time/Sports Illus­trated dig­i­tal mag­a­zine demo also seems promising.

    Robin Sloan says:

    I’m so torn on this.

    On one hand, I absolutely agree. Going through the process of lay­ing out my book in InDe­sign was such a good reminder: oh yes, right, THIS is what design looks like. THESE are the tools you’re sup­posed to have. There’s no ques­tion that font choices, lay­out deci­sions, etc. don’t just adorn or frame the con­tent; they ARE the con­tent in lots of impor­tant ways.

    On the other hand: the web has done pretty well w/out these tools so far. I mean really, it has. And in fact, the trend-line — plot­ted by all of us, by our actual daily behav­ior — has been zoom­ing AWAY from fancy page design. We don’t even like mul­ti­ple columns any­more! We like a long river of text: a straight-down-the-page blog, a Twit­ter feed.

    Now, I def­i­nitely WANT the first argu­ment to be more com­pelling. Increas­ingly I can’t stand ran­dom con­tent shrap­nel. And yet, and yet. There are a lot of things we want, & the web doesn’t deliver them. There are a lot of things we want, and they lead us away from the real oppor­tu­ni­ties — the Googles and the Twitters.

    I mean, I liked a lot of the ideas in that Sports Illus­trated video demo, but I didn’t find it CONVINCING. It was too much like the old Apple Knowl­edge Nav­i­ga­tor demo; too pat, too per­fect. Too con­tained. Not enough chaos. I mean, I’m sure Time Inc. and oth­ers will go ahead and make prod­ucts like that, and they will be cool; I just don’t think they’ll account for a par­tic­u­larly big slice of media con­sump­tion. “The elite and the elderly…” ;-)

    So what’s the syn­the­sis? What’s the for­mat that gives us our design arse­nal back — but that ALSO rec­og­nizes the real­ity of the way peo­ple browse the web — that doesn’t try to turn back the clock and make an Inter­ac­tive Mag­a­zine circa 1998? An open ques­tion. Although I think Pic­tory is a point along the path, and it’s inter­est­ing to see the ways in which it’s magazine-y and the ways in which it’s webby. I think it’s a much bet­ter model for the future than the SI video. Actu­ally, I’m going to blog that right now.

    Tim Carmody says:

    One of the big ten­sions of the moment is between con­tent cre­ators who want their cre­ations to be sta­ble — screen-independent, platform-independent, solid objects — and con­tent con­sumers who want to be able to scram­ble that con­tent as they see fit. 

    Now this oppo­si­tion doesn’t actu­ally hold — there are plenty of con­sumers who WANT to con­sume a sta­ble object, because they like media that seem like the prod­uct of a total design+content vision. And there are plenty of cre­ators who are excited about the idea that their cre­ations are live objects in the world, gath­er­ing points for re-creation and community.

    But there’s def­i­nitely a ten­sion between a sta­tic and a dynamic object. And gen­er­ally, con­tent providers/managers have an inter­est in keep­ing the objects sta­tic, and con­tent repur­posers have an inter­est in keep­ing it dynamic. 

    (Note that sleight-of-hand — it’s no longer cre­ators, but pub­lish­ers and rights man­agers, no longer con­sumers, but poach­ers who arbi­trage con­tent. There are sin­is­ter shadow ana­logues to every posi­tion in this spectrum.)

    Book­square had some good com­men­tary on this recently. Essen­tially, some pub­lish­ers are try­ing to rethink DRM, not as a way to pre­vent piracy, but as a way to pre­serve the through-designed integrity of a media object. An indus­try con­sul­tant told the assem­bled pub­lish­ers “You must have DRM to guar­an­tee that your con­tent is used in the way you want. You retain con­trol of use” — or some­thing like that — to which Kasia at Book­square retorted, “What hap­pens when your con­tent becomes my content?”

    I’m going to take a long quote here, because I think this is a good insight:

    [This is] the dirty lit­tle secret of dig­i­tal media: I, the con­sumer, never really “own” what I buy. This col­ors my per­cep­tion of the trans­ac­tion, impact­ing every­thing from price to usage. I con­stantly weigh what I get against what I’m pay­ing for it. I’m going to say it plain: this is not a bad thing as long it’s not forgotten.

    In the tra­di­tional book trans­ac­tion, author and pub­lisher con­trol over the book ends when I hand over my money for the book. All the hopes that con­tent will be used in the man­ner the pub­lisher and/or author envi­sion are gone when I am handed a receipt by the cashier. I can do any­thing I want with the (print) book, includ­ing using it as a pil­low (hat tip to Lawrence Lessig). I can lend it. Resell it. Make art from it. Rent it.

    Dig­i­tal is dif­fer­ent. I know I say it a lot. I believe ebooks/digital are a wholly new mar­ket with new rules and reg­u­la­tions (maybe I should say mar­kets?). This mar­ket­place should not be treated nor expected to con­form to busi­ness as usual. Yes, this poses chal­lenges; it also cre­ates oppor­tu­ni­ties. Port­ing the “book” men­tal­ity to dig­i­tal lim­its the imagination.

    But this analog/digital dis­tinc­tion doesn’t fully hold up either. Yes, I can do what­ever I want to a book that I buy — but I can’t redesign it on the fly. Like­wise, I can fold or lend or trash or cut pieces out of a mag­a­zine, but that doesn’t change the fact that it’s a through-designed object before I ever get it. And there’s vir­tu­ally noth­ing I can do to make the doc­u­ment more dynamic, more networked. 

    In one sphere, I’m lim­ited by the con­straints of my con­tract with the con­tent provider; in the other, I’m lim­ited by the con­straints of the phys­i­cal world itself.

    Tim Maly says:

    Jason Kottke’s post about Google’s new DNS and the impor­tance of speed is worth link­ing to I think.

    Marissa ran an exper­i­ment where Google increased the num­ber of search results to thirty. Traf­fic and rev­enue from Google searchers in the exper­i­men­tal group dropped by 20%.

    Ouch. Why? Why, when users had asked for this, did they seem to hate it?

    After a bit of look­ing, Marissa explained that they found an uncon­trolled vari­able. The page with 10 results took .4 sec­onds to gen­er­ate. The page with 30 results took .9 seconds.

    Half a sec­ond delay caused a 20% drop in traf­fic. Half a sec­ond delay killed user satisfaction.

    So, wow. Instan­ta­neous may very well be transformational.

    Tim Carmody says:

    Why isn’t there a kind of rich RSS that down­loads whole web­pages (images, videos, and all), pre­caches their links, and stores it all locally? That would be awfully close to instant — in most cases, you wouldn’t have to do a server call at all at the moment of read­ing. You’d have already down­loaded it. 

    It’d be like the dif­fer­ence between watch­ing The Daily Show in iTunes or watch­ing it on Hulu. But for text-based-media on the web. Espe­cially for sub­scrip­tion con­tent — which is what a mag­a­zine is — this would be espe­cially powerful.

    Schmidt ought to take a look at newsless.org before he starts talk­ing about get­ting the world deliv­ered “one story at a time.”

    As Matt and a few oth­ers have been say­ing, in the future the atomic unit of news wont be the story. We’re talk­ing con­text, liv­ing nar­ra­tives, con­stantly evolv­ing wikinews — all things that *require* the network.

    Yes, I’m the dude who just had this open in his browser for two days so he could even­tu­ally come around to com­ment­ing on it.

    The point that I’d like to make is that a zero-latency and zero-load time web is less impres­sive with a device as we typ­i­cally think of it, ahem “wait for the pages of a mag­a­zine to load,” and more impres­sive with some­thing like this. What Schmidt doesn’t allude to, and I think this is more because of the audi­ence he was writ­ing for and less because of his gen­eral intel­li­gence and vision, is that the device that he’s going to have in his hand is going to be react­ing in real-time to stim­uli in the envi­ron­ment. It’s all about infor­ma­tion. Devices get in the way of what we’re try­ing to do.

    This is a seed for some­thing big­ger I can’t artic­u­late yet. Btw, you should install sub­scribe to com­ments so that we can get email noti­fi­ca­tions of fol­low up comments :)

    Tim Maly says:

    Daniel,

    I think that your insight is right. Instan­ta­neous (or near instan­ta­neous) results make cer­tain apps pos­si­ble that weren’t before, much as broad­band makes YouTube, Nap­ster., and iTunes possible.

    I’m reminded of Jakob Nielsen’s Pow­ers of 10: Time Scales in User Expe­ri­ence post. Specif­i­cally the first three scales. 0.1 sec­onds and 1 second.

    0.1 sec­ond is the response time limit if you want users to feel like their actions are directly caus­ing some­thing to hap­pen on the screen.”

    When the com­puter takes more than 0.1 sec­ond but less than 1 sec­ond to respond to your input, it feels like the com­puter is caus­ing the result to appear.”

    More than 10 sec­onds, and you break the flow. Users will often leave the site rather than try­ing to regain the groove once they’ve started think­ing about other things.”

    So yeah, what hap­pens when extremely rich meta­data seems to always be “just there”.

    Robin says:

    Eep. This doesn’t bode well for any of the e-readers, which are all sort of embar­rass­ingly slow. And that’s a domain where, like, the com­par­i­son to a book or mag­a­zine is not REMOTE; it’s obvi­ous! It’s the standard.

    I think what this really means is that the e-reader that gives us the speed we need is going to get a lot of love, and instantly make all the other devices seem stu­pidly lame in com­par­i­son. And gotta say, I think that e-reader is prob­a­bly gonna be Apple’s.

    Tim Carmody says:

    Yeah, the biggest bum­mer for me from recent reviews of the Nook is that the Nook is SLOW. Slower even than the Kin­dle, it looks like.

    Again, speed needs a faster proces­sor, a bet­ter graph­ics chip, and more mem­ory. All of those things pep up costs and drag down bat­tery life.

    Also, once you’ve got all of those things and a hork­ing big screen, it makes no sense not to start putting pho­tographs and video on there.

    Which means, yes — it’ll be a mul­ti­me­dia device. Prob­a­bly from Apple.

The Snarkmatrix awaits your reply