Release Candidate One with Chris Clark

Goodbye, Steve

I don’t think I, or anybody in our little Apple-orbiting community of designers, engineers, and journalists can overstate how much of an impact this one man has had on our lives. Steve Jobs wasn’t merely a man, he was a phenomenon, and he’ll be terribly missed.

The thing that makes me saddest about his absence going forward is knowing that every time we quote him, every time we invoke his name, it’ll be in posthumous reference. Like quoting Gandhi or Martin Luther King Jr, or any of the misfitting, troublemaking, beautiful souls in Think Different, we won’t be quoting a titan whose taste and work ethic and personality still drive an industry. We won’t be quoting him like we might still have to face him backstage at WWDC and pretend not to be shitting our pants. Going forward, every time we mention Steve Jobs we’ll be remembering a great man passed. I hope his legacy never fades.

His approach to life, his approach to building things the world can fall in love with, is timeless.

iOS 5 Notification Center Fall Down Transition

Max Rudberg

This mockup from Max Rudberg is right on the money. My first thought when I saw iOS 5’s notification shade with its linen texture was that linen is supposed to be under the UI. It’s the multitasking drawer, the springboard folder, the flipside of the weather app, the surface behind your page in iWork. Notification Center puts linen atop the UI in a direct lift of Android’s UI. Rudberg’s approach here isn’t just more consistent with iOS conventions than the official one, but is also more novel and interesting to use.

The whim of Jobs is a strange thing.

System Level Tweet Composer

Apple provides some great APIs for integrating with the system utilities, but they’re slow moving. There’s no standard MFTweetComposeViewController, and there probably never will be.

Yours Truly

Well shit.

Designed For Use

Lukas Mathis has at long last written a book. Lukas is one of those people whose blogs I’d encourage you to read instead of this one if you really had to pick, but thankfully you don’t and we can stay friends.

His book is called Designed For Use and I can assure you it’s worth a look. I say this as a man with a perennially half-read copy of About Face on his nightstand and a low tolerance for dry prose. Instructional design books tread a fine line between compelling reading and academic bore. Designed For Use delivers the goods with accessible writing and content that is broadly applicable.

Wi-Fi Sync

Literally the only thing the icons have in common is that they combine the two symbols for ‘sync’ and ‘Wi-Fi’, oddly enough, that Apple has been using for years

Jesper

This is why I love Jesper. Why aren’t the Register whacking jailbreak developer Greg Hughes over the head for stealing Apple’s Wi-Fi and sync icons? Or for, like, breaking his developer agreement by using private API and then selling the product on the Cydia store? There’s no justice for Goliaths anymore.

Personal, Relevant, Connected

Mike Kruzeniski

An interesting peek into the thought process behind Windows Phone 7. There’s a fun slide seven minutes in, complaining that the average application on competing platforms is used only once, and that only 1% of downloaded apps are used regularly in the long run.

99% of apps are forgotten in the long run because 99% of apps are crap, and it costs you very little in time or money to install them. It’s a lofty goal for Windows Phone 7 that the majority of its apps should be universally useful and long-cherished by all who touch them, but I’m a little flabbergasted that Microsoft believes it can foil Sturgeon’s Law with a slogan and a design aesthetic.

My Month With the Nexus S

I’ve been using a Samsung Nexus S as my full time phone for just over a month now, out of a sense of professional obligation and some idle curiosity. Working with iOS and iOS alone for so long, I can’t help but feel a little sheltered from the world of competing platforms. Android’s out there, and there’s only so much you can learn from the media without experiencing it for yourself.

If the Nexus S were my first smartphone, having used only candybar feature phones before it, I’d probably love it. It’s an Internet-connected computer in your pocket… what’s not to love? I’ve sent hundreds of SMS messages, browsed the web, made phone calls, played Words With Friends, refreshed Twitter, listened to podcasts, navigated the road, and used it as my morning alarm clock: the Nexus S does everything one could reasonably expect of a smartphone, and does it competently. The high note? The camera feels amazingly fast. Eschewing any kind of startup animation, the screen is black for a short moment and then… you can take a photo. That shouldn’t be an astounding revelation, but it is.

