Arguably, the largest feature requests have been addressed. Notifications, for example, were dramatically improved in iOS 5, and multitasking support was added in the prior release. Where does iOS go from here? I’ve separated this mentally into two broad categories: fixes, for current features, and new features. It seems like the OS now requires more of the former than the latter.

Fixes

The notification system in iOS 5 has been an obvious improvement over the previous modal dialog. Gone are the days when you had to decide whether to answer the text message immediately, or forget to do it later. However, Notification Centre still isn’t up to the Apple standards of UI design. The most glaring instance of this is the tiny clear button beside each application’s group of notifications. It’s simply far too small to be functional. The solution isn’t to enlarge the button, but rather to remove it entirely. It shouldn’t be necessary to manually manage notifications in 2012. Ideally, each of these notification groups should automatically clear themselves after a period of time. For example, the reminder notifications I cleared earlier today are still present in Notification Centre, for some reason. This isn’t a bug, but a systemic problem with the current handling of all notifications. They’re present until you deal with them, one by one.

Apple’s next fix concerns Siri. I should provide a full disclosure, in advance of my complaints. In my iPhone 4S review, I wrote:

The biggest hurdle, however, is not technical. It’s mostly because commanding a virtual assistant feels very odd, even if it’s in plain language. I’m sure it’s a bit quicker for me to reply to a text message with my voice, or tell Siri to call someone as opposed to finding their name in my list of contacts. But I really, really do not want to. I’m also the kind of person who will find a secluded area to call someone in public, rather than trying to chat while walking down the street.

I am perhaps not the correct person to be writing about what Siri desperately needs. I use it for adding reminders, setting timers, and checking the weather. Nevertheless, I would like to see its functionality improve.

Foremost, I’d like it to be significantly more accurate. The other day I asked for it to remind me to prepare the asparagus. It interpreted this command as “enter the asparagus” which, aside from being a great name for a rock band, is quite useless. Apple assures me that Siri is a personal assistant, which I can use natural speech to command. But it isn’t contextually sensitive in the way that it should be. I admit that I’m not even close to an expert on how speech recognition software works, but this seems like it could be addressed with better recognition algorithms.

The next necessary improvement is for non-Americans, like myself. Siri absolutely needs to integrate with Maps and Yelp like it does in the States. This functionality is what Apple often demonstrates because it’s impressive and useful. Being able to dictate messages is useful, but the ability to ask for things nearby is futuristic.

Finally, I imagine third-party developers would love the ability to integrate with Siri. It isn’t as simple as it sounds, however, especially from a user interface perspective. Consider scheduling applications. I have three that I use regularly, and targeting each is difficult for a non-human to do. I place appointments with a set time in Agenda, my calendar app. This is easy enough to understand. But it gets tricky for short-form scheduling. I place reminders in the Reminders application, but I place tasks for completion in Clear, my to-do list of choice. The delegation of these tasks is tricky for a machine to understand. It could be specifically stated (“add ‘iOS 6 post’ to my Drafts list in Clear”), but this is inelegant and clunky.

New Features

As I said, I can’t think of any glaring omissions in iOS. Apple added WiFi syncing, a better notifications system, multitasking, copy & paste, and third-party development. The requested features seem to concern current features that are being asked to do more than they shipped with, like the iPhone’s home screen. It’s not a bad system, but it has become cumbersome with a veritable plethora of third-party applications. I have only 67 on my iPhone, but it feels like too many. Folders are a hacky workaround. There has to be a better way.

Shawn Blanc wrote an exceptional post on why this is a big deal:

Rebuilding the Home screen isn’t just about increasing usability. It is also about innovating at that “front-door interface” of how and where we get to the stuff on our devices (you can hardly do anything on your iPhone without going through the Home screen). Moreover, the ramifications of a reimagined Home screen go beyond iOS. As we are now learning via Lion and Mountain Lion, innovation on iOS is a setting of the stage for innovation on OS X.

In a post from earlier this year, Federico Viticci argued the same:

The concept of the Home screen we interact with today is broken because the Home screen wants to be a real, physical, tangible surface while providing access to the gates of the intangible: apps.

It’s a multifaceted problem, and one that cannot easily be solved. I don’t have any ideas on how it could be fixed, but it’s something that Apple is likely concerned with.

In a similar vein, I feel compelled to address home screen widgets. In his “Back to the Mac” keynote, Steve Jobs addressed the concept of OS X and iOS feeding each other. With this in mind, I think widgets would occupy a similar place as Dashboard does in Lion. If Apple does implement widgets, I think they would be placed on a screen to the left of the first home screen, in the area where Spotlight currently sits. The Spotlight interface would likely be integrated into this new screen.

