AT HOME, sick with a cold and bored, my daughter buys a single packet of “My School Dance” in a freemium iTunes game. The manufacturer charges her (well, charges me) for ten packets. This same “accidental” 10x overcharge happens across three different games by the same manufacturer in the span of about an hour.
American Express notifies me of the spurious charges, but won’t let me dispute them until they are “posted.” I spend half an hour on the phone with a very nice gentleman at Amex learning this. Why would Amex notify customers about a charge days before they can do anything to resolve it? I don’t know. And I don’t ask the gentleman on the phone. His job is hard enough.
A few days pass. Amex “posts” the false charges and emails me with a link to resolve the problem on Amex’s “dispute a charge” web service.
Amex’s “dispute a charge” web service “encounters an error” when I try to use it to resolve the problem.
This happens every time I try. I try for three days.
So I call Amex, but I can’t resolve the problem because I don’t have the card in my wallet.
So I head to iTunes, where I should have gone in the first place, and click through two or three generations of iTunes “Report a Problem” interfaces: visually different generations of iTunes software, with different user paths, all still being served by Apple. Generations of iTunes software that, when they fail, link to other generations of iTunes software, which also fail.
I click and click my way through five years of iTunes interfaces.
Finally I find an iTunes page where I can manually “Report a problem” for each of the 27 false charges. (Three of the charges, remember, were legitimate. I’m willing to pay for the three items my daughter intended to buy. But not 30.)
If one software product overcharges your kid by a multiple of 10, that could be a software bug. When three products from the same manufacturer all do it, that’s not a bug, it’s a deliberate attempt to defraud families, by overcharging on purpose and hiding behind the opacity of iTunes’s purchase reporting. Simply put, the manufacturer is dishonest, and figures iTunes’s support section is impenetrable enough that you’ll eventually give up trying to get a refund.
But they didn’t count on my tenacity. I’m the Indiana Jones of this motherfucker. I have studied maps and bribed natives and found my way to the hidden iTunes refund page that actually, sometimes, works.
On this page, I inform Apple of the fraud 27 times, in 27 different boxes. Each time, after reporting, I click a blue button, which generally returns an error message that iTunes was unable to process my request. So I enter the data and click the button again. It’s only 27 boxes of shit. I’ve got all the time in the world.
The page tells me that only two refunds went through. Every other request ends with an error message saying iTunes could not process my request, and encouraging me to try again later.
Instead, I leave the page open, and, about ten minutes later, I manually reload it. When I do so, the display updates—I guess this generation of iTunes software preceded “Ajax”—and I learn that most of my refunds have gone through.
So the software actually works about 33% of the time, even though it indicates that it only works 5% of the time. Remember that wait-ten-minutes-then-randomly-reload-to-see-if-anything-changed trick. It’s the sign of excellently designed consumer software.
I’ve put over two hours of my time into this. Going on billable hours, I’ve probably lost money, even if I get all my overcharges refunded. But there’s a principle here. Several principles, actually. Tricking kids is wrong. Stealing is wrong. Building a beautiful front-end but neglecting customer service is wrong. Mainly, I’ve just had enough of 2016’s bullshit.
[I]n El Capitan B4, Apple decided to stop shipping Procmail, and with it, lockfile. It wasn’t deprecated and then removed… it was unceremoniously sent to the bit bucket. So, as of B4, scheduling in El Capitan broke.
REBUILDING iTunes library from scratch over two days got app working again. Fine use of lazy weekend.
Had to sacrifice all custom playlists dating back to 2002, including An Event Apart playlists and delivery room mix from Ava’s birth.
Playlists still exist on old iPod but can’t be copied from it back to iTunes. (All software I’ve tried freezes & fails.)
Playlists still exist as code snippets inside .itl file in old iTunes folder, but numerous trials prove iTunes can’t launch from that folder any more. Thus I can’t temporarily launch from old folder, export playlists, switch back to safe new folder, and import them, thereby saving them.
And iTunes can’t import old .itl files. I Googled. I tried anyway.
13 years of custom playlists. From before, during, and after my marriage. Including one my daughter called “princess music” and danced to when she was three. Gone.
But, really, so what? Over time we lose everything. This loss is nothing. Attachment is futile. Always move forward, until you stop moving.
SOMETIME in the night, maybe around 4:00 AM, my new iPhone, which is my only alarm clock, and which was plugged into the wall and fully charged, powered itself down and went black. Maybe it just happened. Maybe Snow White, my restless night ghost cat, accidentally triggered the shutdown by stepping daintily on the phone.
Sometime in the night, maybe around 4:00 AM, I woke up. I’m no longer in the habit of waking in the middle of the night, and I don’t know what made me do it this morning. Maybe it was Snow White, silently walking on my chest, and fleeing just before her action produced the desired result of waking me, so that I thought I woke on my own. Maybe it was a preternatural connection between my central nervous system and the iPhone—like something out of Cronenberg—responding to the phone’s silent shutdown. (Wake up! I’ve died! the iPhone cried.)
Or maybe it was the anxieties of the day before catching up with me. A hugely important business meeting yesterday, yada yada. Something odd and unsettling my daughter’s teacher had said in school the day before (if my daughter’s report of what happened was accurate). An argument my daughter had yesterday with her best friend, and her conviction (voiced to me only) that they were drifting apart forever. Or maybe I just drank too much water before going to sleep. Whatever the cause, I lay there awake. And lay there. Giovanni, the tuxedo cat, on my arm. Snow White, who sleeps in my daughter’s room, suddenly in my room, standing on my chest.
After about an hour of anxious thoughts and idle fur stroking, I reached for the phone to see what time it was. And that’s how I discovered that the device was strangely cold, except around the lightning port, which felt unnaturally hot. The screen was black. My button pushing, which began desultorily and grew ever more urgent, had no effect. The device would not come on. It was cold. Off. Maybe dead!
And suddenly I was out of bed, because that’s what happens when your mobile device stops working. You spring into action like a firefighter at a burning building. Flicking on living room lights, brewing a Nespresso (sorry), plugging things in, pushing buttons with the methodical calm of an ER surgeon.
Never fear, O my friends of the internet, the device came back to life. Yes.
What’s strange is that, if I hadn’t woken up early, I would have slept right through, because the alarm would not have gone off, and without it (for instance on Saturdays) I sleep in hard.
And if I had slept right through, I would have missed my daughter’s “publishing party” at school today (that’s what the school calls it when the kids read stories aloud that they have written), and she would have been late to school one too many times this year. I would also have missed my appointment at the Apple store in Grand Central—the first Apple store appointment I’ve made in years, to fix an iPad Mini which mysteriously stopped taking a charge two weeks ago and is now, essentially, a large, awkward guitar pick.
Is my phone jealous of my iPad? Did it shut down so I’d sleep through my appointment at the Apple store?
Did I wake from family worries? Business concerns?
YOUR site may soon be collateral damage in a war between Silicon Valley superpowers. By including ad blocking in iOS9, Apple isn’t trying to take down your site or mine—just like the drone program doesn’t deliberately target civilians and children. Apple is trying to hurt arch-rival Google while providing a more elegant (i.e. more Apple-like) web experience than user-hostile ad networks have previously allowed. This is a great example of acting in your own self-interest, yet smelling like a rose. Will independent sites that depend on advertising be hurt along with Google?
We have always been at war with Eastasia
We should be used to this war between digital super companies by now. iPhone and iPad users, consider your Amazon experience on the platform. Notice how you can’t buy books in your Kindle app in iOS? Apple supports Amazon to the extent of letting Amazon distribute Kindle software on the iOS platform. But if you want to buy a Kindle book for your phone, you have to go to a desktop browser (or open Safari on your phone and navigate to Amazon.com). Kind of encourages you to get your digital books in iBooks instead.
Same with Amazon’s video app on iOS. You can stream all the movies you want on your phone or iPad, but you can’t buy them in the Amazon Video app. You must use a desktop browser or navigate to amazon.com in the version of Safari that comes with iOS. Kind of encourages you to buy videos from iTunes instead.
You also can’t buy Kindle books or streaming Amazon videos in the Amazon shopping app for iOS, although you can use that app to shop for anything else.
See, Amazon doesn’t want to give Apple a cut of its media sales, so Apple won’t let Amazon sell products in its apps. In Apple’s reasoning, all other vendors pay Apple a cut; Amazon shouldn’t get a pass. And Amazon is serious about not sharing revenue, because Amazon is a ruthless competitor that has taken over nearly all online retail sales in the U.S. by innovating service and delivery, and giving consumers the lowest possible price—a price that leaves them no margin to share with Apple. It’s also a price that strangles the companies that provide the goods Amazon sells. Oh, well.
Because Amazon is serious about not sharing sales revenue with Apple, and Apple is serious about blocking sales by any vendor that refuses to share revenue, Apple denies Amazon the right to sell products via its iOS apps. Who suffers? You, the consumer, as you put down your phone and toddle over to a desktop—or just shrug and do without. (Not that it’s the worst suffering in this world. But it is anti-consumer, and makes both Amazon and Apple look bad.)
And, of course, you can’t stream Amazon video on your Apple TV, and likewise can’t watch video content you’ve purchased through Apple iTunes on Amazon Fire TV without jumping through (possibly illegal) hoops. Not since Microsoft dominated the desktop software world in the 1990s have tech and media companies viewed success as a last-man-standing affair, with the consumer as collateral damage.
Still, we’re used to all this and don’t think about it.
Ad blocking is a different beast.
Certainly, at first, ad blocking seems like a different beast. After all, consumers may want to buy books in their Kindle app, but no consumer is clamoring for more ads. And media and advertising have only themselves to blame for the horrendous experience online advertising has become. We hate advertising so much, we’ve trained ourselves not to look at the top or right sidebar on most sites. In fact, it’s become a designer’s trick that if the client forces you to put the CEO’s pet link on the home page, you hide it in plain sight at the top of the sidebar, where no one but the CEO will see it. Popups and screen takeovers and every other kind of anti-user nightmare have made advertising a hated and largely ignored thing on the web.
There are tasteful ad networks, to be sure. The Deck, which Jim Coudal created with Jason Fried and me, serves one single, small, tasteful, well targeted ad per page. When we launched The Deck, I hoped other networks would take inspiration from it, and figure out how to increase engagement while minimizing clutter. I even tried to sell my studio’s media clients on the notion of fewer, better priced, better targeted ads. But of course the ad networks have done the opposite—constantly interrupting content to force misleading, low-interest ads on you.
Hip web consumers have long used third-party ad blockers to unfug the web experience, and great applications like Readability explored alternate content revenue models while boosting type size and removing ad clutter from web content. I served on the Readability advisory board. And I used to go around the world warning designers that if we didn’t figure out a way to create readable, clutter-free layouts for our clients’ sites, apps like Readability would do it for us—putting us out of work, and removing advertising as a revenue stream for media companies. As it happens, in the intervening years, many smart sites have found a way to put content first and emphasize not just legibility but readability in their layouts. The best of those sites—I’m thinking of The New York Times here—have found a way to integrate advertising tastefully in those large-type, content-focused, readability-oriented modern layouts. (Medium.com, of course, does an amazing job with big type and readability, but it doesn’t need to integrate advertising—at least not yet—as it floats on a sea of VC bucks.)
But advertisers don’t want to be ignored, and they are drunk on our data, which is what Google and other large networks are really selling. The ads are almost a by-product; what companies really want to know is what antiperspirant a woman of 25-34 is most likely to purchase after watching House of Cards. Which gets us into issues of privacy and spying and government intrusion and don’t ask.
And in this environment of sites so cluttered with misleading ads they are almost unnavigable, Apple looks heroic, riding to the consumer’s rescue by providing all the content from newspapers without the ads, and by blocking ugly advertising on websites. But if they succeed, will media companies and independent sites survive?
Consumer good vs. consumer good
What Apple’s doing wouldn’t matter as much if consumers were still sitting down at a desktop to get their news and cat gifs. But they’re not. Everyone does everything on mobile. Including browse the web.
Thus in The Verge today, Nilay Patel argues there’s a real risk that, in attacking Google’s revenue stream, Apple may hurt the web itself:
The collateral damage of that war — of Apple going after Google’s revenue platform — is going to include the web, and in particular any small publisher on the web that can’t invest in proprietary platform distribution, native advertising, and the type of media wining-and-dining it takes to secure favorable distribution deals on proprietary platforms. It is going to be a bloodbath of independent media. … Taking money and attention away from the web means that the pace of web innovation will slow to a crawl. —Welcome to hell: Apple vs. Google vs. Facebook and the slow death of the web
John Gruber thinks otherwise, at least for small indie sites like his:
Perhaps I am being smug. But I see the fact that Daring Fireball’s revenue streams should remain unaffected by Safari content-blocking as affirmation that my choices over the last decade have been correct: that I should put my readers’ interests first, and only publish the sort of ads and sponsorships that I myself would want to be served, even if that means leaving (significant) amounts of money on the table along the way. But I take no joy in the fact that a terrific publication like The Awl might be facing hard times. They’re smart; they will adapt.—Because of Apple
In Publishing Versus Performance, I looked at the conflict between advertising and content through the filter of performance. For those who didn’t read it (or don’t remember), I pointed out that most consumer interaction with the web happens on mobile, which means it happens on mobile networks, which, at times at least, may be severely bandwidth-constrained; so performance counts as it hasn’t in years. And while good designers and developers are working like never before to create performant websites, the junk ad networks spew interferes with their good work and slows websites to a crawl. This threatens the future of the web, as consumers will blame the web for poor performance, and stick to apps. But removing those ad networks isn’t an option, I pointed out, since, abhorrent or not, advertising dollars are the engine that drives digital media: no bucks, no content.
Well, now, Apple has decided for us. Removing those ad networks may not be an option, but it’s happening anyway. How will it affect your site?
Apple, like Facebook, has entered into a standoff with the publishing industry and the open, if for-profit, web. And it’s being done under the aegis of design: choose a better reading experience on our curated platform, they offer, or let us clean up that pesky advertising on the open web.
? Is the web under threat? Will Facebook or Apple kill or save journalism? Share your thoughts or your favorite links on the subject. Bonus points for older articles.
IN “HOW DROPBOX Remains Relevant,” Khoi Vinh explains why Dropbox owes much of its success to subtly faceted, user-focused design:
Even in an age when the biggest operating systems in the world actively eschew file hierarchies, Dropbox is thriving—its service matters deeply to countless users. Why? In part it’s because the company works hard at making file hierarchies useful, that they focus on the outcomes of file management and not just on the files and folders.
Absolutely. Dropbox sweats the user experience details as commendably as it masters the considerable engineering challenges required to reliably sync files everywhere a user may need them.
But there’s another reason Dropbox succeeds. And it isn’t despite its emphasis on old-fashioned file hierarchies. It’s because of that emphasis.
? ALTHOUGH Khoi may well be right that “smart passive management of design assets and working files seems inevitable,” I, for one, do not look forward to the day I no longer have direct access to my files and the ability to control where and how they are stored. To my way of thinking, passive management of file assets is okay for screwing around with iPads, where we’re mainly watching TV on Netflix or obsessive-compulsively checking the popularity of our Instagram uploads. But for real work, and even for passionate hobby work (like managing family photos), give me files and folders any day.
Stay with photos a moment. Consider snapshots. For my money, apps like Photos (and, formerly, iPhoto) that “save” me from the “inconvenience” of knowing where my images are do me no favors. Thanks, but no thanks. Let me save photos where I want to save them, not where the system thinks I should save them—typically on a laptop’s rapidly filling solid state hard drive with minimal storage capacity.
Dropbox, with its emphasis on good old-fashioned hierarchies, is superb at automatically saving one original of each photo I take, whether shot with a phone or a fancy camera. No loops, no duplicates, no confusion. In contrast, Photo’s cloud sync options, designed to spare the user the trouble of thinking, always trip me up. Like when, after syncing my phone to my home desktop computer, I tell Photos to delete the photos I’ve just sync’d from my phone. Photos obeys my command, and then instantly restores the photos to my phone from the “cloud.”
Why would a system expect a user who has deleted files to want those files restored a moment later? In what universe of scenarios can that possibly be what the user expects? [Your system may work differently from mine. Your deletes may stick. If so, good on you. You may have checked a different box in a hidden drawer of a preferences dialog, possibly in the app preferences you can set in the app itself, or possibly in the app preferences you set in the phone’s Settings app, or possibly online—say, in iCloud, or possibly in the iCloud settings in the phone’s Settings app. This is simplicity?]
Because my phone and iCloud restore photos as soon as they’re deleted, my Camera Roll is an unwieldly monster—despite my applying common sense, logic, years of design and computer using experience, and hours of conversation with a rapidly dwindling circle of friends—not to mention the hours I’ve spent scouring the web for hints. The whole situation reminds me of an article I saw on the cover of PC World years ago: “Plug ‘n Play: How To Make It Work.” (Hint: If you have to learn how to make it work, it ain’t plug ‘n play. And that’s kind of how I feel about the current state of passive file management.)
? SYSTEMS designed to relieve you of thinking too often end up forcing you to think, and think, and think, without ever solving the problems their supposed simplicity has created for you. How much easier would photo maintenance on my phone be if Photos, like Dropbox, used file hierarchies? I could solve the problem myself in a second, with the click of a checkbox, if only Apple weren’t committed to chasing a future where nobody needs to know anything about how their computer works—and, as a result, some of us have no clue what to do when the computer doesn’t work quite right.
? I UNDERSTAND that these are difficult problems to solve, and that confusion and frustration are the price consumers pay for innovation that may benefit them in the long run, once all the kinks are out. I’m not anti-innovation or anti-Apple.
But I’m a web person. I like files. I like editing a CSS file without necessarily having to edit an HTML file. I like fixing a problem by replacing a corrupted file with a clean one. Maybe I’m set in my ways, but I don’t consider it a hardship to open a folder or replace a file. I wouldn’t be quite as happy with a web where I didn’t “need” to “bother” writing CSS.
In the same way, I like deciding where files go—saving an image for Project A in a Project A folder, a text document for Project B in a Project B folder (and all of it in Dropbox). I’m glad Adobe Lightroom maintains a picture of my photo folder hierarchy in a sidebar of its interface, enabling me to see where my files live, and instantly choose a group of photos by date (instead of, say, scrolling through thousands of files visually). When it’s time to get dressed in the morning, I don’t throw myself into a giant room full of clothes. I pull socks from my sock drawer and shirts from my shirt drawer. I’ve been doing this since I was five years old. It’s not a challenge.
Khoi ends his excellent Dropbox piece thusly:
Maybe we’re all just set in our ways, but people seem at least resigned, and more likely just plain comfortable with managing their files. It may not be what future workflows are built around, but for working designers, the future is hypothetical, and Dropbox works today.
To which I say Amen. And add the hope that, so long as my career lasts, I can keep using a workflow I find easy and comprehensible.
“Don’t make me think.” Absolutely. But, equally, don’t treat me like an idiot. Folders über alles.
MAC USERS, if you’ve experienced occasional (but not infrequent) network dropout problems since upgrading to Yosemite, this article in Ars Technica explains why, and tells how to fix it … if you dare.
I most definitely do not dare—following the suggestion could introduce system failure and security bugs when future updates come along—but the piece makes interesting reading, both from an “I’m a nerd and want to know how things work” point of view, and also in light of recent criticism by Marco Arment and others concerning Apple’s quality control.
“HOMELESS FOLK sleeping in front of the SoHo Apple Store. What a perfect commentary on our society,” I thought. Then I realized these aren’t the homeless. They’re upwardly mobile consumers vying to be the first to buy a new model iPhone when the store opens in the morning.
I HAVEN’T GRIPED about a run of bad luck with Apple products for some time, because I haven’t experienced such a run in years. So I was due. So pretty much all the Apple products I own are now malfunctioning, each in its own special way—a way that interacts cunningly with the malfunction in another Apple product I own to prevent me from, say, accessing internet content, or getting photos out of my camera and onto a device where I can view and edit them.
The interlocking details of these curiously synchronous malfunctions are of little general interest, but the cultural assumptions surrounding their discussion may merit some small call on your attention.
People used to talk about the Zeldman Curse, meaning things went wrong with my Apple software or hardware that didn’t go wrong with anyone else’s. But that was never true, of course. Google any problem I wrote about back then, and you’d find lots of other people having the same problem, usually quietly, on an out-of-the-way Apple message board, which only rarely contained an actual, working solution.
Media-wise, Apple was always mum on these subjects—the one exception being 2010’s notorious iPhone 4 antenna problem which supposedly doomed Apple and the iPhone and of course did neither because it wasn’t really a big problem and it was easy to fix.
But those other things that sometimes went wildly wrong for some users of some Apple products? Those things, nice people didn’t talk about. As a community, Apple fans were Victorians when it came to malfunctions of the hardware or software body, and those who complained—like Victorians seeking sexual information—were to be shunned.
This ban on complaint never stopped me because my filters are different from yours, and because I needed the psychological release that came with writing more than I needed your approval.
The real meaning of Apple design
Now, we all know Apple is smart. Their sales pitch is design, but not in the “pretty” sense people who don’t know what design is think I mean when I say the word “design.”
Their stuff is pretty, but that surface prettiness is merely an objective correlative—an indicator, if you will—for the beauty and emotional satisfaction of a generally seamless computing experience. It’s the comparative ease of creating and managing a music library, not the attractiveness of the surrounding chrome, that makes people connect personally with iTunes. Like the best websites, Apple products anticipate what you will need to do, and make it easy for you to do it, thereby enabling you to focus your attention on the content with which you are engaged, instead of on the interface that facilitates your interaction. Interaction design. Experience design. That’s what Apple is brilliant at.
And even when the hardware is visually gorgeous—like the MacBook Air, my road machine as a frequent speaker—the real selling point isn’t that visual beauty; it’s the fact that this powerful computer weighs little more than a pad of paper. You can toss it in your handbag or backpack and run out the door. That whole deskbound computing experience? The Air freed you from it even before the iPad came along.
Ingenious
If a brand’s whole essence is bound up with good experience, it makes sense for the brand to handle bad experiences quietly and with skill. This Apple does in its stores. If something goes wrong with a piece of hardware, or if an individual piece of software is malfunctioning in ways you can’t fix after fifteen minutes with the Googles, you walk into the Apple store, and a smiling initiate fixes the software for you, or replaces your bum iPhone with a free new one. Walking out with a free new iPhone kind of makes you forget that you were angry at Apple for the problems of the iPhone you walked in with.
The house that Jack wired
But you can’t lug your apartment or your whole network routing setup to the Apple store when your MacBook Air says it can’t connect to the internet because another device is using its IP address (even though no device is). And you can’t plug into ethernet because the Air doesn’t support it. And if you bought that ethernet converter enabling you to plug an ethernet cable into your Air, that’s when you find out that most ethernet cables don’t actually fit into that thing Apple sold you for $50. You can’t bring the Air into the Apple store to be diagnosed and fixed because it connects beautifully to the internet over Wi-Fi everywhere but in your home. And that happened suddenly, after you hadn’t changed anything about your network.
And it’s not just you, because your colleague gets the same error message on his Apple computer in the design studio you share. And it isn’t the way you configured your networks, because you hired a guy to configure the one in your studio, while you configured the home one yourself, using only Apple hardware and software. And the guy you hired to wire your studio is competent, because that is what he does for a living, and has done for 20 years, as his bald head attests.
And you want the Air to connect to the internet because you want to get photos off your camera, and you can’t do that with your desktop Apple computer (an iMac) because iPhoto will not open in that computer. iPhoto will not open in that computer because your iPhoto library is corrupted, and the usual secret fixes for that problem (Command-Option open) do not work. Besides, the iPhoto library on your MacBook Air is also corrupted.
Your iMac is set to open Aperture when you connect your camera to it, but Aperture shares iPhoto’s library, so if you plug your camera into your iMac, Aperture spins uselessly and stops responding, just like iPhoto does.
You can sometimes force iPhoto to open on the Air by holding down Command-Option on launch, but if you did that, the photos would just sit there, because the Air cannot connect to the internet in your home. So you couldn’t share the photos on Flickr or Instagram or Facebook, and what would be the point of having taken them? And besides, the Air has no room for photos because the Air has no room on its little bitty drive. And you can’t edit photos on your Air because it’s a “light” computer by design. So even if iPhoto wasn’t broken on your Air, and even if it had room on its itty bitty drive, the best you could hope to do would be dump a bunch of photos into it and then not edit or share them.
The iMac has internet access, but neither Aperture nor iPhoto will work on it because of the aforesaid corruption problem.
So I’ve bought iPhoto Library Manager to fix the corruption in my library, and I believe it will do that, but it’s been working on the problem for fourteen hours so far and it is not even halfway finished. Yes, I have a large library. By tomorrow night, if the software has worked, I may be able to access my photos—although there is the very strong possibility that when I connect the camera, Aperture will open, and will freeze, because it doesn’t know that iPhoto Library Manager has built an entirely new photo library, because that’s how iPhoto Library Manager solves the problem. So tomorrow night, when iPhoto Library Manager finally stops grinding away at my corrupted photo library, I may need to uninstall Aperture just to get the photos off my camera.
I also can’t access internet content outside my living room because my walls are thick and my network no longer recognizes my Airport Extreme (so I’m waiting for Apple to deliver another one) but that would be a third kvetch in the same post, and two is all you get.
So I think maybe Apple is telling me to go out and spend time with my friends on this cold but sunny morning, and to only use computers in my studio, where they and the internet magically work. Only, why would Apple tell me that? How does that message get me to buy more of their stuff? It doesn’t, logically. And yet I know I will buy more and more of their stuff. I’m probably buying some right now.
I should acquire an unfaithful mistress and lavish her with jewelry I can’t afford. At least then people would understand.
IN EPISODE No. 80 of The Big Web Show (“Everything Web That Matters”) I interview Daring Fireball author John Gruber about his background in computer programming and journalism; the joy of designing print layouts with QuarkXPress and the transition from print to web; why investors who are angry at Apple have it wrong; why some web standards geeks who once passionately disliked Apple have grown warmer toward the company; and the secret story behind the name, “Daring Fireball.”
In A List Apart Issue No. 367, Peter-Paul Koch, Lyza Danger Gardner, Luke Wroblewski, and Stephanie Rieger explain why Apple’s new iPad Mini creates a vexing situation for designers and developers who create flexible, multi-device experiences.
Each week, new devices appear with varying screen sizes, pixel densities, input types, and more. As developers and designers, we agree to use standards to mark up, style, and program what we create. Browser makers in turn agree to support those standards and set defaults appropriately, so we can hold up our end of the deal. This agreement has never been more important.
That’s why it hurts when a device or browser maker does something that goes against our agreement—especially when they’re a visible and trusted friend of the web like Apple. Read Vexing Viewports and contribute to the discussion.
This issue of the magazine also marks the departure of Jason Santa Maria as creative director after seven years of brilliant design and support.
Jason’s elegant redesign of A List Apart and its brand in 2005, together with the master stroke of bringing in Kevin Cornell as illustrator, brought the magazine new fame, new readers, and new respect. Over seven great years, his attention to detail, lack of pretension, and cheerful, can-do attitude has made working on ALA a pleasure. Jason was also a key member of the strategic team that envisioned ALA’s upcoming content expansion—about which, more will be revealed when the site relaunches in January.
Jason will continue at ALA as a contributing writer and as designer of A Book Apart (“brief books for people who make websites”), of which he is also a co-founder.
DESIGNERS. WE LOVE CANVASES. It’s what we know. Even the cave wall had predictable, fixed dimensions. On the web, in the past few years, we’ve finally had to acknowledge that the canvas is not fixed, that each user’s canvas is different, and that fixed-width design—while safe and comfortable because it’s what we know—really doesn’t make sense in the world of HTML, and probably never did. We’ve spent the past two or three years rapidly learning (and sharing) new ways of designing.
But while we were unwrapping ourselves from the notion of a fixed canvas on the web, many of us were gleefully tucking into a fixed canvas in Apple’s world of the iPhone and iPad. True, the iPad had more pixels than the original iPhone—an advantage also enjoyed by later iPhone models with their Retina displays. But they shared easily interchanged aspect ratios (4:3 for the iPad and 3:2 for the iphone), enabling designers to design right to the canvas.
Apple’s fixed canvas wasn’t just a designer’s security blanket. It enabled us to craft a certain kind of polished experience right to the device. We laughed (or cried) at the Android with its 500 “standard” breakpoints and counting. Apple had given us a fixed-width sandbox and we built castles in it.
Well, goodbye to all that.
The end of fixed aspect ratios
With the iPhone 5’s switch to a 16:9 aspect ratio, and given the unknown aspect ratio of the upcoming iPad mini, “we’re going to see a big change in a certain type of iOS app—the one designed for the device,” Craig Grannell predicts in today’s reverttosaved.com:
[Veteran developer John] Pickford summed it up by stating his approach would no longer depend heavily on screen shape, and I’ve heard similar from other developers, both of apps and games although especially the latter. In a sense, this could be a good thing—freeing up iOS from the constraints of specific screen shapes opens up developers to whatever Apple throws at them next and should also make apps simpler to port to competing platforms. But it also impacts heavily on those tightly crafted experiences that were designed just for your iPad or just for your iPhone. Having all the action take place only in the very centre of a screen, because a developer cannot guarantee what device you’re using, or, worse, carving out a viewport and surrounding it with a border, could cheapen iOS games and apps in a big way.
Perhaps I’m being pessimistic, but pre-iPhone 5, indies were already feeling the pinch. With that device and perhaps a new, smaller iPad to contend with, the shift towards more fluid and less device-specific apps seems inevitable.—Craig Grannell, iOS screen fragmentation points to a shift in app development
I share Craig’s assessment of what the change in aspect ratios portends for application design. But I believe that designers will rise to the challenge, as we have on the web; and that bright app designers will find ways to design experiences which, even if they are actually flexible behind the scenes, still feel like they were custom crafted for the device in your hand.
REDUNDANT MECHANISMS that fail to communicate with one another can make using Mac OS X Lion more confusing than it should be.
Consider the screenshot shown here. While Apple’s Software Update knows that I have downloaded the latest version of iPhoto (“Your software is up to date”), Apple’s App Store, pulling from a different database, does not know that I have already installed iPhoto. It only knows that a new version is available.
Because the App Store’s left hand doesn’t know what Software Update’s right hand has already downloaded and installed, the App Store flashes a red download alert badge, urging me to download 500MB of Apple software that Apple’s OS has already installed on my Apple machine.
Suppose I don’t bother to check Software Update and verify that the App Store’s “Update” tab is urging me to take a nonsensical action. Suppose I actually go ahead and click “UPDATE” in the App Store’s “Update” tab. What will happen?
The software, all 500 MB of it, will download again, and install itself again. That’s what will happen.
And the cream of the jest? After installing the software again, if I click into the “Purchases” tab of the App Store, the “Purchases” tab will inform me that an iPhoto update is available, and urge me to install it. And if I have been huffing nitrous all day and take Apple’s advice, the 500 MB package will download for a third time and install itself a third time.
And you thought Retina images were tough on bandwidth.
(A friend tells me that Mountain Lion resolves this clustercuss by removing Software Update from the equation. I suspect that those of us still using Lion are receiving unintended anal leakage from UI decisions that make sense in Mountain Lion but are idiotic in Lion. #imisssteve)
“IF I WERE advising them on these decisions, I would have had them look at what people actually want from Facebook — fast access to their friends’ photos and posts — and … helped them design an HTML5 web experience that actually works for mobile.”
