iPad, Letters.app and Nerd Myopia

As any­one read­ing this blog is almost cer­tainly aware, Apple announced the long-awaited iPad last week; and the tech world col­lec­tively lost their fuck­ing minds. As I’ve already opined, I think that Fraser Speirs has writ­ten the best analy­sis of the col­lec­tive pants-shitting and I would highly rec­om­mend read­ing Fraser’s arti­cle if you haven’t already. Flying some­what under the radar dur­ing all this bab­ble was another phe­nom­e­non which I think pro­vides an inter­est­ing par­al­lel to some of the ideas that Fraser artic­u­lates so well.

If you fol­low me on Twitter, you may have noticed ref­er­ences to some­thing called “Letters.app.” For those unaware, here is some back­ground. Earlier this month devel­oper Brent Simmons put out a call-to-arms for the devel­op­ment of a new email client to fit the needs of “devel­op­ers and power-users.” The argu­ment being that all extant instances of email clients (specif­i­cally for the Mac OS, but pre­sum­ably for all plat­forms) are lack­ing in some way that makes them unsuit­able for “devel­op­ers and power-users.” The goal of the project, soon dubbed Letters.app was to har­ness the skills and cre­ativ­ity of the indie Mac devel­op­ment com­mu­nity to build the per­fect beast. Shortly after­wards, the project com­pletely and very pub­licly imploded.

At this point I need to take an aside and clar­ify what I mean by “imploded,” as my asshole-sense can already detect the prep­ping of a thou­sand responses telling me that I am wrong. First of all, it is true that the Letters.app project is still under active devel­op­ment. Project pres­i­dent John Gruber (Daring Fireball) and project lead Gus Mueller (Flying Meat Software) con­tinue to make progress and I eagerly antic­i­pate see­ing the fruits of their labors. I con­sider myself an email power-user and hope that Letters.app might fit my needs.

However, I main­tain that a read of the archives of the (now closed) pub­lic dis­cus­sion email list proves my asser­tion. The mail­ing list dis­cus­sion is rife with con­tention, rigid-thinking, straw-man argu­ments and an over­whelm­ing dis­missal of the needs and require­ments of any­one who dis­agrees with a given poster. In almost every case those dis­missals are phrased some­thing like this: “Letters must/must not do X because it is meant only for ‘devel­op­ers and power-users’ and you don’t apply.” What is con­stantly missed, even in the face of it being pointed out, is that there are many peo­ple who are “power-users” of email who have never seen a line of code and who can barely reboot their com­puter. In one par­tic­u­larly ironic twist, at sev­eral points the prover­bial “non-power-user” is described as a “bored sec­re­tary.” This, more than any­thing, demon­strates the myopia of some of the “indie devel­oper” camp on the list. Having been a long-term denizen of the cor­po­rate world I can tell you, “sec­re­taries,” or “Administrative Assistants” as we call them in the enlight­ened post-1960’s are almost always the largest con­sumer /producer of email in an orga­ni­za­tion, and have the most need for power features.

So, the ques­tion is: “What does this have to do with the iPad?”

I would argue that the same myopic dis­missal of any­one who isn’t a devel­oper, and IT per­son or a tech­nol­ogy wonk as a “non-power-user” is as much respon­si­ble for the “future shock” that Fraser describes as it was the never-ending argu­ment on the Letters.app list. It is easy for us, and I include myself in this class on two of the three counts men­tioned before, to dis­miss the needs of non-technical power users. I’ve even seen some of this atti­tude in iPad defend­ers when they extol the virtue of the iPad as a device for their kids, or par­ents, or any­one who is pre­sum­ably “not good with com­put­ers.” Fortunately Apple isn’t so myopic.

Assuredly, the iPad will be a good fit for those users. I con­tend it will also be a good fit for cor­po­rate users who already have a pri­mary desk­top sys­tem and need a basic com­mu­ni­ca­tion and con­tent cre­ation tool for lim­ited travel. I con­tend that, with the proper third party appli­ca­tions, the iPad will be a good tool for many artists who work in the field. My Angry Mac Bastards co-host Peter Cohen is excited about the pos­si­bil­ity of an “Aperture Touch” prod­uct in con­junc­tion with the iPad Camera Connection kit. I myself and excited about the pos­si­bil­ity of tak­ing my writ­ing on the road with­out the over­head of a full Mac OS lap­top. People I know in the edu­ca­tion seg­ment, from K-12 all the way though higher edu­ca­tion have expressed excite­ment over how the iPad may be inte­grated into their work­flows. Not to men­tion the plethora of ver­ti­cal mar­ket opportunities.