In the Fixes section above, I pointed out the challenges of machines making decisions in a way that us human beings take for granted. I don’t think this is possible quite yet, but my “wouldn’t-it-be-cool-as-shit” idea borrows from Microsoft’s Future Vision video. At 1:26, a “5 Minute Focus” menu is shown, with tasks that the phone thinks can be completed in five minutes. As I noted when the video was released, this would be a great idea to borrow since Microsoft probably won’t ship it.

Others’ Thoughts

Aside from complaining about the current iOS home screen, Federico Viticci has a great iOS 6 wishlist, too. Features that he wants and which I’d agree with include iCloud tab syncing (coming), all-mailbox search, AirDrop, and better multitasking.

Craig Hockenberry, like the rest of us, is tired of having to enter his passcode when he’s at his desk. He’s come up with something called “Homebase” which would adjust settings based on device location. If, for example, your iPhone is within range of your home WiFi base station, it doesn’t require a passcode to unlock it, or for Find my Friends. Very clever.

Lastly, Neven Mrgan is annoyed by the grippers introduced in iOS 5. I’d like to see these improved as well.

That’s my iOS 6 wish list, then. It’s not complete, it isn’t particularly unique, and it likely won’t be fulfilled. But it’s what I believe would dramatically improve my iOS user experience. To what extent these changes will be improved will likely be known in the first half of June, at WWDC, and I’m excited.

I was looking at the PlayStation Vita the other day, and remembering that, had this product come out two years ago, it would have easily eclipsed the hottest product of that time — the iPad — which cost more and did far less.

I doubt this. The iPad was a huge product. Everyone was speculating and chatting about Apple’s tablet, as they had been since the rumours began several years prior. The hype around the Vita today, or the hype around similar products around the time of the iPad’s launch simply isn’t—and wasn’t—as big as the publicity of the iPad.

Steve Jobs seemed to understand better than most the need to manage perceptions. As Apple’s most influential advocate, when he said a product was wonderful, it was wonderful. From the first iPod (which kind of sucked) to the first iPhone (which really sucked as a phone), we drank his Kool-Aid by the gallon, and raved about these products.

The only reason people buy Apple products is because Steve said we should. The only reason people ever liked the iPhone was because Steve said it was good. Every person who buys an Apple product are too stupid to look elsewhere because they (we) bask in his magnificence.

This is, of course, nonsense.

Now think about tablets. The market had largely rejected them, and Steve Jobs himself initially said that folks would never buy anything without a keyboard. Then he brought out the iPad. And even though it was really just a netbook without a keyboard, folks saw the result as magical and different.

People didn’t buy it because it was an Apple product. People bought it because it ran the same touch-based OS as the iPhone and iPod touch, as opposed to its competitors which ran Windows. Competing products were basically laptops folded in half. The iPad was thinner, lighter, had longer battery life, and ran a touch-optimised operating system.

Without Steve Jobs, the magic is gone. Microsoft built Windows 8 to bridge into tablets and optimized it for that experience. People love Windows 8 because it is an iPad experience without the compromises […]

He’s just reading off the PR package now.

[…] and because Microsoft is assuring early reviewers get a positive experience by making sure they get the right hardware, software, and services wrapper. With Mountain Lion, Apple is doing the more traditional thing of just tossing the product out there.

Mountain Lion is in a developer preview stage. Windows 8 is in a public beta stage. These are completely different.

But without Steve Jobs selling the magic, folks are having a WTF moment. Instead of seeing the world through Steve’s reality distortion field, they are looking at the product critically and finding it lacking.

Nowhere does Enderle cite any early reviews of Mountain Lion, nor make any specific points as to what he thinks reviews dislike. His entire rant hinges on his unsubstantiated, unreferenced statement that 10.8 sucks. And, from what I’ve read so far, reviewers are generally enjoying it. The biggest controversy so far has predictably been Gatekeeper.

This article also relies upon his opinion that Windows 8 is amazing and beloved by reviewers. On the contrary, while the adaption of the Metro interface and the speed of the OS has been widely praised, most seem unconvinced by the combination of a desktop and tablet operating system.

David Pogue:

On a nontouch computer like a laptop or desktop PC, the beauty and grace of Metro feels like a facade that’s covering up the old Windows. It’s two operating systems to learn instead of one.

Matt Warman:

[…] it’s a weird, clunky, stupid duplication. Only Microsoft would provide an operating system with two different versions of its own web browser, available in two different places, with the same name and looks but different capabilities.

