20150223 AppleWatch iPhone iPad

The Apple Watch is the New iPhone—and the iPhone is the New iPad

Apple had a plan when they introduced the iPhone. The iPhone was going to be your new pocket computer—easily at hand all the time. No bigger than a handful (and at the time, even a 3.5” screen was considered huge for a phone). It probably would’ve gotten thinner and thinner, until it became like the iPod touch 5th generation. (Have you held one of those recently? Pretty amazing.) iPhone app developers were given tools to carefully craft apps at a fixed screen size.

It’s been said that the iPad was in development even before the iPhone, but the phone was going to be the generate more money because everyone had a phone. So the tablet form factor (the iPad) was going to be an accessory. After being wowed by an iPhone, users would eventually want something that wasn’t so pocketable, but still booted up instantly, was thin & light & touchable, very secure, and ran the same apps as their phone.

That was the plan.

But a funny thing happened along the way:  Continue reading

Standard
more_glances_large

An Apple Watch ‘Glance’ is a Today Extension for Your Watch

The Apple Watch isn’t out yet—not until April, 2015, Tim Cook says. But your company should be planning and designing for it already.

Apple has released a beta version of the developer’s SDK (software development kit) for it, as well as UX HIG (human interface guidelines) for it, and your architect and UX designer should be abreast of them.

The Apple Watch introduces several new terms which will become part of your vocabulary, such as Glances, Short Look Notifications, Long Look Notifications, Apple Watch app, and Apple Watch Extension. Each one of these new Apple Watch interfaces varies in the amount of customizability it offers to your company when creating an Apple Watch experience.

What are all these new terms, and what’s a good way of thinking about them that won’t overtax our already full brains?  Continue reading

Standard
Apple Watch S1 - 000Percent

Is the Apple Watch S1 chip replaceable?

What if the S1 chip in the Apple Watch–containing the CPU and virtually the complete system on a single chip–were replaceable? Looking at the images on Apple’s web site, I found an intriguing matchup. (Note that I am not a hardware guy, so this is not based off of any hardware engineering knowledge.)

If you look at the image that Apple uses to demonstrate the Taptic sensor, it shows the internals of the watch. Look carefully at the left side of the watch’s guts, and you’ll see what looks to me like some sort of connector or latch mechanism.

Continue reading

Standard

Apple software quality: is the sky really falling?