What the tech media tends to miss is that all of the user classes I’ve just men­tioned con­tain “power users.” They’re just not nec­es­sar­ily power users of com­puter devel­op­ment and admin­is­tra­tion tools. As Fraser points out, peo­ple want to do “Real Work.” And for the vast major­ity of the world “Real Work” is not main­tain­ing com­put­ers. Apple com­put­ers and oper­at­ing sys­tems have always been about enabling “the rest of us.” The iPad is just the next step towards that goal. I choose to embrace that future. The iPad may not be the device for you, but to deny that there is a vast mar­ket for it is to show the same myopia that led to inane sug­ges­tions for Letters.app such as requir­ing the user to run a mail server on their desk­top just to enable local stor­age of email; some­thing even most power-users would agree is just retarded.

  • kvanh

    The pub­lic face imploded. We’ll see if the behind the scenes did too, prob­a­bly not. I think open­ing the mail­ing list to pub­lic that quickly was a mis­take, but I hope we con­vinced them to sup­port real IMAP.

  • TC

    Changing the IT par­a­digm isn’t going to be easy… I see it as being like tax account­ing. There are pow­er­ful peo­ple and com­pa­nies that derive a lot of rev­enue from the exist­ing fuckedup­ness. It is mainly those peo­ple who bitch about chang­ing the sys­tem: the rest if us just want to do what we do.

  • http://www.facebook.com/tomvons Tom von Schwerdtner

    The HTML email bit has been a pet peeve of mine for years. The idea that you have to use idi­otic ASCII for­mat­ting instead of a freak­ing HTML table dri­ves me nuts. Sane links, bare min­i­mum for­mat­ting capa­bil­i­ties, syn­tax high­lighted code sam­ples? All eas­ily within the realm of pos­si­bil­ity, but shot down by some fear of pur­ple text on a pink back­ground, which by the way, your grand­mother is still going to send you, it’s not like she knows or cares about this “text only” reli­gion.

    How bout we have a mail client that sends struc­tural and seman­tic HTML, sans col­ors and fonts, and lets the receiv­ing client style it as per the users pref­er­ence? How great would that be?

  • http://www.theangrydrunk.com The Angry Drunk

    I may not have made it clear enough, but you’re cor­rect, it was the pub­lic face that imploded. We’ll see how things progress on the letters-dev list.

  • http://www.theangrydrunk.com The Angry Drunk

    100% agree­ment. Anyone who thinks that, were email invented today, it wouldn’t default to some sort of styled text, is insane. Yet we insist on hob­bling our­selves with metaphors imposed by pre-1990 tech­nolo­gies. I think that the par­al­lel to the iPad bed-wetting is obvious.

  • http://alsowik.net/ josh

    People need to real­ize there’s a dif­fer­ence between “power users who are also devel­op­ers and tin­ker­ers” and “power users who just use some­thing a fuck ton”. And a device like the iPad will encour­age more peo­ple to become “power com­puter users”, just like the iPhone encour­aged peo­ple to use data from their cell phone provider.

  • Gatesbasher

    I think Speirs (and you) hit the nail on the head. When I hear that such-and-such a device can’t do “Real Work™”, in most cases it turns out the speaker con­sid­ers “real work” to be fuck­ing around with the com­puter try­ing to get it to do some­thing — any­thing. Which is great if that’s your job, but it’s not for all of us.

  • Ianf

    Agree with you, Drunky (and I’m stone sober, btw., as always), but, where Letters.app is con­cerned, how can ANYONE seri­ously treat a con­cept described solely as “awe­some” [“Need new email client; must be awe­some”]; there is no obvi­ous Mission Statement (that I can see); and the ensu­ing project of writ­ing pre­sum­ably RFC-822-compliant mail client is led by some­one who can not even be both­ered to sub­mit mes­sages in archive-readable for­mat? Or else, how do you pro­pose we read the dis­cus­sion msgs with unbro­ken paragraph-length lines? ( E.g. http://​lists​.ranchero​.com/​p​i​p​e​r​m​a​i​l​/​e​m​a​i​l​-​i​n​it-… )

  • http://www.theangrydrunk.com The Angry Drunk

    To be fair, they did come up with a Vision Statement at some point (for the life of me I can’t find it now though) and I think that the con­sen­sus is that the for­mat­ting issues have to do with Mail.app using format=quoted-printable instead of format=flowed. Nonetheless, they’re still wankers.

  • Ianf

    Before self-imploding, did any­one there even attempt to reexamine/ rede­fine the basic sequential-message-river par­a­digm of email clients, or was it all a bat­tle over fave fea­tures? Email badly needs a new client model, one designed with human, rather than machine heuris­tics in mind [ http://google.com/search?q=define%3Aheuristics ]. Example: when view­ing any sin­gle mes­sage, the client should dis­play instantly-compiled (e.g.) mail exchange fre­quency diagram(s) for that cor­re­spon­dent; most fre­quent com­mon words (=pseudo-tag clouds); sta­tis­tics over length and original-to-quoted text (akin to signal:noise) ratios; per­cent­ages of threads unan­swered, etc. The client already knows all that [and Gmail makes use of it], some of it well in advance and very suit­able for iter­a­tive accu­mu­la­tion, so why shouldn’t the recip­i­ents get to see it as well?

  • Sigivald

    Maybe I’m missin’ some­thing here, but why would I (or any other human “client”) want to see almost any of that, when view­ing a mes­sage?

    What will a mes­sage exchange fre­quency dia­gram tell me (that I didn’t already know; “X talks to me a lot” or “X doesn’t talk to me a lot”).

    Even worse, a word tag cloud?

    I mean, I sup­pose the proof is in the pud­ding and it would be worth look­ing at if some­one made it, just to see if some­how it’s use­ful — but on its face, it’s stuff I don’t care about mas­querad­ing as infor­ma­tion, tak­ing up screen real-estate and cog­ni­tive effort.

    Maybe email really does need a new client model … but I don’t think that’s the one it needs.

  • Yogi

    I’m all fired up about music, sheet music and tabs, for me and the band and stu­dents as well (all turn the pages together, now.)

    I can’t believe that peo­ple are dis­miss­ing it as a toy. All I’ll need on the road is a phone and the pad. Big win for my wrists.

  • Ianf

    I’m glad you’re ques­tion­ing my by neces­sity sketchy EXAMPLES of enhance­ments now miss­ing in email clients. Observe I never said any of that should be per­ma­nently on screen, prefer­ably con­fig­urable on demand. Because some of the listed func­tions indeed are novel, here is what I IMAGINE they’d be good for (and bear in mind that I am talk­ing about heavy mail usage: in excess of 150 mes­sages a day; 3000 – 4000 per month; and [cumu­la­tively] sev­eral thou­sand valid inquiries under a 10-year period — I no longer care to remem­ber, nor trust my instinc­tive recall of his­tory of/for each inquiry).

    • mail-frequency dia­gram: an at-a-glance
    graphic overview of his­tor­i­cal mail flow
    with the same indi­vid­ual mail-originator/
    recip­i­ent.

    • a pseudo-tag cloud: auto-compiled from
    exchanges ONLY with said orig­i­na­tor; to
    abet in deter­min­ing the nature of recur­ring
    inquiries (if any).

    • “sta­tis­ti­cal” dia­grams of signal:noise
    ratios (how­ever defined): helps me decide
    me whether cor­re­spon­dent is “seri­ous”
    (how­ever defined), and cares to express
    her­self clearly with­out end­less tail
    inclu­sions (which lower over­all com­pre–
    hen­sion of the exchange and can not be
    relied upon to pro­vide the back­ground).

    • per­cent­age of threads un/answered:
    cumu­la­tive val­ues of un/ resolved or
    one-off/ recur­ring nature of the
    cor­re­spon­dence.

    Observe that these were just EXAMPLES of func­tions pos­si­ble within cur­rent mail-client model, all per­fectly suit­able to be expressed by e.g. space-saving Tuftian sparklines [ http://​www​.edwardtufte​.com/​b​b​o​a​r​d​/​q​-​a​n​d​-​a​-​f​e​tch… ]; and I could think of sev­eral more com­plex ones were mail par­a­digm to change.…

  • Yogi

    OK, great. Now, please tell us WHY you want them.

  • Yogi

    OK, great. Now, please tell us WHY you want them.