Furthermore, the two operating system updates aren’t even comparable. Windows 8′s Metro interface is a radical and interesting reconsideration of standard desktop paradigms. Mountain Lion’s name identifies its purpose as a relative of Lion. There’s no magical tablet interface, but good, solid updates throughout. Of course, Enderle doesn’t mention any of this. In his world, Mountain Lion is an utter failure (“sucks”) and Windows 8 is the future of everything. The reason this is occurring is because Steve Jobs is dead.

Rob Enderle should start mowing lawns. It’s hard to screw up as badly as he did here.

Apple’s competitors see things a little differently. Google, for instance, doesn’t sell products. Rather, they’re an advertising company that uses products and services as advertisement vehicles, much in the same way radio stations have worked for decades. Where Google differs is in the targeting of ads. Radio stations follow a particular format, listened to by a particular demographic. Advertisers can guess at what those listeners might be interested in. Google builds up a silo of data gleaned from your email, web searches, friends on Google+, and videos watched on YouTube. A giant heap of personal information that allows Google to provide services for free which are, for the most part, decent.

Microsoft’s revenue is mostly generated through licensing their software. Around 25% of their revenue comes from hardware sales, which is not insignificant, but cowers in the shadow of Windows and Office. Since Microsoft doesn’t sell computers or phones, the majority of their revenue must come from licensing. Direct sales of their software are always going to be dwarfed by sales to equipment manufacturers.

By contrast, Apple’s business model is simple: make products and sell them. There’s no need for ads in web services because one needs to have an Apple product to make real use out of iCloud. There are no licensing shenanigans to worry about because Apple designs the whole product as a unit. That means customers will receive the same stellar experience no matter what iPhone they buy, rather than the disparate platforms one has to contend with in the Android and Windows Phone families.

Apple’s business strategy is not reliant upon a killer product, like some magic bullet. Every product is a killer product which is improved over time as new features are demanded by consumers. The iPhone and the iPad are both lines of products that have significantly contributed to Apple’s bottom line, but they are in a long line of killer products introduced since 1997. And that’s the big secret: a long period of steady improvement and steady growth, with great products as the backbone.

While I had that document open, I began picking through some of the guidelines, noting that I could think of apps that violated many of the sections. There are developers that spam the store with nearly identical copies of applications, apps that are nothing more than a UIWebView, and a number of others. This is my shame list. It documents a number of egregious oversights, inconsistencies and irritations by Apple and by (some) developers alike.

Section 2: Functionality

2.9 Apps that are “beta”, “demo”, “trial”, or “test” versions will be rejected

For some reason, however, separate “lite” or “free” versions are allowed. A quick search for “lite” yields multiple pages of apps, including some approved within the past month. This is not a new rule, yet it is consistently ignored. Apps like Twitterrific and Astronut approach this the correct way: by offering an in-app purchase of the full version.

2.12 Apps that are not very useful, are simply web sites bundled as apps, or do not provide any lasting entertainment value may be rejected

Google’s applications are almost universally websites-in-an-app. Facebook is treading this fine line. These are not low-key, independent developers, but some of the most-downloaded apps on the store.

2.20 Developers “spamming” the App Store with many versions of similar apps will be removed from the iOS Developer Program

Oh really? Kosher Penguin’s apps, for instance, are almost exclusively of this kind. They were approved for sale between July and September of 2011 and are still available. Terrible.

2.22 Apps that arbitrarily restrict which users may use the app, such as by location or carrier, may be rejected

I already pointed out that the official Daily Show app can be purchased in Canada, yet the video content — the reason most people would buy the app — only works in the US. One could argue that the app itself is not restricted by location, or that it isn’t “arbitrary” because it’s a licensing issue. I disagree. The app should not have been approved for sale anywhere but the United States, or the international version should not give the impression that there is video content available.

Section 5: Push Notifications

5.5 Apps that use Push Notifications to send unsolicited messages, or for the purpose of phishing or spamming will be rejected

5.6 Apps cannot use Push Notifications to send advertising, promotions, or direct marketing of any kind

I already whined about this on Twitter. Glaring and repeat offenders include Hipstamatic, Soundhound and one of Jamie Oliver’s apps, apparently. While Push Notifications are arguably never unsolicited as users are required to explicitly allow receiving them, the spirit of these notifications present themselves as unsolicited spam.

Section 8: Trademarks and Trade Dress

8.5 Use of protected 3rd party material (trademarks, copyrights, trade secrets, otherwise proprietary content) requires a documented rights check which must be provided upon request

In a past article, I noted multiple instances of Google profiting from applications on the Android Market that use third-party trademarks without permission. Apple’s store isn’t entirely clean of this, though it’s decidedly less pervasive. For example, LightBike 2 is an obvious knock-off of Tron, the intellectual property of which is owned by Disney. Yet it’s been offered for sale since May in defiance of this policy.

