I’ll miss my Apple Watch. Kind of.

Last week Apple released the Series 5 Watch. Last week I went back to an analog watch.

I love adopting new tech, but I wasn’t going to buy an Apple Watch when they were first released; I always loved analog watches. Moreover, I didn’t see the value in the early Apple Watch, and it was expensive.

However, when I won an Apple Watch Series 2 in a competition a few years ago, I was enthusiastic. I’d used a FitBit in the past, and so I figured I’d at least get a good exercise tracker out of it. To my surprise, I fell in love with the Watch. I was fascinated by the novelty of it. I felt a bit like Dick Tracy, and all the new interactions and gorgeous UI elements felt like a sci-fi future.

Dick Tracy: ahead of the curve

Pretty soon thereafter, however, I began to feel it was a surface kind of love. True, the Watch was beautiful and quirky and presented all sorts of new interactions to play around with. It was a nerd blast. Nonetheless, I found myself slowly growing weary of it. There wasn’t one deadly blow, but myriad tiny knife slices.

Like forgetting to bring the Watch’s bespoke charging cable with me when I traveled; it was just another accessory I had to remember to pack, another cable tangled in my bag.

Or, not placing the Watch squarely on its charger the night before and heading out for the day, only to discover it was dying or dead after I’d left.

Then there was the fact that the Watch seemed to get slower with each software update. I’ve come to accept that computers and mobile devices age out pretty quickly, but my mental model of a watch is that it should have longevity spanning decades, not software cycles. (One of my first grown-up purchases was an analog watch I got for myself after completing undergrad; it still works and I still love it.)

The watch that replaced my Apple Watch; it’s solar powered!

You know that piercing fear when you suddenly wonder whether you silenced your phone at the movies or in a theater? Now I had that plus the fear my Watch would chirp, buzz or light up. Another thing to worry about. (Yes, I know you can set your devices to follow the same rules, but like many fears, this one isn’t very rational.)

Perhaps the biggest annoyance, however, came from the notifications. That really nifty haptic feedback, the little thump-thump on your wrist when there’s an incoming chat or text or, basically, anything else? It started to give me anxiety. Thump-thump: the boss sent me a chat message. Thump-thump:someone liked one of my tweets. Thump-thump: new email! Sometimes I’d forget to silence my Watch when I slept, and I’d be awakened by its thump-thumping. I stopped wearing it to bed, which was a bummer since sleep tracking was one of my favorite things about the Watch.

Periodically I’d audit my notifications, turning off any that seemed irksome. Recently, I just turned them all off. But when I did that, I realized I’d killed one of the primary benefits of owning a Watch: keeping up-to-date with notifications. But here’s the thing: is the constant barrage of notifications really such a good thing? And my iPhone is always within arm’s reach anyway.

This led me to another realization: many of the cool things the Watch does, my iPhone does just as well, or nearly as well. For example, I never used my Watch for Apple Pay since it’s sluggish and my iPhone is always at the ready. Did I ever use my Watch to control my iPhone camera? No. Were Apple Map’s turn-by-turn haptic notifications so much better than audio directions on my iPhone? No. Was navigating my podcast app with my watch really that convenient? Not at all.

Photo by Apple

But look, I’m not a hater. I think the Apple Watch is a truly revolutionary device. Far from being the flop some predicted, the Watch is perhaps the most innovative hardware Apple’s shipped in some time. And I can understand why people love it; the health integrations, sleep tracking, activity monitoring…it’s all pretty damn amazing.

But for me, my iPhone is good enough. The Watch, while cool, just added more cruft to my already cruft-y digital existence. Any new tech I adopt needs to have benefits that outweigh the day-to-day hassles. For many people, the Watch does just that. For me, it didn’t.

Oh, one last thing. The Series 5 has one really great feature all previous Apple Watches lacked: an always-on display. But this is a feature every single analog watch has had forever.

Should Adobe have acquired Sketch?

I was asked this question on Quora. Here’s my response.

sketch icon.png