And Android’s text cursor does something wonderful: you tap where you want to type, and after the cursor appears you get a drag-handle to fine tune its position. Compared to the iPhone where you must tap, hold for half a second, watch a magnifying loupe appear, then drag the cursor around, the instant gratification of see-it-grab-it-drag-it is a joy. It’s a little thing, but given how much writing I do on my iPhone and iPad it makes a tremendous difference. Manipulating larger selections of text isn’t as pleasant. On iOS you double-tap a word and it’s selected, revealing two drag-handles for adjusting the selection; Android makes you tap and hold for half a second, opening a menu from which you must tap Select Word, which selects the word and provides drag handles for adjustment. I can’t tell you how much I dislike having to tap, hold, and wait that half-second for something I do as frequently as editing text, and it’s funny that both operating systems are guilty of the same thing. I wish they’d both change their behavior.

Any iPhone refugee’s impression of Android wouldn’t be complete without mentioning the system-wide notification drawer. Sebastiaan de With’s roundup is accurate and goes into more depth than I will, but suffice to say that while the contents of, interaction with, appearance of, and animation of said drawer all need improvement, it’s a mile ahead of the iPhone’s interruptive notification dialogs. There’s maybe no example more telling than the Available WiFi notification on each platform. I disabled WiFi alerts on my iPhone years ago and never re-enabled them: they’re intrusive and I usually don’t want to join the networks they advertise. On Android, it simply doesn’t matter if there’s one more badge in the status bar for available networks; it’s no sweat.

But a fast camera, unobtrusive notification drawer, and easy-drag text cursor are about where the favorable comparisons end. I can’t say anything nice about the touch-sensitive hardware buttons, whose unpredictable behavior is a source of frustration and wasted time, and despite the boastfulness of Android hardware vendors about memory and processor specs, the Nexus S just feels slow. This device is a good six or seven months newer than the iPhone 4, so I assume it should outperform the iPhone 4 in any kind of bare-metal benchmark, but in the real world with the default operating system it barely competes with an iPhone 3G. Animation in general runs at half the frame rate you’d expect, and scrolling (a common complaint against older Android phones, if I recall) doesn’t lag on the Nexus S so much as it looks like it’s dropping frames. Kudos to Google for solving the widespread complaints of jerky, unresponsive scrolling, but there’s still a long way to go.

Not helping my impression of slowness is the slow web browsing, but I guess that’s my own fault: I turned off WiFi to preserve battery life. Still, I expect when tapping a link in a web page (or tapping a bookmark) for there to be some immediate indication of progress. When nothing happens, nothing at all in the page or the browser chrome for several seconds, my confidence in the system is eroded.

Of course if battery life weren’t such a concern I’d keep WiFi enabled, but despite the Internet’s suggestion of turning it off along with Bluetooth and GPS, turning screen brightness to the minimum, and keeping a widget on my home screen to quit all background processes with a single tap, it takes only a little fun to drain the battery. Playing a game, listening to music… it seems anything out of the ordinary is cause for massive battery drain, despite the operating system’s insistence that cell standby and the display are the chief culprits. If I abstain from music and disable all the aforementioned hardware features, the phone lasts a whole day, but it’s ridiculous that I should have to. Every missing minute is obviously “my fault” because I’m the person wielding the phone, but when identical behavior on a competing platform produces dramatically different battery life, I find it hard to blame myself. The end result is that I walk away with a worse impression of Android and of the Nexus S than I perhaps should. Add “generally not useful as a pocket computer because there’s not enough battery to last the day” to a long list of little complaints about the system’s usability, and the Nexus S loses the smarts and becomes “just a phone.”

I said at the start that if the Nexus S were my first-ever smartphone I’d probably love it. But since it wasn’t my first, I come to it (and maybe more importantly to the operating system) with expectations of performance, stability, battery life, and general attention to detail that it just can’t meet. Sure, it comes with a whole host of freedoms that I can exercise, like installing a third-party keyboard component to replace the system keyboard, but I didn’t exercise those freedoms because I don’t care, I’m just not that guy. I never themed my Windows installations, never jailbroke my iPhone, never turbocharged my car. I want a phoneputer that just works and lets me pursue my own goals; goals that don’t include being a sysadmin. The Nexus S does everything one could reasonably expect of a smartphone, and it does them competently, but if you’ve experienced a smartphone that does those things exceptionally, mere competence is a big step backward.

Business, Design, and Engineering

The point of native apps is to provide a better experience than websites can offer. Watching a splash screen rotate a ‘Loading…’ spinner for 80 seconds isn’t it.

John Gruber