Apple is currently attempting to get an incredibly weird Steve Jobs doll removed from the market, citing California law that protects the image and likeness of public figures. But one can add Justin Timberlake to your photos with an app. The photos are almost certainly unlicensed, and the concept of the app is legally dubious at best.

Section 10: User Interface

10.1 Apps must comply with all terms and conditions explained in the Apple iOS Human Interface Guidelines

10.6 Apple and our customers place a high value on simple, refined, creative, well thought through interfaces. They take more work but are worth it. Apple sets a high bar. If your user interface is complex or less than very good, it may be rejected

I’d need time on a geological scale to list all the apps that violate these guidelines.

Section 12: Scraping and Aggregation

12.3 Apps that are simply web clippings, content aggregators, or a collection of links, may be rejected

See 2.12 above for applications that are just framed websites. This guideline is so vague that it could include RSS readers.

Section 15: Violence

15.1 Apps portraying realistic images of people or animals being killed or maimed, shot, stabbed, tortured or injured will be rejected

There are a large number of realistic first-person shooters available on the App Store from developers small and large.

So what was the point of this post? Was it to point out that things are not always consistent? (Now that I’ve noted that nugget of wisdom, I’m sure I could knock you over with a fucking toothpick) Was it to show that Apple is some draconian overlord, or that developers are stupid, or that the App Store is a cesspool of vile, barely-usable and irritating apps?

No. Rather, it’s to note inconsistencies and problems with the current process of app approval in relation to Apple’s own guidelines. Overall, Apple has proven that it can maintain a safe, easy and convenient place for users to buy apps. They’ve done a fairly good job. There are just a few chinks in their armour.

1. An Apple Developer account is required to view this document. To allow for easy reading, I’ve mirrored a copy here (PDF), which is broadly similar to the one Engadget mirrored if my copy disappears for some reason.

In recent memory, Apple has been rather slow to introduce necessary (or “necessary”) features to iOS devices; copy and paste, and multitasking are two of the more notable examples. But, as it has been said time and time again, Apple tends to implement these features in a more logical, more intuitive and better way than the contemporary best version. In the last few weeks, Amazon has introduced a digital locker, and Google just announced Google Music Beta. Both are cloud-based music storage solutions (marketing speak be damned). And now Apple seems poised to jump into this field with a service of their own.

The current crop of cloud storage spaces work beautifully for documents, bookmark syncing and photos, all of which tend to be formats measured in kilobytes or just a few megabytes. Music and movies tend to reside in libraries measuring several gigabytes. While I would like to be enthused about Google Music Beta, it requires the user to upload their library. A 1,000-song library, using Apple’s estimations, is about 8 GB. Assuming a typical home user will have a 1 mbps upload, this will take over 18 hours of solid uploading to initially sync their entire music library. That’s simply far too long. Any time music is added to or removed from your library, Google’s tool will automatically make the necessary changes in the cloud. It’s good that it’s automatic, but it still takes time. It’s 2011. Why does online storage have the same (in)convenience it did back in 1995 with FTP?

Amazon does a way better job. Any time you purchase a song through Amazon MP3, that song gets added to your Digital Locker. This also goes for movies and TV shows purchased through those Amazon services. And yet neither solution helps me much, because I am Canadian.

In fact, anyone outside of the US cannot appreciate either of these solutions. Neither Amazon nor Google sought licensing from any record label to begin their cloud locker services. You can argue ad nauseum about whether or not they should be required to get this permission, but the fact remains that they’re treading on their (lawyers’) interpretation of American fair use laws.

In summary, then, the current state of cloud music storage relies on American fair use laws and individual users to manually upload their music files. Wouldn’t it be nice to change that?

Unlike Google or Amazon, Apple sells digital music in 26 countries. Apple has a much greater advantage in ensuring that the service they provide will be available in all of (or a majority of) the countries the iTunes Store is available in. Conversely, Apple has a major disadvantage if this service were to only be available in the US.

How will this service work, then? Will the user be required to upload all of the individual music files they own, à la Google Music? This is slow and cumbersome, as established. Will all tracks purchased from iTunes automatically be made available in the cloud? This has the potential to exclude large amounts of a user’s library if that user has ripped music from CDs or purchased it from other services such as Amazon MP3 and Beatport. As an example, while I have a substantial music library, only around 500 songs in it have been purchased from the iTunes Store, significantly less than the number of CDs I’ve ripped.

