Viewing all posts tagged with: Karbon

× Clear filter

John Gruber, in his Daring Fireball post responding to an article of the same name by Kyle Chayka at The New Yorker:

Saving a whole pile of notes to yourself as text files on your desktop, with no organization into sub-folders, isn’t wrong. The whole point of “just put it on the desktop” is to absolve yourself of thinking about where to file something properly. That’s friction, and if you face a bit of friction every time you want to jot something down, it increases the likelihood that you won’t jot it down because you didn’t want to deal with the friction.

This exact scenario is what led me—22 years ago, in 2004!—to create xPad for macOS.

I had been hired by a web design agency with a list of existing client projects, all of which were in some state of disrepair, and it was my job, day-in and day-out, to dig into ancient codebases and fix critical bugs as quickly as possible. These were the days before large-scale use of version management systems like Git, so I had to be extremely careful to keep many nippets of code and notes as I tore apart pages and services. And, at the end of each day, I would end up with 50 text files in TextEdit that I needed to save manually. The next day, I’d have to open them all up again.

I realized quickly in 2004 what I needed was a simple way to have a single UI that would allow me to create and edit text documents, but which completely removed the friction of saving, opening, categorizing and labeling. I solved this problem by building my first native app, xPad.

xPad would automatically store and retrieve all your documents for you, and had simple support for visual categorization (which you could completely ignore if you so desired)1 . The best part was that it was very fast and had no cognitive overhead—it was just was the place all of your text went. While it didn’t make much money in the beginning, after I made it freeware it ended up being quite popular because I wasn’t the only person who needed a tool like that.

Chayka, in his article, wrote:

I’ve tried out other software for keeping track of my random thoughts and ideas in progress—the personal note-storage app Evernote; the task-management board Trello; the collaborative digital workspace Notion, which can store and share company information. Each encourages you to adapt to a certain philosophy of organization, with its own formats and filing systems. But nothing has served me better than the brute simplicity of TextEdit, which doesn’t try to help you at all with the process of thinking. Using the app is the closest you can get to writing longhand on a screen.

Part of my goal with xPad (and, later, the iOS app we created at Karbon called Scratch2 ), was that it didn’t force you to adopt any philosophy, format or filing system. It was simply a fast way to create text, with zero managerial duties for saving, retrieving or managing files.

Modern Apple OSes have adopted the same basic strategy for their core Notes feature (Notes today is very similar in concept to, but significantly more feature-rich than xPad and Scratch were), and the default operating system behavior to generally save and reopen documents without user action helps a lot.


  1. The biggest mistake I made with the development with xPad was in opting to use a custom blob for all of the text data. The app had robust support for import and export, and you could even do the expected OS-level things like dragging items out of the drawer to export a text file or save notes to your iPod (!). But, ultimately, my lack of data architecture design knowledge at the time led me to build the simpler solution (single blog) instead of building based on a structure of literal text files. Where this complicated things was when someone somehow lost access to xPad itself but still had their data blob—they wanted to get their text out but couldn’t do it without the app. I solved a majority of these with my own bespoke support tool, but it was a design mistake that haunted me a bit when the app got very popular as freeware and was used for more than a decade longer than I expected.
  2. Scratch’s goals were not exactly the same as xPad’s—it was for iOS after all—but it did share some core DNA, philosophy-wise. Overall, Scratch was about quickly jotting down information on the go, with the device you had in your pocket all the time. Most users likely didn’t refer back to older notes as frequently as xPad users would have on desktop. Scratch was the “quick-input notepad”, xPad was “a single solution replacement for Stickies, NotePad, Scrapbook and TextEdit.”