Applications

iPad as the new Flash

Jeffrey Zeldman compares the trend for creating novelty interfaces in publication apps to the bad old days when Flash spawned a million bad interface designs. He also succinctly picks up on an important point as to why web standards are so important:

Everything we’ve learned in the past decade about preferring open standards to proprietary platforms and user-focused interfaces to masturbatory ones is forgotten as designers and publishers once again scramble to create novelty interfaces no one but them cares about.

While some of this will lead to useful innovation, particularly in the area of gestural interfaces, that same innovation can just as readily be accomplished on websites built with HTML, CSS, and JavaScript—and the advantage of creating websites instead of iPad apps is that websites work for everyone, on browsers and devices at all price points. That, after all, is the point of the web. It’s the point of web standards and progressive enhancement.

There’s also some really good discussion to be found in the comments. But Zeldman nails the case for why this kind of stuff makes bad business sense for magazine publishers:

Unless your organization’s business model includes turning a profit by hiring redundant, competing teams, “Write once, publish everywhere” makes more economic sense than “Write once, publish to iPad. Write again, publish to Kindle. Write again, publish to some other device.”

WIRED on iPad

I’d missed this first time around: Oliver Reichenstein wrote a thorough, in-depth analysis of the typographic problems with the WIRED iPad app:

First, the paper magazine was crammed into the little iPad frame. In form of a PNG slide show. To compensate for the lack of interactive logic, this pretty package was provided with a fruity navigation. In the end it was spiced with in-app links, plucked with a couple of movies and salted with audio files (“interactive”). Then it was off to marketing. And it sold 24,000 copies. Dammit. It’s the Nineties all over again.

He makes some really potent points about the differences between designing readable publications for print and screen: the folly of column layouts, careful use of gutters, the impact of too much ornamentation. He presents some very subtle examples, but that is the strength of his reasoning: it’s the subtleties of designing for different digital devices which are most important; the devil is, indeed, in the details. Porting a print design directly to digital reading devices like the iPad isn’t good enough.

We should use original tools to create iPad apps, not because Steve Jobs said so, but because these tools create products with flesh and bone, that is: an understanding of both the purpose, the potential and the limits of the iPad technology.

The problem with magazines on the iPad

Peter Kafka writes about the problems with bulky magazine apps:

The Wired iPad app has a weight problem.

The first one came in at about half a gigabyte of memory, and it hasn’t shrunk that much since.

And Condé Nast’s newest iPad app, from the New Yorker, isn’t much better: It takes up 173 megabytes–but that’s for a weekly issue. If Condé can’t slim the app down, a month’s worth of New Yorkers will be much heavier than the first monthly Wired app.

Appears that this weight problem is down to their use of some horrible image-based reader software:

Both the New Yorker and Wired have the same weight problem for the same reason: They are built on the back of an Adobe (ADBE) program that essentially functions as an image reader.

That is, each page of the magazine is turned into the equivalent of several big photos. Which means an image-rich layout at Wired or a page of text at the New Yorker both consume a lot of memory.

Aside from the horribly inappropriate use of technology (displaying text as images is just dumb and inefficient), this is a horrible accessibility problem: it means that these magazine apps are pretty much unusable for many disabled users.

Once Adobe figures out how to break up HTML text into individual pages, McCarthy will make the switch, she says. Perhaps in a month.

There’s really no need to use HTML. And there’s really no need to have to compromise and use text scrolling. There’s a technology which allows for portable reading of rich media content, whilst maintaining precision layouts, and even maintains accessibility. It’s been around for a while.

It’s called PDF. It’s an open format, and it was created by Adobe. Duh.

Twitter.com or a Twitter App?

Matt Buchanan at Gizmodo comparing the new Twitter.com to a native application:

The new Twitter feels a lot like an application, slapped on top of Twitter.com. That’s partly because it’s built like an application. It uses the same Twitter API that any third-party app does. The two-pane split view recalls the iPad Twitter app, and the design intent is largely the same: to keep you on Twitter.com while you’re consuming the content the people you follow are tweeting. The right pane is like an activity panel. It expands out to show conversations between users, photos, videos, profile info, location and more. And the whole thing flows insanely smoothly and dynamically, like an app. There’s infinite scrolling, so tweets keep coming as you scroll down. When you click the arrow to expand a tweet into the right panel, it shoots out like a card. There’s even keyboard shortcuts and autocomplete like a real app (or Gmail, another exemplary web app).

“ū—”: A Distraction-Free Writing Environment

Cheeky but fun little parody by Merlin Mann of the Writer app which I mentioned yesterday:

We call this workhorse “ū—” in tribute to an untranslatable Inuit word meaning, “the moment when Family Leader finds himself sweeping yak hair from the [ice-covered lean-to] while his angry wife screams heavily-distracting criticism of Family Leader’s time use.” Since it’s untranslatable and we don’t speak a word of Inuit, we’re not sure what that word would be. But, we definitely thought “ū—” sounded cool and a little Eskimoey.

Also, we had to come up with a name that wasn’t already on the App store. So.

Writer for iPad

This new writing application for the iPad from Information Architects is pure elegance. Hardly surprising considering the well-thought philosophy behind it:

Professional Typography is not just pretty to look at. It facilitates the process of reading. If you look at text as an interface, typography is its usability. Common text editors are typographically weak (small font, tight leading, random measure, lack of whitespace). In addition, few people have the professional skills to design digital text. In Writer, font type, text size, column width, leading and contrast are carefully set for the best reading experience both in portrait and landscape mode.

I’ve been finding it difficult to find a reason to invest in a first-generation iPad, but it’s beautiful apps like this which might just sway me. The thoroughness of their branding nails it:

The period at the end of the logo reflects the main virtue of the application: It pushes you to get to the point.

Motorola acquires 280 North. But why?

280 North wowed people with the creation of their web application framework Cappuccino, which is built on an impressive new programming language, Objective-J. The whole framework is modelled on desktop development with Objective-C for Mac OS X, and it can do some pretty amazing stuff – it’s like Cocoa but for the web.

Techcrunch report that 280 North has been acquired by Motorola for a whopping $20 million, quoting a Motorola spokesperson:

“I can confirm that Motorola acquired 280 North earlier this summer. The transaction provides Motorola with specialized web-app engineering talent and technology that will help facilitate the continued expansion of Motorola’s application ecosystem. We believe 280 North will be instrumental in helping us continue to foster the Android ecosystem with innovative web-based technologies and applications.”

I really don’t understand the logic behind this acquisition, and suspect it could mean the end of the great open-source work that 280 North have done.

  1. Motorola are committed to developing for the Android platform, so why acquire technology which is so intrinsically tied to the Mac platform? Objective-J is essentially a webified version of Objective-C; the look-and-feel of Cappuccino’s UI elements are based on the Mac UI, and the development tools feel just like Mac apps.
  2. Cappuccino’s aim was to bring the ease of developing desktop applications to the web: it’s about creating web applications which feel like desktop applications. Motorola have very firmly positioned themselves in the mobile market, so why the interest in web applications which feel like desktop applications? Even if they are branching out into the development of tablet devices for the home, surely it makes sense to develop technology for a touch UI? Touch is not what Cappuccino is about – Sproutcore is way ahead of the game in this area.

I’m ready to be proven wrong, but this seems like a knee-jerk acquisition. This isn’t about acquiring 280 North as a viable company, or Cappuccino as a platform for further development – it’s about acquiring the clever brains behind this web app framework for Motorola’s bespoke purposes. It’s right there in that Motorola statement: “the transaction provides Motorola with specialized web-app engineering talent”.