It would be in Apple’s best interest to allow access to all songs purchased through iTunes by default, but also allow users to add their own music to the bucket. The problem, as ever, comes back to the record labels and local laws. Since Apple cannot determine whether or not you actually own the songs you’re uploading, they might be granting you storage of your enormous library of pirated music. This would, to put it mildly, displease the record labels.

It’s a tricky and complex issue. Not providing users with the ability to upload their own files is grounds for user dissatisfaction, but allowing them this ability will piss off the record labels. And when record labels get pissed off, ordinary people tend to suffer most.

Before I begin, some quick housekeeping notes:

1. This post builds upon some rather fantastic posts by other writers, but with my perspective from the ground up. I have a small selection of others’ posts in the footer, and I highly recommend reading them.
2. I’ve broken this down quite a lot more than usual. If you’re reading this in an RSS reader, I’m sorry.
3. This is not an iOS v. Android comparison, nor is it necessarily iOS-centric. It’s the platform I am most familiar with, so it’s easiest to talk about at length (however, aspects of other platforms will be also discussed).
4. The post begins with a quick primer^[1]. Don’t skip it, though — I rather like it in-context.

Enthusiasts v. Normal People

Everyone is an enthusiast, a know-it-all and a devotee of something. Some people are crazy about music, others about fly fishing. I, for instance, am a bit of a nut for cars and photography. I’m not an expert in either field, but I respect and admire both. Let’s start with photography.

Professional photographers would scoff at the default camera app in the iPhone. It’s far too simple, and far too imprecise. There’s no way to adjust the ISO, the exposure or the white balance. But most people don’t care about adjusting those things. They open the camera app to get a quick snap of the events of that moment, and that’s it. For most people, the default camera app is all they need. For enthusiasts, alternative apps exist (such as Tap Tap Tap’s fantastic Camera+, which offers much finer control).

Let’s talk about cars^[2]. Normal people want a reliable car that doesn’t look too ugly to get them from point A to point B (and maybe the elusive point C, if they’re feeling frisky). They care about the comfort of the seats, the quality of the stereo and the colour of the paint. Non-human-beings like myself want to know whether or not the engine is direct-injected, what kind of transmission it has and the power distribution ratio (if it’s four-wheel drive). I’m an enthusiast who actually cares about that sort of thing, but if I were marketing an average car, I shouldn’t expect an average customer to deal with those sorts of decisions.

In both cases, an average consumer simply wants the best outcome possible, with the fewest nitty-gritty detail decisions. They just want their photos to look good, and their car to drive well.

Multitasking on iOS

To begin, let’s state the obvious: iOS doesn’t multitask. It does something I like to think of as task juggling. Sure, a few of Apple’s applications do true multitasking: emails and SMS messages and sent and received in the background, and new events on an Exchange calendar get automatically pushed to the device. But third-party apps aren’t allowed to do true multitasking.

There are a few multitasking APIs developers have access to. Pandora can continue to stream music in the background, Flickr can upload your snapshots, and Skype can receive incoming calls. Despite the initial whininess by some pundits, it actually works pretty well in most apps for most users. Apps that don’t really do any of these things (say, a game) get put into a “sleep” state when you switch away from them. When you switch back, it restores to the state it was in before you had to answer your modal iOS notification.

This implementation has a huge upside: it helps keep battery life high by only running the most relevant background processes. It also offers a downside: applications can’t periodically refresh. That means your Twitter client, RSS reader and Facebook will refresh next time you switch to them, but not while they’re sitting in the background. Some clever people have devised some clever hackish workarounds, like Boxcar which shows push notifications for Twitter and Facebook.

These two rudimentary paragraphs are probably obvious to those who are tech-savvy, and were probably boring. They’ll tie into the overall story, though, so keep reading.

iPhone v. iPad

This method of task-switching works pretty well in the single-task, single window environment of a phone. Imagine trying to juggle a couple of instances of Safari on a 3.5-inch display. It’s hopeless. Despite its 10″ display, the iPad also adopts these UI conventions. The larger screen, running at the same resolution of desktop displays of not-that-long-ago, is dominated entirely by one application, no matter the mental real-estate that application occupies. Watching a movie, writing a tweet and editing a document are all done at 1024 × 768.

When writing a blog post, I often have a few Safari windows open, a plain text editor and my Twitter client. I’m often referencing them all, and it’s easier to keep them all open on my XXL canvas (since tidied). A computer OS treats these as separate tasks — its definition of task is an application process. My definition of task is “the thing I’m working on.” Since a modern desktop architecture supports multitasking and multiwindowing, I can adapt and treat them as one task, even if the OS doesn’t. This is in stark contrast to the iPad, because it lacks both. Another example of this would be my web development setup. Again, it consists of multiple windows for various discrete tasks, even though it’s only one thing I’m working on.

