Changes to Sketch’s Conceptual Model

A few days ago, I received an email from Sketch informing me (a customer) of upcoming changes to the app’s licensing model. They come as part of broader changes, which you can read about here.

I was thrilled when I discovered Sketch. For a long time, one of my primary tools was Macromedia Fireworks, a pioneering drawing and prototyping application that blended bitmaps and vectors and featured ‘symbols,’ reusable components that could take variables.

At the time, nothing matched Fireworks for UI work. The component-based paradigm allowed you to design a button and drop it into several screens using different labels. If you tweaked the original button, all instances would change. Amazing.

Continue reading

Appreciating Device Upgrades

Yesterday I upgraded my laptop to the latest version of its operating system, macOS Big Sur. Big Sur was released a month ago, but I waited because Descript — an app central to my podcasting workflow — wasn’t yet compatible. Descript released a supported update yesterday, so I thought the time was right. As usual, I backed up my computer before updating its OS. But I didn’t need to: the update was utterly problem-free. (Still, it’s best to be cautious: backing up only takes about an hour and saves many hours were something to go wrong.)

I love Big Sur so far. The system’s user interface changes make it a more coherent sibling to iOS and iPadOS, the other operating systems where I spend much of my time. There aren’t many new features, but many existing features (such as notifications and various system controls) have been refined. This is subjective, but my computer also feels faster.

Continue reading

The Electronic Whole Earth Catalog

A fantastic find (via The Long Now Foundation): the Internet Archive is hosting a MacOS System 7 emulator running a copy of The Electronic Whole Earth Catalog. The Catalog is a hypertext version of the venerable Whole Earth Catalog. It was published in 1988, several years before the invention of the World Wide Web.

Opening screen from The Electronic Whole Earth Catalog
A screenshot from The Electronic Whole Earth Catalog

This find is interesting for several reasons. For one thing, the Whole Earth Catalog is culturally significant: many makers and geeks (myself included) cite it as an influence. Even though it first existed in print, the Catalog wasn’t meant to be read linearly: even in book format, you’d skip around to read granular content items organized by subject. (Here’s a PDF scan of the first edition from 1968.) The Catalog was a perfect application for a hypertext before hypertext technology was widely available.

And that’s where another interesting angle comes in: the Electronic Whole Earth Catalog was implemented in Hypercard, a hypertext authoring and navigation system that came bundled with early Macs. Hypercard gave many people (myself included) their first experience of using and creating hypertexts. I learned a lot from this fantastic software, and reference it often with students and clients. Most haven’t heard of Hypercard or seen it, which makes this emulation a treasure.

The Electronic Whole Earth Catalog

TAOI: Reimagining Email

The architecture of information:

The team at Basecamp has developed a new product, Hey. It seems like an interesting — and opinionated (I mean this in a good way) — reimagining of how email works. If you have some time, Basecamp CEO Jason Fried’s video introduction is worth your attention:

Hey was in the news yesterday because its mobile app is being pulled from Apple’s iOS App Store, and Basecamp’s management is vocally fighting the move. Much has been written about that situation already, and I won’t say more about it here. I say it “seems” interesting because I haven’t yet tried it firsthand; currently, access to the product is by-invitation. My thoughts below are based solely on the product’s website and the video above.

Continue reading

Alternatives to 32-bit Apps on macOS Catalina

When a new version of macOS comes out, I usually upgrade my computer relatively soon. I like having access to the latest features, and significant macOS release upgrades are generally trouble-free. That hasn’t been the case with the newest version, Catalina. The trouble stems from the fact that Catalina doesn’t run 32-bit applications. While most major software in the system is now 64-bits, there are still some stragglers — especially legacy apps and drivers that haven’t been (and likely won’t be) upgraded.

That’s why I waited longer than usual before upgrading to Catalina: there was one application in my system that was 32-bits, the driver for my Fujitsu ScanSnap S300M scanner. I knew this driver was incompatible because every time I launched it (under Mojave, the previous version of macOS), I’d get a warning saying that the app would not run in the future. (Here’s a way to learn which apps won’t work: under the Apple menu, go to About this Mac > System Report… > Legacy Software.)

