Apple Embraces Tinkering for the First Time in 20 Years
Steve Jobs famously described the computer as “a bicycle for our minds.” Whether or not you’ve heard that before, it’s worth refreshing your memory on the context by watching this short video. The gist is that humans aren’t very efficient at getting around when compared to the rest of the animal kingdom, but because we are “tool builders,” we can more than make up for it. The tools we create magnify our capabilities. They make us better versions of ourselves. And the computer, Jobs believed, is “the most remarkable tool that we’ve ever come up with.” So what a bicycle can do for our bodies, a computer can do for our minds.
I love this analogy for many reasons, but primarily because it’s not simple. It’s far-reaching and it works from many different angles. One thing I draw from it, that others may or may not, is that the bicycle-like properties of the computer are strongest for those who use this remarkable tool to make tools of their own. A computer is a bicycle that makes bicycles, and a human is most magnified when they are a tool builder, not just a tool user.
To me, whether Jobs intended it this way or not, the “bicycle for the mind” is the tool that empowers you to repurpose it for your specific needs, not just to consume things with it, or use it in the same way as everyone else.
Or, in the words of former Apple Product Manager of Automation Technologies Sal Soghoian, “the power of the computer should reside in the hands of the one using it.”
Creators Build Tools
Many people use their computers for creative work, but, as I covered in my last post, everyone who does any kind of work also does some kind of meta-work, creating tools and systems that support their process. You might build a small business entirely around pre-packaged services like eBay or Shopify or Squarespace, but at some point you’re going to go beyond just using computers and services and start creating tools to make your work easier. This might be as simple as a customized spreadsheet to model your business plan, or a set of TextExpander snippets that automate your customer support replies. Or it could be as complicated as a multi-step Photoshop Action, or even a proprietary asset management system.
Creators build tools, which means they need tools for building tools.
Computers, Hammers, and Saws
The first home computers were tools, but also expressly and proudly tool-creation devices. The blinking cursor on an Apple II or Commodore 64 was as much an invitation to create your own BASIC program as it was to load and run someone else’s.
Early home computers were powerful for the time, but also simple. As combination tools-and-tool-creation-systems, they were a lot like a hammer or a saw that you might find in a woodshop. You can use a hammer and saw to build a bookshelf, or you can use them to build a jig that will speed up your production of a dozen bookshelves.
You may discover that a jig can speed up your work by tinkering away with the tools you use every day. Tinkering is a word I use a lot. It was years of tinkering with expressions in After Effects that led me to create my short film TANK. Tinkering with color correction led directly to Magic Bullet. Tinkering means experimenting, trying things out, and expanding your capabilities. Going farther.
In a woodshop, the same tools you use to do the work are also the tools you use to to the meta-work of automation. This means the woodworker is fully empowered to build their own tools. And they inevitably will, thanks to the power of tinkering.
Two Bicycle-free Decades
Early home computers shipped with BASIC. Early Macintosh computers shipped with Hypercard, which you were invited to use to create recipe books and home inventories, but was also famously used to create the hugely-popular game Myst.
In 1998, marking the triumphant return of Steve Jobs, Apple released the iMac G3. The “i” was for Internet, and this computer that would come to define the new Apple was in every way a consumer device, designed for every kind of person to use, not just computer nerds. Instead of a blinking cursor, it prominently featured the Internet Explorer web browser. The emphasis was on using a computer, on consuming content from the web.
This same year, Apple discontinued Hypercard. The iMac — the foundational device of the Apple we know today — was the fist Mac that didn’t come with an obvious way to customize its capabilities. It was a tool, but not fundamentally a tool-making tool.
And that would set the trend for Apple devices for the next twenty years.
“Anyone Can Code”
No, they can’t. Not just anyone can make an app. Exhbit A: People don’t.
That first iMac did ship with AppleScript, a noble, if wrong-headed attempt to dress up code as plain English. OS X shipped with a terminal app that could run bash and Python.
Scripting is powerful, and significantly less intimidating than coding an app. But scripting is still coding, and most people find writing code intimidating, becuase it has nothing to do with their creative work.
No normal people ever used these tools to make their computer-centric work easier. Building apps, large or small, became exclusively the domain of programers. A rift was starting to form between computer users and the super-users who could repurpose the computer to do their will.
Programing is great, but it’s not using a hammer to build a jig. It’s using a hammer-factory to build a hammer. When the tool-making tools don’t look anything like the work-making-tools, the worker is disempowered. Unless your work is making code, coding isn’t tinkering.
Computers from 1998 to the present day have disempowered their users by not shipping with simple, easy-to-use tools for tinkering.
But What About Automator?
I’m being a little unfair with that last assertion. Apple did take a stab at code-free scripting in OS X, with an app called Automator. It first shipped with Mac OS X Tiger in 2005, and on the surface, it would appear to be exactly the kind of tool-making tool that I claim has been missing since Hypercard.
Automator’s express mission was to allow people to create custom tools using a graphical model of stringing actions together. It would seem, on the surface, to be exactly what I’m asking for.
I realize that to some, the above screenshot seems as intimidating as the Xcode screenshot. But there's a key difference: Just about anyone can tell what is happening in the Automator workflow above. When you download an Automator workflow, you can open and dissect it like this, and see how it works. This gets back to my “blinking cursor” theory of computers that natively ran BASIC: If running it is a lot like writing it, you can learn by example and tinker your way to the next level.
Automator was a great idea that seemed to be held back by a lack of support, or interest, within Apple. It can do a lot, but never quite enough to become an essential part of my workflow. The few times I tried making anything useful with Automator, I would inevitably hit a wall, and resort to scripting. Any useful Automator workflow I ever got my hands on was essentially a wrapper around a script.
As just one concrete example, Automator has nothing like an if/then action, so there’s no way to do the simplest kind of flow control. Here’s an Apple support thread about, you guessed it, working around that limitation with scripting.
Also, it sounds glib to say it, but I’m sincere when I point out that no one ever made Myst with Automator. Automating repetitive tasks is fine, but we’re all better off when our tool-making tools allow us to have fun, to express our creativity, and to make art, games, and stories — not just resize and rename a bunch of JPEGs.
Third Parties Step Up as Best They Can...
There are several great Mac and iOS automation tools from third-party developers.
TextExpander is an easy first step into automation for many. It allows you to type something short, which gets replaced with something long. If you email Slugline support and I sign off my reply with “Feedback like this helps us prioritize future development, so thanks again for getting in touch!” I hope you don’t mind knowing that I don’t type that out every time by hand.
Keyboard Maestro is a deep and powerful tool for automation on Mac. I’ve been using it a ton since the discontinuation of Quadro for iPad, and I’m sure you’ll hear more from me about it.
Hazel is another wickedly useful Mac tool for Automation. I use it for simple things, like tidying up my downloads folder, but I also built a remote render-monitoring system with it for TANK.
In 2015, a company called DeskConnect released an ambitious iOS app called Workflow. The easiest way to describe Workflow is “Automator for iOS.” To my great surprise, where I struggled to do useful things with Automator, I immediately found myself creating useful tools with Workflow.
I also had a similar reaction to many others, which was that Workflow was so awesome and so powerful that I genuinely wondered if Apple would continue to allow it in the App Store.
On iOS there’s Drafts, which offers automation for text. It’s a syncing notes platform that can spit out your text in all kinds of interesting and powerful ways.
It wouldn’t surprise me if the creator of Editorial had trouble building a business model around it. I know first-hand how hard it is to make money with a productivity app. I’ve never invested too much effort into making anything complex with Editorial, because I didn’t know many other writers who used it. As much as I love TextExpander and Keyboard Maestro, the topic of discussion here really is about automation tools that ship with the computer, like BASIC and Hypercard did. Attempts to keep Hypercard alive as a paid product failed. The bicycle-making capability, I believe, must be ubiquitous. It must be fundamental to the computer, like a blinking cursor.
But unfortunately, in 2016, Apple took a very public step away from this idea.
...While Apple Steps Down
In 2016, Apple eliminated Sal Soghoian’s position, prompting him to leave the company. Here’s what John Gruber of Daring Fireball said about that:
...a huge part of my argument for why I feel so much more productive on a Mac than an iPad revolves around the automation technologies that Soghoian’s group developed. [...] I find this to be a profoundly worrisome turn of events for the future of the Mac. I hope I’m wrong.
Gruber wasn’t wrong. Automator hasn’t been noticeably updated since Sal left Apple, and the Mac still suffers from a lack of tinkering tools, and a massive rift between users and coders.
But, crazily, Gruber was wrong about something else: While the Mac has not taken any steps forward in empowering its users to create tools, iOS has, and profoundly so.
That iOS app I mentioned above called Workflow? Apple did not kick it out of the App Store for being too powerful. Instead, in 2017, they acquired it. The reaction from the community was hopeful, but I and many others found it hard to be optimistic. Apple has a history of acqui-hiring, and of killing off beloved professional apps like Aperture and Shake.
But at their 2018 WWDC conference, Apple revealed the best possible news for Workflow fans. Workflow, under the new name Shortcuts, would be updated and integrated deeply with Siri in iOS 12.
Apple was not just going to ship an automation tool. They were publicly tying it to Siri, one of their most important initiatives. Apple shouted from their biggest stage that automation was a key part of the future of iOS.
When I watched this Keynote, I think my legs started pedaling involuntarily.
Shortcuts, Shortcuts, and Shortcuts
Apple did make the namespace a little confusing by renaming Workflow to Shortcuts. iOS 12 also debuted the idea of “Siri Shortcuts,” which are hooks that apps can add to allow Siri-based voice access to specific features. This is separate from, but related to, the Shortcuts app, which is literally just an updated version of Workflow. With it, you can download and/or create Shortcuts, which are graphical mini-scripts that can do all kinds of useful things on your iOS device.
Confusing? Sure. But wait a minute: Download and/or create. Shortcuts encourages you to do both equally. To dissect and learn, or to jump in and tinker. In other words, it’s the 2018 equivalent of the blinking BASIC cursor.
The bicycle is back, and I couldn’t be more excited.
Do you, like many people, have a love/hate relationship with your smartphone? Maybe you agree with Mat Honan, who wrote in his hilarious review of the Google Pixel 3, “When I am not looking at my phone, I become slightly anxious. And then, when I do actually look at it, I become even more so.”
Shortcuts, the app, is my favorite thing to happen to the iPhone since the camera got decent. I truly feel that my relationship to my iPhone has fundamentally changed, because I can now build things on it that make it do things that only I would ever want. Useful things, but also fun things. Complex things and simple things.
My wife was annoyed that her iPhone would make noisy alert sounds when she was trying to take a nap. I created a super-simple shortcut that asks how long she plans on napping, and turns on Do Not Disturb for that amount of time. It took five minutes to create and share with her via AirDrop.
I had an idea for an app that would help me prep portrait-orientations images for Instagram. The problem is, there’s no way such an app could ever be profitable. I didn’t really want to make money with it, but I couldn’t afford to hire a developer to make it, so the idea sat. Now I’ve tinkered it into existence as a shortcut.
Prior to shortcuts, the only Apple-supplied way to solve this problem would have been with a Mac running Xcode, and all the encumbrance of building a custom iPhone application. With Shortcuts I was able to tackle this problem while sipping a beer at my favorite lunch spot.
For this genuine use case, the iPhone is now its own development platform.
There’s so much you can do with Shortcuts that it’s difficult to know where to start. My recommendation is that you start very simple. Like maybe so simple that you wonder if it’s even worth doing.
There’s a pizza place near my office that serves one kind of pizza each day. They post it on their website in a consistent enough way that I was able to make a super-simple shortcut to extract just that information. I assigned it a Siri phrase, so now I can say to my phone, “Hey Siri, what’s the pizza of the day?”
Shortcuts can also do useful things with images beyond just cropping. These pretty screenshots adorning this post? I made them with another shortcut I put together that masks iPhone screenshots and arranges them in a row.
And hey, it’s no Myst, but I even made a shortcut that turns plain text int a simple interactive “Choose Your Own Adventure” story.
Pushing the Limits
Making a simple shortcut is easy. I showed my 9-year-old son how to do it, and before long he’d created a short quiz to test my knowledge of Pokemon and marine biology, and mock me for getting answers wrong. I asked him if programing a shortcut felt like building in Minecraft. He said “No, it’s much easier.”
It’s also possible to make deep and complex shortcuts. I made one called Next Small Thing that attempts to be a genuine project-based to-do list manager, with the unique feature of only showing you the next available task, so as not to overwhelm you — a feature that tends to only be available in overwhelming to-do apps.
The most complex shortcut I’ve made so far is called Drinking Buddy. It logs your alcohol consumption and gives you a rolling calculation of your Blood Alcohol Level, which you can optionally record to Apple's Health app. It started simple, but I kept tinkering, and before long I had something almost app-like.
A Touch Painful on Reentry
But shortcuts are not apps, and this fact will not be lost on you as you use them. They feel most app-like when run from their Today View widgets, like Drinking Buddy above. Alas, just as often, you’ll see their alerts and menus presented over the Shortcuts library, or even over the actual guts of the shortcut.
Shortcuts can be a bit brittle and tricky to troubleshoot. So living with them can feel a bit like breakfast with Wallace & Gromit, where the trappings and mechanisms of your automation are dangling in plain view, and you may just spend as much time tinkering with them as you save by using them.
The power of Shortcuts to tie apps together can be both a strength and a limitation. One of my favorite shortcuts is also one that you’re least likely to try out, because it requires up to four apps and services to work. I use Gear Checklist to build custom checklists for all my photo and video shoots. Based off a master equipment list stored in either iCloud Drive or Bear, you select a project name and prep date, and then pick which items you need for the shoot. The shortcut then creates a project in Things, my to-do list app of choice.
But to do so, it relies on the aforementioned Drafts, and an extension to Drafts called Things Parser. If you’re willing to install all this stuff and configure it, you, too, can conveniently create photo gear checklists at the touch of a button.
UPDATE: I’ve updated Gear Checklist to work without Drafts and Things Parser. Now all you need is Things.
Shortcuts can be run as Action Extensions (the things that show up when you press a Share button in iOS), which is very cool and powerful. For example, you can find a photo in the Photos app and share it to my Panogram shortcut that splits wide images up into tiles. But if you do, Panogram will probably crash, seemingly for lack of memory. This seems a bit silly on a phone with 4GB of RAM. Running Panogram from the shortcuts app works fine.
There are some simple things that shortcuts just can’t do, like automatically run at a particular time, or set an alarm, or create a contact. There’s no way to copy/paste actions in a shortcut, nor are there any tools for navigating your list of actions, so creating complex shortcuts requires patience and a lot of scrolling.
The good news is, a strong and vocal community has formed around Shortcuts. Apple must be noticing just how deep a chord they’ve struck with this addition. What we have now is truly just the beginning, and it’s wonderful to have reason to believe that Apple is committed to placing the power of the (tiny, portable, and ever-present) computer into the hands of the ones using it.
Back to Bicycles
So, is the “bicycle for the mind” back? I think so, but with a little caveat.
Job’s bicycle analogy was all about efficiency of locomotion. Without a bicycle, we’re highly inefficient animals at just getting around, but we can build tools, like bicycles, which put us at the top of the list.
But I also take from it that riding a bicycle is good for you. It makes you stronger. Buying a tool and using it is like driving a car — you’ll get to your destination, and efficiently, but you’ve done nothing to better yourself. Every day that car will take you exactly the same distance.
But each day you ride a bicycle, your legs get stronger. You get where you’re going, sure, but maybe more importantly, the more you ride, the farther you can go.
This is the way I look at the Jobs bicycle analogy: When you build your own tools, you make your mind stronger, and able to go farther the next day.
As I use Shortcuts more and more, I feel myself somewhere between driving a car made of apps built by other people and riding a bicycle of my own creation. I’m creating genuinely useful tools, and I’m pushing myself farther each day I ride. But I’m also just using someone else’s app. I’m not sure if I’m truly living Sal Soghoian’s dream of the power of the computer residing in the hands of the user.
But I know something fundamental has changed in my relationship with my iPhone. It’s now something I can tinker with, in a way Apple hasn’t put their full weight behind for 20 years. The result, for me, is that my phone is less anxiety-inducing. At times, it’s downright inspiring.
So, as I said on Twitter, Shortcuts is like an electric bicycle — maybe you’re not getting quite as much exercise as you should, but it’s better than driving.
Apple should be proud that they’re back in the bicycle business. Maybe, just maybe, the key to keeping our phones from ruining our lives is to put the power to control them back in our hands.