On a phone, users don’t want to micromanage tasks. Every time I use someone else’s iPhone, their multitasking tray is full of every application they’ve ever launched. This is OK, because none of them are actually running on an iPhone (Android also puts unused applications into sleep mode, and Windows Phone 7 doesn’t have multitasking).

On the larger screen of the iPad, this doesn’t work as well. Multiple OS tasks may be one user task on that kind of device, and iOS only supports single-window tasks. Viewing only one app at a time is inelegant and inefficient. If you have an Android tablet, a Finnish company has developed an application called Ixonos, which allows you to have multiple windows open at once. But if you watch the video, it also proves itself as inelegant and clunky. The controls are far too small on a 10″ screen^{[3] [4]}.

Clearly, it’s your fault

I briefly mentioned my web development setup above. It usually consists of a Photoshop window or two, a tabbed plain text editor, Transmit, and a couple of browsers to test in. It’s a setup that works really well on my desk, but is hopeless on a 10″ tablet (let alone the Samsung Galaxy Tab’s much smaller 7″ screen). But, and this is important, it isn’t the OS itself that makes web development on a tablet a horrible experience^[5].

As I pointed out above, it isn’t just multitasking and multiwindowing (or the lack thereof) that affect the user experience. Even if the iPad had multi-both, it’s just too small to switch between all of those windows. In this case, as usual, it’s up to the user to delineate what is, and what is not appropriate for a tablet.

When Apple introduced the first iPad, they told people exactly what the tablet’s focus would be. They showed off the web experience, email, productivity, multimedia, books and games. It’s casual computing for average people. When Apple introduced the iPad 2, they didn’t change their focus one bit. The addition of cameras are the only slightly broadening factor, but even they fit into the scope of a casual computing device (the rear camera is an crappalicious 0.7MP). The increased RAM and the faster CPU are only there to enhance user experience when running and switching apps, not to provide the ability to run many at the same time, on the same screen.

Something about average users?

Average people (my dad, not my IT pro dad) understand the multiple windows ∴ multiple apps paradigm. They would be absolutely comfortable with a larger-display tablet. The trouble with a large tablet is that it further grains the market, because it’s niche is confusable with that of a consumer laptop. Instead of a simple tablet → consumer laptop → power laptop product line, it becomes something closer to simple tablet → power tablet and/or consumer laptop depending on what you’re doing with it → power laptop (never mind that the MacBook Air throws a wrench into Apple’s own product line).

I didn’t bring up the MacBook Air arbitrarily there, by the way. I see this hypothetical future iPad XL (or whatever) as being the Air of the tablet line. The Air is very specific: it’s a lightweight, go-anywhere MacBook that drains power from the battery through a pipette. In much the same way, an iPad XL would be the combination of the OS X desktop experience and the iOS touch interface. It’s probably the future.

Footnotes

1. It’s pronounced as rhyming with “trimmer”. The word that rhymes with “rhymer” is the stuff you put on walls before you paint. [↑]
2. This section is clearly inspired by John Gruber’s post linked below. [↑]
3. For your convenience and mockery, here is a mockup of an iPad with multiple instances of Safari running. You can even try syncing this image to your iPad to see just how awful that is. [↑]
4. Clearly a 15″ screen would be much more friendly to a multi-window tablet OS. Don’t mention those “tablet” convertible laptops, though. Windows is not a touch OS, no matter how many shells and skins are applied to try to make it one. [↑]
5. That said, I have heard rumours that one of my favourite web development environments is getting a “lite” iPad counterpart. [↑]

Further Reading

1. Frank, Steven. I need to talk to you about computers.
2. Gruber, John. Various and Assorted Thoughts and Observations Regarding the Just-Announced iPad.
3. Quintana, David. Mobile Multitasking.

iPad 2 — count on it

The event is very clearly about an iPad upgrade. Put all your money on that, if you can find a friend stupid enough to match your bet.

iOS 4.3 — count on it

A new iOS device means a new version of iOS. 4.3 has been in developer beta for a couple of months now, and it seems like it’ll be the version shipping on the second-generation tablet.

Random House on iBookstore — very likely

Random House, the world’s largest book publisher, announced today that they’re switching pricing models to the same kind Apple uses. It would be a major boon to the store (whose name I’m not comfortable typing more than once).

iOS 5 preview — maybe

Apple has done next-generation iOS previews in the March/April timeframe for the last three years. It might make sense to combine them into one event. If there is iOS 5 talk, I’m betting on a revised notification system, new voice controls and a new Maps application. None of the NFC stuff will be announced.

Developer show-off — sadly very likely