There’s been a lot of hand-wringing for the past few months about the perceived quality of Apple’s software, and it seems to have reached fever pitch with yesterday’s post by Marco Arment (http://www.marco.org/2015/01/04/apple-lost-functional-high-ground).

Rather than whine about any perceived “losing” on Apple’s part, let me describe what I think is happening, what’s driving those changes, and how long those drivers might compel change into the future.

What’s happening?

The claim is that Apple’s <insert software name here> is buggy and/or getting buggier. <Insert software here> can refer to any or all of iOS 7, iOS 8, OS X 10.9, OS X 10.10, Xcode, Swift, iPhoto, etc.

I agree with most of the Apple-software-quality-is-declining blog posts in terms of individual problems they’ve pointed out. Yes, the iOS 8.0.1 bug fix went terribly wrong. Yes, there are problems with rotation handling in iOS 8. Yes, Xcode’s code formatter crashes constantly when writing Swift code (although this seems to have been mostly fixed recently). Yes, OS X 10.10 had wifi problems.

In Apple’s defense, consider the fact that the iOS 8.0.1 problem was detected within hours, and fixed in a day or two. It was also due to a configuration issue that wasn’t tested on live phone networks. Also in Apple’s defense, consider that none of these software quality problems resulted in lost data. Anyone around for OS X’s early days remembers the 10.3 Oxford chip set problem with Firewire 800 devices, and how that *did* result in lost data. http://www.cnet.com/news/firewire-800-drives-with-oxford-922-apple-statement-lacie-wiebetech-owc-updates-oxford-statement-taking-precautions/

Now this doesn’t mean I think Apple deserves a Get Out of Jail Free card. I mean, when you ship a laptop with no physical network jack and then you ship an OS update that messes up wifi, well, your customers deserve to be angry at their loss of productivity.

So, sure, Apple has botched a few things, but I think it’s pretty obvious that they’ve botched things at least as bad in the past. So let’s not bring up the “this wouldn’t happen if Steve Jobs were around” mantra, OK? Great.

What’s driving these quality problems?

Are there more problems than in the past? Yes, but that’s because of the enormous amount of change lately.

  • iOS and OS X are much more complicated than they used to be, and there are a lot more users worldwide.
  • Apple is trying to make iOS and OS X more alike than they already are (for users and developers), as ARM-based, touch-driven devices catch up to the speed and screen size of Intel-based, keyboard-driven devices.
  • Apple is innovating on the developer front (Xcode 6, Swift, Adaptive UI, Apple Pay, Health Kit, Home Kit, Extensions, Metal, iCloud, etc.).
  • Apple is innovating on the device front (Apple TV, CarPlay, Apple Watch, iPhone 6/6 Plus, A8 and A8X chips, etc.)

Despite the fact that Apple is famous for having a limited number of hardware devices for sale, this is an enormous amount of change. I can’t emphasize this enough. For the past two years, Wall Street has been saying Apple wasn’t innovating—yet this year Apple revealed enormous changes in APIs and devices that it has been working on in secret for 2 or more years.

So what’s driving these software quality problems? In a word, change. Enormous change, at a rapid pace.

Why is there this enormous ecosystem change?

OK, so enormous, rapid change means that software is harder to get right, out the door. But why? Why is Apple creating enormous change so rapidly?

The answer to that is complicated. It’s a lot of things: competition for users, competition for developers, and changes within Apple.

It’s not just Apple vs. Microsoft anymore. Apple is competing for users with Microsoft, Google, Amazon, and Facebook. The biggest challenges are Google—with Android, Chrome, search, and services—and Facebook, with the largest social network in the world. Court rulings have demonstrated that it’s hard for Apple to protect the difficult, multi-year work involved in device and UX design with intellectual property rights (patents). Apple has to compete a different way, so it’s going to be constant innovation.

Apple’s also competing for developers. Google has lots of developer APIs for its services, Facebook has Parse, and of course Microsoft has myriad popular developer tools both for Windows and the cloud.

The third area that has driven so much change is the shuffling of Apple’s management. Not only has Steve Jobs passed away, but also Tim Cook fired Scott Forstall. While neither of these events is cause for alarm, both Jobs and Forstall had strong opinions about user experience that conflicted with Jony Ives and possibly others at Apple. That resulted in the quick jettisoning of the ostensibly dated look of iOS 6 and OS X 10.9—and its skeuomorphic baggage—and the new streamlined look, motion effects, and transparency effects of iOS 7 and OS X 10.10. That executive shuffling may also have resulted in the new larger iPhones, requiring lots of rethinking of developer tools for layout out apps.

So what does the future hold?

OK, we have enormous change, driven by internal and external forces (management changes and competition). Can we expect this to continue? Are Apple users doomed to eternal software glitches?

Well, I think it’ll continue for the next 6 months at a minimum. We still have the iPad 6 Pro/Plus coming, which may require more UX and API changes. We have the Apple Watch, for which Apple has released a preliminary SDK, but promises even more changes in a year or so. Apple TV is set for a refresh. CarPlay is in its infancy. And now Mattt Thompson is thinking Swift may be only the beginning of a much bigger change for developer tools and APIs (The Death of Cocoa: http://nshipster.com/the-death-of-cocoa/).

So hold on tight, folks. The next year may involve almost as many changes as the past year. And there may be more glitches along the way.

My feeling is that this is unavoidable, with the enormous change that is happening at Apple.

The good news, though, is that I don’t think this rapid rate of change is sustainable. And I don’t mean just users and developers. I think Apple has some very sharp people, but even they cannot sustain this rapid change of pace forever.

The rapid pace of change will ebb and flow. Remember, Apple doesn’t come out with amazing new category-killer devices every year. There are 5-10 years between new categories: Mac, iPod, iPhone, iPad, and now Apple Watch.

So this torrid pace will continue for a year, and then I think it will calm down. And then Apple’s software developers can catch up. And 3rd party developers can catch up. And users will be able to breath a sigh a relief. But not before this tumultuous 2-year period (we’re half way through it now) is over.

Standard
iWork runs identically on everything from iPhones to Mac Pro's. So what, exactly, is an "iPad app"?

There’s no such thing as an iPad app

After the reviews of the iPad Air 2 and iPad mini 3 trickled out yesterday, the meme on Twitter seemed to be “Apple needs to create better iPad apps.” Nilay Patel of The Verge said it, @Lessian said it, and earlier @Monkbent said it.

While I agree with their intent—that iOS, now running on 64-bit processors, is fully capable of much more than apps do today—phrasing it in terms only of the iPad does a disservice to Apple, to UX designers, to developers, and to businesses.

I’m here to warn you today that there is no such thing as an iPad app. And if you think about it that way (thinking that iPhone and iPad—and even Mac OS X—apps are different things), then you haven’t fully grasped where Apple is moving to in the future.

It’s funny: in the past six months, the argument has completely inverted. Earlier this year, at a mobility conference, I gave a presentation called “You Can’t Ignore the Tablet”. Now, six months later, here I am warning people not to create iPad-only apps.

There are both technical and non-technical reasons why iPad-only apps don’t make sense. Here’s a list of 4 reasons why you don’t want to create an iPad-only app.

Continue reading

Standard
iWork runs identically on everything from iPhones to Mac Pro's. So what, exactly, is an "iPad app"?

The one thing no one is talking about for Apple’s iPad & Mac event this week

Software.

Sure, everyone wants new devices, and new devices are a key part of Apple’s ecology, but devices without software (apps) are meaningless. Take Windows Phone… please.

OK, so some people are talking about OS X Yosemite and iTunes 12 being unveiled tomorrow. Sure, that’s software, but we’ve heard all about Yosemite at WWDC in June, and iTunes will get a new coat of paint but otherwise won’t be significantly different.

I’m talking about major software changes. What am I talking about?

Continue reading

Standard