Performance is probably the most important part of user experience, but rarely talked about in design circles because designers can’t take credit for doing it. Performance is entirely in the hands of engineering and infrastructure teams.

That’s probably why Google has always been so good at it, and why people so happily overlook Google’s flaws every single day: it’s fast and it gets the job done. Given a choice between something fast but plain and something shiny but noticeably slower, fast usually wins; good performance is good user experience, and Google was always faster.

If you remember when Tweetie first came out, a relatively plain and native-looking iPhone Twitter client, it scrolled like nipples on butter when every other third-party iPhone app in the world scrolled like nipples on asphalt. Regardless of Tweetie and primary competitor Twitterrific’s appearance and respective feature sets at the time, Tweetie was impressive just because it felt fast.

Much has been said about The Daily’s general slowness. From chunky paging to long waits on the download, and the criticism is fair. But it highlights an issue that I only feel at ease talking about now that I no longer work for an iOS contracting company, and that’s the relationship between business, design, and engineering.

On great software teams—and I include the web in this, not just compiled native software—the three are in sync. But there are a great number of businesses in the world that don’t care about software and probably never will. Media companies, food and drink companies, cigarette companies: they love their core business, and they’re good at their core business, but the world is telling them they need an app. So they hire contractors, and that’s where things can get messy… because business isn’t always in the same boat as design and engineering.

Contractors aren’t bad. Contractors are usually sharp-shooters of incredible talent who have to bounce from project to project, never settling into a Primary Skill Set because every project calls for something different. But contractors aren’t in charge of the product the way they are when they write their own software: the client is. Contractors will take as much pride in their work as they can because they don’t want to be known for shipping anything bad, but they’ll always be overruled by The Money.

Clients are The Money, and they rarely acknowledge the importance of performance or even subtler design nuances, because they don’t know software. All The Money wants to know is whether the project is On Brand and whether it has Every Feature In The World. And that’s the problem. Every project has a deadline, every project has a budget, and nobody wants to spend half the budget making sure the product is bug-free and high-performance—to them that looks an awful lot like wastefulness—when they could spend their budget on features they can see.

This doesn’t describe every contract gig. I’ve dealt with some great clients who have great taste and want to make something great for their customers. And that’s great. But there are plenty that aren’t great, and that’s not great for anybody.

I don’t have any insider knowledge on what happened at The Daily, I’m not even completely certain who designed it or developed it, but when we talk about final cut, when we talk about who decides what ships and what needs work, when we talk about prioritizing the tasks of software development under a deadline: the person who signs the checks at a billion dollar news company whose head of marketing said “we need to get on this iPhone App bandwagon” isn’t the right person to make those calls. Steve Jobs is so revered because he knows how to run a business and he has the taste and self-respect to not ship things until they’re ready. Most companies don’t. Most companies are beholden to arbitrary deadlines, and make crummy trade-offs to meet those deadlines. But that’s why most companies aren’t as beloved as Apple and Pixar. Most companies are in the business of selling shit because it’s profitable.

Interview: Marco Arment

Writing about a subject helps clarify, mature, and sometimes even change my opinion on a topic.

Marco Arment

You wouldn’t believe how many things I’ve started writing, and three hours later shitcanned because I’ve realized how wrong I was. If you have a private opinion, consider it void until you have to justify it to the world. Then again, if you’re truly stubborn this advice may be lost on you.

“Live in doubt” is the best advice I can offer anyone with a creative impulse. Save the blind confidence for when you’re wearing your Sales hat.

Last Day

Black Pixel is a company I helped found and have been proud to call home for two years now, as we worked our asses off to turn it into one of the premier iOS development squads in the world. We’ve built everything from children’s games to business tools to storefronts to streaming entertainment apps for some of the country’s biggest brands, and chances are you’ve used one of our apps and not known the months we poured into it. It’s been a helluva ride, but all rides end; today is my last day among the Pixels.

I’ll be joining Square, Inc. here in San Francisco just as soon as I’m done tackling this mountain of visa paperwork. It’ll be an opportunity to focus on just one service, just one product. One of the great strengths of working as a gun for hire is the incredible variety of problems to tackle, the experience of working so many deadlines for so many clients, and the broad set of skills it encourages you to develop. But I’m looking forward to focusing on some small but interesting problems at Square, and focusing hard. It’s a company to watch, and I’m excited to be coming aboard.