Five-or-so developers show off their apps in a clumsy manner. Oh, the joy and the suspense. Note that I like the idea of such an opportunity, but most developers that have demoed their apps over the years are lousy public speakers.

Steve Jobs — unlikely

I don’t think he’ll make an appearance. It’ll be a Phil Schiller/Scott Forstall show. PC Magazine points out that he might appear via FaceTime, which would be unlikely, but possible.

Mac OS X Lion — somewhat likely

On the one hand, it’s very clearly an iPad event. On the other hand, they recently issued the developer preview. I think they’ll save it until WWDC.

MobileMe changes — very likely

White iPhone 4 information — you’re joking, right?

Update: on further thought, this might actually happen.

White iPad — more likely than the iPhone

Quick note: I want to claim this before anyone else does. I think the second-generation iPad might have a carbon fibre internal frame and back, and I think the back will be painted. Think flatter, bigger iPhone 4. This way, they can do both the front and back in white or black.

CEO Steve Jobs defined the Retina Display of the iPhone 4 as a display that exceeded the resolution of the human eye from about a foot away. The magic number in that case was about 300 PPI. However, an iPad isn’t usually a foot away from the eye — it’s more like three feet away. If the pixel count were quadrupled, therefore doubling the resolution, it would be 264 PPI. That’s pretty close to 300 PPI, and probably comfortably above the magic number for three feet. But.

But, as I pointed out last time we chatted, that’s still more pixels than almost as many pixels as are currently in their 27″ Cinema Display. That display is fine when powered by a beastly graphics card, plugged into a wall. However, the iPad is powered by batteries and last I checked, the graphics capabilities weren’t rated as “beastly.” And I still think that such a display is prohibitively expensive to manufacture right now.

Engadget still thinks that the display will be ultra-high-resolution, and in theory I should believe their sources (on account of having none of my own). Their sources are usually correct, and there’s some evidence for such a display in the current SDK beta. The iBooks app has a double-resolution wood grain texture, the inclusion of which probably got someone fired. Furthermore, 9 to 5 Mac points out that Apple themselves want developers to include iPad@2x images. And holy crap, would you look at this: is this the display? Uh, no,

John Gruber checked his sources and it seems that I’m correct. Gruber slips that there are high-res iPads currently testing, but he believes they’re for a 2012 launch. He also points out that the new iPad is likely to have a screen manufacturing process similar to the iPhone 4 and iPod Touch — this is something I’d guess would happen also.

No surprises, then.

PS: This is wrong.

Apple made a bit of a splash with the launch of the iPhone 4. One of the most lauded features is its “Retina Display” – Apple’s name for its 326 pixel-per-inch screen. It is the highest-resolution display currently shipping in a consumer product, and is roughly equivalent to the quality of a printed page. It is with this display that Apple made two very intelligent decisions: the first was that they placed the display in a product they knew would be a hot seller in a competitive market. This ensured that it would be a feature consumers would be exposed to on a regular basis, and would be something they’d demand in competitive products.

The second intelligent decision was to double the resolution by quadrupling the amount of pixels on the screen. That ensured that apps designed for previous versions of the iPhone would be perfectly doubled in both directions, reducing the need for interface designers to have to re-think the display. A 1px-tall line became a 2px-tall line, but appeared at the same physical size. This kept upgrading custom interface components to the new resolution relatively simple. And so, as the first anniversary of the iPad’s introduction draws near, rumours are swelling that the next iPad will gain one of these gorgeous displays. “Ridiculous,” I say. And, if I do say so myself, I think I might be correct. It just won’t.

The iPad currently has a resolution of 132 pixels-per-inch (PPI). Compared to a regular computer monitor, it looks great, but next to an iPhone 4 it’s positively coarse. Since the iPad is the same size as a magazine page, it would be amazing to make it look as good as one. Many have pointed out that a 300 PPI display of the same physical dimensions as the current iPad’s would have a resolution of 2,325 by 1,746px. That’s 4,059,450 pixels: more than a 370,000-pixel increase over the 27″ Cinema Display. They see this as the biggest problem: no display like this is known to exist. However, I see this as a minor technological hurdle compared to the massive headache this will cause for developers everywhere.

Remember how I pointed out that one of the most intelligent things Apple did with the iPhone 4 is to double the pixel dimensions in order to keep the physical dimensions the same? A 2,325 by 1,746px display would force developers to re-think their apps. Old apps wouldn’t work on the new display, as they would draw half-pixels that can’t exist. The apps would be blurry, not just pixellated, and entire layouts would have to be reconstructed from scratch. In order to work around this, the second-generation iPad would require a 2,048 by 1,536px screen. However, this would yield a resolution of 264PPI – still high, but far below Apple’s own definition of a Retina Display.