Without this driver, the scanner is useless — even though the hardware is perfectly functional. This device is an important part of my workflow; I use it every other week to digitize most of my paper documents and correspondence. Fujitsu no longer sells this model and has no plans to release 64-bit drivers. So I was stuck. I had two choices: I could hold off on upgrading the operating system (for a while), or I could buy a new scanner. I didn’t like either option. Sooner or later, I’d have to upgrade the OS. And as I said, the scanner itself was in perfect condition; I didn’t need a new one. What to do?

It turns out there was a third option: look for an alternative driver. I found a third-party application called VueScan that works with a range of scanners, including the S300M. It’s been working well for me; the only downside is that it’s a bit slower than Fujitsu’s driver. But given my use of the scanner, it’s not slow enough to merit buying a new device.

Thus far, Catalina has been great. I’m especially enjoying the new Sidecar feature, which allows me to use my iPad as a second screen when I’m on the go. So far, everything is working for me — including my old scanner. The lesson: if you’re contemplating upgrading to Catalina, but are holding back because of legacy software on your system, consider looking for alternatives.

On Google Reader

Yesterday, I tweeted about missing Google Reader:

The tweet touched a nerve; lots of folks have chimed in, mostly agreeing with the sentiment or recommending substitutes.

To be clear, I still read RSS feeds every day. (I use Reeder on the Mac and iOS and synch my feeds using Feedly.) Although I’m open to exploring alternatives, I’m not unsatisfied with my current arrangement. (Ringing endorsement!) So I’m mostly not lamenting the loss of Google Reader’s functionality. Instead, I miss what Google Reader represented: a major technology company supporting a truly decentralized publishing platform.

Google’s brand imparted some degree of credibility to an emergent ecosystem. I suspect a nontrivial number of people must’ve tried RSS feeds because Google provided a tool to read them. It’s great that tools like Feedly, Reeder, Feedbin, NetNewsWire, etc. exist, but none of them have the broad appeal or brand power that Google does.

I said I’m “mostly” not lamenting the loss of Google Reader’s functionality. This is because while current RSS readers offer the basics, Reader was a natural, cohesive component of my personal information ecosystem. Unsurprisingly, it looked and felt like (and integrated with) other Google tools like Gmail and Google Calendar, which I was using extensively at the time. As befit a Google product, Reader also offered excellent search capabilities. None of the RSS readers I’ve tried since offer the same level of coherence and integration that I experienced with Google Reader.

I sense Google Reader was a casualty of Google’s primary business model: selling its users’ attention to the highest bidder. I doubt RSS provided the scale or control required to run a mass advertising business. IMO it’s no coincidence that Google pulled the plug on Reader at a time when centralized social networks (Facebook, Twitter) were gaining traction in the mainstream. (Google+, which the company had launched a couple of years earlier, failed to take off. I wonder if they saw Reader as competition for G+?)

Six years after Google Reader’s disappearance, we’re wiser to the limits of centralized control over news aggregation. Subjectively, I sense many people are rediscovering the joys of blogging. (And, like me, using the social networks mostly as a way to publicize our blog posts.) Podcasts — which are based on syndicated feeds — seem to be more popular every year. While I miss Google Reader, I believe decentralized syndication is an essential part of the web’s future — not just its past. Is the time right for Google (or any of the other major tech platform companies) to embrace the platform again?

Collaborating by Default

Writing in his blog, Benedict Evans highlights the new wave of startups focused on personal productivity, “dozens of companies that remix some combination of lists, tables, charts, tasks, notes, light-weight databases, forms, and some kind of collaboration, chat or information-sharing.”

The cycle of bundling and unbundling functionality isn’t new:

There’s an old joke that every Unix function became an internet company – now every Craigslist section, or LinkedIn category, or Excel template, becomes a company as well. Depending on the problem, that might be a new collaboration canvas, or a new networked app, or a new network or marketplace, and you might switch from one form to the other. Github is a developer tool that also became a network – it became LinkedIn for developers.

What is new is the social nature of the experience. Old-school computing was lonely: the user interacted with his/her computer alone. Even if the system included communications software, such as email, interactions with other people were limited to that software alone. Today, we expect web-based applications to be collaborative by default.

We experience software differently when we assume other people will be sharing the place with us. As I’ve written before, we may ultimately discover that the purpose of social media was to teach us how to collaborate with people in information environments.

New Productivity

Mobile Computing at a Different Level

