Language has lived, lives, and will live on.
Great conversation here discussing how the Library of Congress, the largest library on the planet, is encouraging folks to use their digital resources and data sets in innovative ways as part of a general rethinking of the cultural role of libraries today.
I was particularly struck by Kate Zwaard’s thoughts on how the notion of ephemerality is changing in the age of Instagram, mobile, and cloud computing:
I think the other thing about the ephemerality of the material as far as the young people think about what they create. It think actually they don’t think about it as ephemeral. They actually trust the world to keep it. So they don’t think about their photos as disposable but they don’t think about storage. They’ve actually abstracted that, right? That’s someone else’s problem. And to me that’s actually very good. I think reconstructing an archive from someone’s cloud services is very possible.
With WWDC 2016 upon us and its expected focus on the much-anticipated third-party Siri API, I’d like to reflect on how Apple has been preparing native app developers for a world where the experience of a given application service or brand is multifaceted, continuous across platforms, extensible, and, ironically, as a consequence of increasing reach, also at risk of being fragmented, subsumed, and erased.
Last year while attending WWDC, I had the good fortune to participate in the inaugural Layers conference, which was introduced as a design-oriented complement to the generally developer-focused WWDC “main event” of the week. The conference size, the diversity of its events, the approachability of its speakers, the range of topics covered, and the engagement level of the audience all came together to make Layers a truly inspiring and memorable experience. One presentation from last year in particular has stuck with me as I’ve thought through the changes we are seeing in the way we interact with services and brands on our iPhones.
Neven Mrgan spoke about some of his favorite things, and, loosely, the sometimes unexpected goodness that comes from sharing what you love. Chuck Jones’ seminal Duck Amuck cartoon was one of the beloved things Mrgan shared (@ around 20:00), a rare treasure which I agree is both wildly entertaining and endures as required reading for anyone interested in the art and craft of animation, filmmaking, or storytelling and visual art in general. But what caught my attention that day was Mrgan’s off-handed comment about the sequence near the end of the cartoon where the frame literally begins to close in on poor Daffy, collapsing from all directions. He joked the image reminded him of his time designing responsive web applications.
The analogy was spot on and, as I thought about it more, seemed appropriate not only to web app design but equally reflective if perhaps in a more abstract way of the fundamental changes native mobile apps have witnessed in recent years, especially in light of Apple’s announcements that very week, which included: app “thinning” and targeting application assets for different devices, Siri Proactive and app deep linking, and multitasking and split-screen window management in both OS X and iOS. Through the lens of Duck Amuck, Apple’s announcements could be seen as the latest in a series of operating system enhancements (cf. iOS 8’s share sheets and extensions framework, notification center widgets) designed to deconstruct what it means to be—and what it means to experience—a modern, mobile (iOS) application.
The trend continued with the hardward-specific “peek and pop” feature enabled by 3D Touch announced later in the year as a feature exclusive to the iPhone 6S and 6S Plus. So it wasn’t surprising that many industry commentators began to question the long-term fate of native apps. And given recent investments in messaging and chat bots, major platform players, especially those who have been laggards in mobile, appear anxious to speed the demise of the standalone app (store), instead encouraging companies to deliver their services on their respective “aggregator apps” or “portals” as Ben Evans astutely describes them, such as Facebook Messenger, Microsoft Skype, Kik, Slack, and the most successful to date, WeChat. Even Amazon’s Echo requires a companion mobile app to manage third-party aggregated services through so-called “skills”.
In parallel, responsive web design emerged to address the proliferation of devices accessing the world wide web today, and effectively, with limitations, provide native app-like experience to web apps when accessed by mobile devices. Rather than developing and serving mobile-specific sites (remember WAP?) for mobile devices, the responsive web is built on the idea that a site should be fluid in nature and able to gracefully adapt its content and services to accommodate the way in which that content is accessed and used.
As with responsive web design, native apps will continue to evolve with greater adaptability based on device type and screen size (including no screen at all) and, by extension, their respective interaction models. Traditional graphical UIs will co-exist with conversational voice and text options. The challenge will be how best to maintain context across these interaction models and move users as seamlessly as possible between them when necessary. And users, for their part, should prove equally adaptable as long as expectations are clearly communicated, transitions are consistent and predictable, and transactions are fast, accurate, and add value.
Rest in peace, and thank you for the films you leave with us.
Netscape Navigator was a browser created by a group led by a twenty-four-year-old named Marc Andreessen, who was described in Newsweek as “the über-super-wunder whiz kid of cyberspace.” The company’s I.P.O., on August 9, 1995, was a huge success. Five million shares went on sale on Nasdaq, at twenty-eight dollars a share; they closed the day at $58.25. The Times called it “the best opening day for a stock in Wall Street history for an issue of its size.
A little more than two weeks later, Microsoft released Windows 95, backed by what was reported to be a three-hundred-million-dollar marketing campaign, along with its own browser, Internet Explorer 1.0, and the browser wars were on. Netscape, of course, was quickly and easily outmuscled by Microsoft. In 1998, Netscape was acquired by AOL, and it faded into insignificance.
So much to like here. Have to love El Ateneo (a converted theater!!). If pressed, at the moment, I think the old Seminary Co-op would top my list, not for anything overwhelmingly beautiful about the space, but the overall feeling of submersion it always created. Books and basements. Who knew?
On the eve of Apple’s “Spring Forward” event, I thought it would be worthwhile to revisit Robert Cringely’s prediction for 2015 as the year “when nothing happened” and, particularly, his take on the significance and reception of the Apple Watch:
The Apple Watch is Cupertino grabbing mindshare and early adopter wallets, nothing else.
Even those who are typically bullish on Apple seem to be restraining their enthusiasm and predictions of massive success for the Apple Watch. All except the stock market itself, with AAPL up over 14% YTD. The naysayers are hedging a bit too. If you widen the view on Cringely’s comment, he isn’t exactly dismissing the Apple Watch to the dustbin of history, instead pointing to 2016 as the year to watch.
I am hopeful he’s wrong. I personally find even the most fanciful aspects of the Apple Watch experience intriguing, at least as they have been described up to this point, and applaud Apple for the tact they have taken as they methodically enter the nascent wearables market. I expect many recent enhancements to the iOS experience like Touch ID and the application extensions framework will be all the more relevant once the Watch is in the wild.
Critically, though, unlike the release of the iPhone in 2007, there isn’t an obvious problem begging to be simplified and redefined. We aren’t dissatisfied with our time pieces in the same way that so-called smartphones left much to be desired eight years ago. The Apple Watch is a much harder sell because of this; it is trying to extend, and ideally in many situations, replace the iPhone experience itself (which obviously is a bit thorny for Apple, though they have been famously comfortable with product cannibalization before) rather than displace something already taking up space on everyone’s wrist.
Will the convenience and attempt at a kind of naturalness by situating tech on your arm rather than in your pocket, be as obvious when we look back on 2015 as portable touch screens appear now, when we reflect on the dark ages of 2006?
It might just come down to the distillation Apple is promising with the interface elements pictured in the photo above: the new pressure-sensitive screen, the much-fetishized Digital Crown, and, simply, the Button. While much has been written recently about the attention Apple is paying to the fashion-related aspects of the Apple Watch (e.g., luxury options, extensive customization compared to previous products), perhaps the obviousness and must-haveness of the device will emerge in its everyday use, where routine things will get done faster and information will be transmitted with less friction and without the encumbrances of even the most modern of smartphone interactions. And that is to say nothing of the integration of Apple’s Siri personal assistant and speech recognition tech, which Tim Cook boasts using “all the time”. Will Apple Watch be Siri’s debutante coming-of-age?
One thing is certain: as my father-in-law reminded me tonight, given Apple’s recent history, it would be foolhardy to categorically dismiss anything they aspire to do with the Apple Watch. For perhaps the first time in the company’s history, it seems Apple has earned the benefit of the doubt.