For nearly a decade, Adobe completely missed the boat on what UI designers were doing, so we made do with Adobe Photoshop (and, for a while, ImageReady and Fireworks—good times!), but it was a less-than-ideal tool for the challenges we faced. It’s to Photoshop’s credit, Swiss Army knife that it is, that it had such a long run as a UI design tool. It wasn’t purpose-built for UI design, however, and with time its shortcomings became untenable.


I remember being surveyed by some smart Adobe researchers back in 2006; I shared my workflow with them, mentioned the kinds of features I was longing for, and explained where their products were falling short. Adobe responded to our needs in fits and starts. Apps like Muse were interesting, but were slow to evolve and ultimately didn’t address our needs sufficiently. Most of us continued to wrangle our way around Photoshop.

Around the same time, Adobe transitioned to an expensive subscription model that lumped all their apps together in a bundle that was unaffordable for many of us. We were paying a hefty monthly fee for apps we’d never use, and still didn’t get the one app we really needed, a purpose-built UI design and prototyping tool. Some of us switched to alternatives like, gasp, Keynote. (Don’t laugh: Keynote is fast, decent for drawing, supports styles, exports to HTML, and comes with every Mac. In fact, its UI seems to be a precursor to several modern UI design apps.) Nonetheless, that silver bullet UI design tool escaped us…and Adobe.

Keynote, looking like Sketch before Sketch was a thing

Then, in 2010, the lean, mean upstart Bohemian Coding launched Sketch which, in short order, ate Adobe’s lunch. At just $99, Sketch was affordable and did what designers needed. At this point, Adobe probably should have released a comparable product or perhaps tried to acquire Sketch outright. I’m not sure Bohemian would have gone for such an arrangement; they seem like a pretty rebellious band of warriors.

Nonetheless, Adobe must have seen the beauty and power of Sketch and realized it was worth acquiring. Perhaps they underestimated the burgeoning UI design and prototyping market. I find that hard to believe, however, since they were doing a lot of market research; I myself was polled twice, in person, by Adobe researchers. And I took many online surveys for Adobe, too. Maybe Adobe heard us, but management ignored the findings.

Some have suggested that Adobe didn’t consider acquiring Sketch because it was Mac only, but that theory doesn’t hold water. For one thing, Adobe’s often launched products on one platform first. For another, most UI designers were on Macs anyway. And, Adobe has the engineering muscle to have kept the Sketch UI and workflow, but re-built it so that it was compatible with both Mac and Windows. Moreover, when Adobe finally launched their “Sketch killer”—initially as Project Comet, later renamed XD—it was Mac-only, and the eventual Windows version lagged behind the Mac version for some time.

We may never know why Adobe didn’t try to purchase Sketch. What we do know is that Sketch is now the de facto standard for UI design and prototyping while Adobe, the longtime giant of desktop publishing and photo editing, has been sidelined in this arena. Even upstarts like Pixelmator and Affinity are giving Adobe a run for their money in the photo editing and vector design market. Nothing is sacred.

Adobe XD and Sketch: who’s zooming who?

At this point, XD is a solid tool—but it’s no Sketch killer. Its features aren’t as robust; it lacks the community and third-party plugin support that Sketch enjoys; and it doesn’t integrate with nearly as many apps as Sketch does. It’s like looking at a reflection of Sketch in a slightly blurry mirror.

Meanwhile, the market is shifting again, and even Sketch is facing competition from apps that promise to bring UI design, interaction design, and animation into a single experience. See, for example, FramerFigma, and the nascent Invision Studio.

So what should Adobe do? Do they continue developing XD, hoping to catch up to and ultimately outpace all the competition? That doesn’t seem like a great bet. Should they scramble a tiger team to develop an entirely new product that’s closer to where the market is headed? Or should they just cede the UI design and prototyping market altogether? It’s a less-than-ideal position for such a venerable company to find itself in. Then again, that’s what can happen when you don’t listen to your users.


There’s an axiom in business that it’s harder to correct course when you’re successful than when you’re struggling. Adobe was flying high and they simply didn’t see the warning signs ahead, or they ignored them altogether, letting a tiny competitor dominate a market they could have—and probably should have—owned.

Then again, hindsight is always 20/20.


Original Quora question here.