There are many ways in which people use computers. (I’m talking about all sorts of computers here, including smartphones and tablets.) Some people’s needs are very simple; they may use the machines merely to stay connected with their world. Other people have more complex needs. You can organize these various uses on a continuum that ranges from least to most powerful. Consider at least three levels:

  1. Accessing Content: Computer is used primarily to find information on the internet. Users at this level interact with others through email or social networks, but do so lightly. They spend the bulk of their on-device time accessing content created by others. Many casual users are on this level; it’s also where they have the least power.
  2. Creating Content: In addition to the previous level, computer is also used as a content-creation device. While users at this level may spend a considerable amount of time accessing content created by others, they also produce lots of content of their own. Many people who use computers professionally are on this level.
  3. Tweaking Workflows: In addition to the previous two levels, the computer is also used to modify how the computer works. This includes enabling new workflows through programming or scripting. This level affords most users the most power.

(There’s an even higher level, which is closer to the machine’s metal and affords a very small subset of people tremendous power. I’m not going to get into that here; I’m concerned with how most of us interact with these devices.)

Consider a transportation analogy. On level one, you are a passenger in public transport. On level two, you are driving a car. On level three, you are a mechanic, capable of making modifications to the vehicle to fix it or improve its performance. As with transportation, the higher the level, the more complexity the user must deal with.

Which level are you? If you’re like most people, your at either levels 1 or 2. This is OK; very few people take advantage of level 3. Learning to program requires great effort, and for most uses the payoff may seem to not be worth the investment of time required.

I was around eight years old when I first interacted with a computer: a TRS-80 Model I. As with most machines of this vintage (late 1970s), when you sat down in front of a Model I you were greeted by a command prompt:


The computer could do very little on its own. You needed to give it commands, most often in the BASIC programming language. (Which incidentally just turned 50.) So level 3 was the baseline for using computers at this time. We’ve come a long way since then. Most computers are now like appliances; you don’t need to know much about how they work under the hood in order to take advantage of them. However, knowing even a little bit about how they work can grant you superpowers.

Level 3 has come a long way from the days of the TRS-80. I’ve been messing around with the new Shortcuts functionality in iOS 12, and am very impressed with how easy it is to string together several apps to accomplish new things. For example, the Home ETA shortcut strings together the Apple Maps, Contacts, and Messages apps. When you install the shortcut, you configure it with your home’s street address and the contact information of the person you want notified. When you activate the shortcut (which you can do through various means, including an icon on your home screen), Apple Maps figures out your current location and uses it to calculate how far you are from home. Then it passes that information to Messages, which then sends your estimated time of arrival to your selected contact.

It’s not a mind-blowing functionality, but the fact that iPhones and iPads can do this at all is impressive. iOS users can now create arbitrary connections between components of the system, opening up possibilities that were previously difficult or impossible. Shortcuts also promises to make these much better as productivity tools. It’s the old Unix “small pieces loosely joined” philosophy — but in a platform designed to be less of a computer than an appliance. It opens up level 3 possibilities for level 1 and 2 users, without asking that they become mechanics.


You’re likely to run across lots of information during your day. Much of it is disposable, but some you’ll probably need to refer to in the future. A lot of it might be useful someday, but you just don’t know right now. Given how easy it is to search digital information, and how cheap storage is these days, you may as well keep it. I’ve long experimented with “digital junk drawer” applications for this use. I’ve tried Evernote, Yojimbo, Google Keep, Apple Notes, and Org Mode for Emacs, but my favorite thus far is Microsoft’s OneNote.

I keep a lot of stuff in OneNote: clips from web pages, quotes from famous people, impressions from books I’ve read, ideas for future presentations, meeting minutes, half-formed thoughts, etc. OneNote provides easy means to clip snippets of information from web pages and other apps whether I’m on my Mac, iPhone, or iPad. This makes it possible for me to keep a central repository of things I’m learning as I go about my day. It all syncs through Microsoft’s cloud, so all three devices have the latest information on them.

But OneNote is more than just a scrapbook for me: It’s also where I keep my projects organized. Whenever I start a new project, I open a new notebook in OneNote devoted exclusively to it. OneNote notebooks can have “sections” in them. Most of my projects have at least two sections: “Notes” (random notes, including scribbles to myself) and “Meetings,” where I record meeting minutes. Some notebooks also have other sections, such as “Admin” and “Research.” I aim for consistency with the naming and color schemes I use to differentiate these subjects. This allows me to quickly make sense of what I’m looking at when I switch projects.

Continue reading