The only solution I can surmise that would allow Apple to build a 300PPI display into the iPad, call it a Retina Display and still be gracious to developers is to shrink the physical dimensions of the screen. A display that is 6.8 by 5.1 inches (8.5″ diagonally) would match all of the desired qualities. However, Apple has been clear that they think the 10″ (9.7″ if you’re being pedantic) form-factor is ideal. There is no single solution that would allow all the boxes to be ticked.

Oh well.

I’ve been reading a lot on the blogonet, the twitscape, the pipe-o-tubes, the internet about just how delayed Cultured Code is with their implementation of OTA syncing for Things¹. Though I typically would understand CC’s predicament here, I don’t see their forthcoming implementation as successful (not that I know much about it). To the best of my knowlege, Cultured Code is currently writing their own backend for syncing between devices. This will require a massive amount of storage space, countless new staff to maintain it and a bulletproof uptime record. Somehow, I just don’t see yet another startup doing this. Why not leave it to the professionals?

Dropbox is likely the best way to store and sync files between devices. It has a ridiculously good uptime record, is impossibly fast and provides plenty of storage for each account. It’s nearly flawless and, best of all, they have an API for developers to use to integrate it with individual apps. My favourite on-the-go writing app is Plaintext, and it uses Dropbox so I can edit the same files wherever I am. It’s simple to set up and it hasn’t failed me. Cultured Code wants to reinvent the wheel. Why?

The one reason they might want to choose their own servers is that they have complete control over stability. This is understandable, but completely unnecessary. Cultured Code can only control so much, and a safe compromise could have been made with Dropbox. There’s one file that needs to be synced OTA, and it’s almost certainly under 1MB (my library file is a measly 200 KB at the moment). Why not rely on a service that plenty of people has, and that consistently delivers files around the world on a nearly constant basis? Cultured Code should stick to what they’re best at: writing damn good software.

Before I jump into the next part of this post, I have an unrelated complaint. Does anyone else think the noisy background on a few of Apple’s pages looks entirely out of place?

I figured now was a good a time as any to write up just a few predictions (most of them obvious) as to the condition of Apple’s lineup for 2011. This could get dry, but it’s 2:44 PM on a Wednesday, so what the hell else could I think of?

At some point between January and March, the iPad 2 (iPad Strikes Back, The Pad Reloaded, The Two Cameras… whatever) will be released. Count on a flat back with a structure made of composites for lighter weight. Perhaps it will have a carbon fibre back that’s painted black, to match the iPhone 4 in a way. It will almost certainly have a front-facing camera; a rear camera is less likely (have you ever held up an iPad in a way that you would a camera?). It will probably have a new chip (A5, or whatever), more RAM and higher capacities. Some have commented on the possibility of a white one – I see this as likely if the rear is painted, and less likely if it’s only the screen bezel that would be white. Look for a post about it nearer to the announcement date.

April will bring a preview of iOS 5. I wouldn’t be surprised to see wireless syncing in this update, but I doubt Apple’s NC data centre will be used for this. Can you imagine waiting for a 1 GB movie to sync with broadband upload speeds between 1 and 3 Mbits per second? I’d rather move each 1 and 0 to my phone manually with a toothpick and a bottle of gin (to ease the pain).

June will, as ever, bring a new iPhone. It will probably have roughly the same industrial design as the current generation, perhaps with a near-field-communication chip (this won’t be announced as part of the iOS 5 preview, even if it’s in the next-generation iPhone). Maybe there will even be (gosh-gee-golly) a white one. Look also for Mac OS X Lion around this time with a few more surprises than were showed at the sneak peek in October.

Speaking of a white current-generation iPhone, I’m betting on it being a limited-edition version in the spring, perhaps only available in a 32 GB configuration. Who knows? It’s a mythical piece of tech, spoken about only in hushed whispers by the elders huddled around a campfire. Whatever. Moving on.

September will bring the usual back-to-school iPod refresh. The Classic will probably be dropped – I haven’t seen an iPod Classic in use by anyone in about a year. The usual thinner, lighter theme will prevail, as ever. Now that the Nano is essentially a Shuffle with a screen, it will be interesting to see if they merge the two product lines. It wouldn’t be a surprise either way.

Of course, updates to the Mac lineups will be sprinkled throughout the year. MacBooks will probably acquire some amount of flash memory, to which the OS and contents of RAM will be written to, but with a regular hard drive for file storage.

As for myself, I will keep up my standards of posting almost an entire year apart in 2011. Hope that’s alright with you.

1. I wrote that sentence so I could use the acronym HTML entity. That’s how I roll.