My reading workflow on the iPhone

Instapaper for iPhone is a simple concept, but simply beautifully executed. It is a joy to use.

It is where I spend most of my reading time on the iPhone.

So it made sense to think about how I use the application, what my reading workflow is on the iPhone. And here’s what it looks like:

I send articles and pages to Instapaper via one of
1. emailing the link to my private Instapaper email address
2. using the ‘send to Instapaper’ menu item in several iPhone apps
3. using the ‘send to Instapaper’ bookmarklet on my PC browser

Email to Instapaper is a fantastic idea. There is just so much that I browse on Mobile Safari and don’t want to read immediately. This includes links from Twitter that I open, scan and email. I doubt I’d use Instapaper as much if I couldn’t email articles to it. [1]

And I share articles I like to Twitter from within Instapaper. The app automatically appends a short URL to the article at the end of the tweet. So far, I’ve sent around 50 articles to Twitter from Instapaper.

[1] Yes, there’s the Mobile Safari bookmarklet, but it’s inconvenient to set up; I’ve never gotten around to it. Emailing is so much easier.

Phone manufacturers != manufacturers of phones

Podcasts have changed my commute since I got the iPhone. I’ve discovered NPR’s This American Life and Fresh Air, BBC’s Excess Baggage and Click, Gruber’s and Dan Benjamin’s The Talk Show and the NYT’s Times Talks and Bits. All of them free in the iTunes store.

Even though all of these were available for free download as MP3s, and I knew (most) existed, I never listened to them on my previous phones.

I recall subscribing to a bunch of NYT podcasts on my Nokia. Checking and downloading five MP3s in parallel, creating a desktop folder each week, copying it to my phone memory card and deleting last week’s folder, refreshing and waiting ten+ minutes while the music player scanned the SD card and detected the new episodes (and identified them as songs, not podcasts), and having to painstakingly navigate to where I had left off a podcast if I wanted to resume. It was a pain and I soon gave up.

The iTunes-iPhone integration makes all the difference. iTunes has nailed catalog and content, discovery, subscription and billing. It has nailed auto-download from the Internet. It has nailed silent and automatic sync with iPhone. It has nailed keeping only the most recent n episodes on-device. And iPhone remembers where I left off, per podcast.

And so then here’s what happens: during the day, the iPhone is plugged in to USB, charging. iTunes is downloading the latest episodes of my subscriptions and syncing with iPhone. Once I subscribe I don’t have to do a thing, ever. New episodes are just *there*.

But iPods have been able to do this for about a decade now. And iPhone for nearly four years. No other phone is able to manage music – and playlists and podcasts and videos and photos and contacts and bookmarks and, yes, apps – anywhere as well. You just have to say the others have been lazy.

Or I guess if phone manufacturers still consider themselves to be that – manufacturers of phones – then they’re missing a lot.

About the smartphone category called iPhone-like

From an email exchange with a friend asking about the Nexus One (the ‘Google phone’) launch.

Thoughts about the Nexus One’s prospects

Does it have better hardware, a better screen, better battery life, better price, more freedom, better apps, better multitasking, better camera than the iPhone? Yes. Is it the iPhone? No.

People who’ll buy the Nexus One say they want to buy something like the iPhone that isn’t the iPhone, and they’re lying even though they don’t know it. They want the iPhone because it’s the iPhone. And nothing else. When you create in your mind a category called iPhone-like, there’s only one member that’s ever going to be a full, incontrovertible member of that category.

These buyers are going to be disappointed even though they won’t know quite why. They’ll blame it on the phone instead of their own expectations, and demand won’t spike the way it did for the iPhone.

Would I buy it?

I don’t like the iPhone, but I like this current crop of Android devices even less. If, in a (thankfully) fictional dystopian universe I had to choose only between the iPhone and the Nexus, I’d take Apple’s baby (and lament long and hard about the lack of alternatives).

Reason #3: form factor wise no Android device has nailed the iPhone. This is HTC and Motorola and Samsung, not Apple we’re talking about. So there. These firms are known for specs, not sex.

Reason #2: I will not buy a phone with a trackball. Ever. Would you buy a Skoda that featured a manually-operated crank to start the engine? Heck, even Blackberrys have moved on.

Reason #1: Polish. I posit that no one has been able to nail the touchscreen experience other than Apple. Not Palm, Not Android. Not (shudder) RIM and most certainly not Microsoft. Since 2007, for instance, Android phones have been underpowered and have had user experience (UX) issues where the phone hasn’t been able to keep up with text or touch input. Now three years later,

Some animations are very smooth, some are janky as hell. The Nexus One has a faster processor than the iPhone 3GS and has twice the RAM, and yet it still cannot have as fluid a UI as the iPhone OS. This is great proof that your software is key—throwing raw power at things won’t necessarily make them better.

And it doesn’t even have to run Android. Every touchscreen phone apart from iPhone suffers from this.

I think it’s worth demonstrating how Apple nails the experience with an example.

In Mobile Safari, the iPhone browser, if you scroll (swipe) too fast, instead of text you’ll see a chequered pattern – the processor can’t render the text fast enough – but the scrolling experience itself is smooth as ever. Once you stop scrolling, text will eventually appear. On any other mobile browser, the scrolling itself will stutter as the processor tries to render everything.

When you’re using a device all day every day as essentially an extension of your body and mind, stuff like this matters more than features.

I’d pick the iPhone. As, sadly, will folks who upgrade from the Nexus One eventually.

Update (10 Jan 2010): Another example of polish in design:

Other issues that I can’t live with day to day? How do I copy text from non-editable field like an email, webpage, or SMS, or even a 3rd party application? Oh, I can’t. Say what you want about the iPhone not having copy and paste for two years — a joke — it’s the single best implementation on the planet for a smartphone and Google’s approach is almost as bad as RIM’s with the Storm-series.

(From Boy Genius Report, via John Gruber)