On This Date

Even though Seth and I no longer have a podcast, we still talk nearly daily about a lot of things. One of them is Drafts, and how we are using it for small life improvements here and there. Journaling is one of them, and it has become a part of standard practice for me. I don’t always have to put something in that’s poignant, but I do document quite a bit from time to time. I’m not perfect at it, but I try to do the best that I can. After all, it’s for me – so if I don’t do well at it, I’m only disappointing myself…

I journal using Drafts because I trust the system. Using Shortcuts, I run an automation in the morning to create the entry at 4:00am so I never miss a day; this entry is created in a specific format with the journal tag, date heading in yyyy-mm-dd format, and some weather and date information. I have another automation that runs just before midnight to save it as a nice-looking PDF at night and archive the draft. I still keep all the journal entries in Drafts: they live in my Journal workspace in the archive folder at the top of the drafts list. I keep them just in case I need to search for something later, even though I hardly do it. But there are times where I might want to go back and review them just to see what happened in the past. One of Seth’s problems was that he wanted a way to review things that happened on that day throughout the life of his digital journal. We used to use Shortcuts to do this, but that’s cumbersome at best. Why use another app when Drafts is perfectly suited for this? Seth ended up finding this forum tip on creating temporary workspaces, which admittedly was from a while ago (November 2018). Even though a lot of you think I’m an expert, there’s quite a bit of this stuff that I don’t know or use.

Using this example, I was able to create an action to show what happened On This Date. In simple terms, it searches for all drafts tagged journal, then searches for a string of the current date in mm-dd format; the action then has some code to let you filter the look of it, then load the workspace. I added a few things because I want to keep my Journal themes applied when creating this temporary workspace.

Let’s walk through the code a bit. First, you’ll find some configurable variables for your searching. This sets the name of the temporary workspace, the tags you want to include (or omit using !tag), and some strings to search.

//BEGIN config variables
//setup tags or searches you wish to load...
let name = "On This Date";
let tagFilter = "journal"
const now = new Date()
const date = now.toString("MM-dd")
let queryString = date;
let group = ActionGroup.find("Journal");
app.loadActionGroup(group);
let lTheme = Theme.find("custom", "Journal Light");
let dTheme = Theme.find("custom", "Journal Dark");
//END config variables

I also added the action groups I use for journaling as well as my journaling themes as variables, since I want to make sure I use them later in the action. Now that all that is configured, we can set up the workspace:

//create workspace
//for other options, see:
//https://reference.getdrafts.com/objects/Workspace.html
let ws = Workspace.create();
ws.name = name;
ws.tagFilter = tagFilter;
ws.queryString = queryString;
ws.setInboxSort("created", true);
ws.loadFolder = "all";
ws.showPreview = false;
ws.showTags = false;
ws.showLastAction = false;
ws.showDate = false;
ws.loadActionBarGroup = group;
ws.loadActionListGroup = group;
//ws.lightTheme = lTheme;
//ws.darkTheme = dTheme;

There’s a surprising amount of customization. I did find out that there was an undocumented .showDate customization that I could take advantage of. The only thing I would like to see added here is .lightTheme and .darkTheme so that I can set the themes directly with the temporary workspace which would eliminate the need for me to call them using the other methods; maybe those will get added in the future. The last part applies the workspace, shows the draft list, and applies my themes. I appreciated the callout in the original action, so I kept it in there: the workspace is temporary unless you use the .update() function, very much akin to a temporary draft to store information.

//unless you call `ws.update()`, this ws is temporary
//load this workspace, and display draft list
app.applyWorkspace(ws);
app.showDraftList();

//set the Journal themes
app.lightTheme = lTheme;
app.darkTheme = dTheme;

Actions like this can seem like a lot at first, but they are fairly simple enough to manage. This action can bring a lot of awareness and possibly even some joy to your day, looking back on the things you’ve done in the past. I’ve also included this in my widgets: I’ve found that I use it more often this way, and it’s a great use of a widget action for Drafts.


I have to admit, this is the first time in a while that I’ve done something like this to change some of my workflows. Not because I don’t adore Drafts, but because of how life has been going for me (all good things, thankfully). But it makes me wonder: what else am I missing? Seems like a great time to go exploring…

An Apt Analogy

With WWDC this past week, I’ve spent some time sitting – stewing, somewhat – about the iPadOS 15 announcements and the subsequent sessions that have highlighted everything coming in the fall. As I watched the Keynote, I couldn’t help but be slightly disappointed in what we didn’t get.1 At the time of writing this, and for at least until the public betas, I don’t have anything installed. I’ll let everyone else fall on that sword. But I’m still monitoring and saving bits of information that I see which are relevant to me, noting the things that will change for me once I get it loaded on my devices, and what it possibly means for the future of this device.

For a long time, I had the 11″ iPad Pro in a Smart Keyboard Folio (when it wasn’t paired with my monitor, external keyboard, and the Magic Trackpad). I wanted to move up in size, but I had been burned by not upgrading at the right time before all the way back to the 10.5″ iPad Pro and was determined not to make that same mistake again. But I’m sitting here on the other side of WWDC wondering if buying the 12.9″ M1 iPad Pro with 1TB of storage and the Magic Keyboard was the right decision: Apple gave us nothing with iPadOS 15 which requires it and there is no differentiation (yet) to warrant that much power. It’s a device that is so capable from a hardware standpoint yet is missing so much in the software. And I’d be lying if I said I didn’t have thoughts of what the hell Apple is thinking with the iPad and how it’s not going the way many of us want. Ultimately, I do believe it was the right decision based on how long I keep my devices, and I’ll do my best not to complain further.

When people start to complain about computing devices, they often turn to their favorite car analogy. But most of them get the wrong vehicle type when it comes to the iPad Pro. It’s not a V8 sports car. It’s not a motorcycle. It’s not a bike. It’s a modular computer which can do a lot of things well, makes trade-offs in certain areas to maintain flexibility and portability anywhere you want to go. So if you are going to target the iPad in this way, use an apt vehicle analogy:

The iPad is a Wrangler.

It does a lot of things well. It has different configurations to give you different experiences. It’s not the smoothest on-road vehicle, but it’s unmatched in the places you can take it anywhere in the world. The iPad Pro is not a powerful laptop, but it’s a powerful, capable modular computer. It can be more than a laptop, but there are also trade-offs that Apple is currently making to keep it modular. A great example on a Wrangler is that they don’t have power seats. There’s an assessment of trade-offs as to why this isn’t done, but I’m sure it’s something assessed for future incorporation. It’s not as easy as people would think: the Wrangler has other requirements to keep, and every change made requires an assessment of what it takes to implement the change. The engineers are forced to think differently when approaching these problems.

You can buy a ton of accessories for the Wrangler to change what you want it to do: you can lift it, put different tires on it, get really wild and put a tent on it, and more. And just like the Wrangler, you can buy different keyboards, input, and output devices which transform the use case. You can order a more powerful chip with more RAM (engine) and cellular connections (NAV system) directly from the factory to allow you to travel anywhere with ease. You can lift it on a stand and use it with an external monitor and keyboard to go more places, just like a lift kit. You can also use it in tablet mode, which feels like taking the top off and feeling the open air when you shed the confinement of the surrounding case. It’s precisely this modularity that makes both the iPad and the Wrangler great. There are people out there that have lived out of a Wrangler, which to some seems like it’s crazy – but just like a power user of the iPad Pro using extra accessories to get the job done, this is their preferred way to live. These types of people are pioneers of a new experience, and can open new ways of living which you never thought possible before.

At the end of the day, you have to choose the right vehicle/device to get what you want done in the way you want to work and what trade-offs you’re willing to live with to get your work done. I wish they would add more. And I think they will start to do that. After listening to Upgrade2, Jason had some great points about the groundwork that’s been laid for the future (some of this is quotes, some paraphrasing, but you get the idea):

When I look at what they did in multitasking, I start to think that they’re on to something, and that they’re headed in a direction that could do more. But that the first thing they did in this release was get it functional and give them room to advance it later.

They put a multitasking menu at the top of a window, which is similar to the traffic light dots on the Mac. Also, not mentioned in the Keynote, if you build [universal] apps with the menu bar for Mac, the iPad app has an icon in the toolbar containing your entire menu structure. And the Quick Note feature is literally a floating window. They also added a window that opens up that floats above other windows that you can also add to the Shelf.

I look at all of this and I am disappointed that there isn’t proper external display support, but literally every piece to do that is there. What that makes me believe is that Apple wanted to walk before it ran. When iPadOS 15 ships, they could literally turn this on at any point.

Am I disappointed that this isn’t available now? Of course I am. But I do think that it will be here sooner rather than later. Apple added the external pointer support and released the Magic Keyboard, knowing that users would take this one step further. My own personal setup includes a 27″ monitor, which looks comical right now with the pillarboxing and letterboxing. Yet, if I play a movie on just a 1/3 split-screen app, it plays in full 4K on my monitor like it’s a native screen. The pieces are all there and Apple needed to fix their mistakes before they can really make it possible. Even with the faults, it can become a completely different experience to what a traditional laptop or computer experience can be if you’re willing to put in some effort or follow the guide of those before you. The experience of using an iPad Pro is one that I appreciate and I feel that, despite the limitations of iPadOS, I can do more for the way that I work.

Like many, I’m disappointed in this moment that I effectively have a Hemi in my Jeep but the roads I’m forced to travel are limited in speed, have twists and turns creating indirect paths to my destination, and might even contain speed bumps so that I can’t really open it up to its full potential.3 But when it gets there, when Apple adds those pieces to the iPad Pro – hopefully in a point release – it’s going to afford me a different computing experience which I can make my own and really open this up. There are a LOT of people that don’t understand the Wrangler experience. It’s not something that most people understand how to use in the full capacity unless you’ve taken trips and put it through its paces, especially when rocks, sand, and water are involved. But when you do understand the capability, it can open up a whole new horizon of exploration for you. And the iPad Pro is just like the Wrangler. It’s no surprise that I love both of them.


  1. Hey, look. COVID happened. It likely influenced a ton of what happened this past year in the development of the new features. The fact that anything shipped is good, and what we got is really good. But I think the M1 suggested that more was coming. But I digress… 
  2. Time Stamp: 1:46:16 into the show, or the chapter on iPadOS 15. 
  3. Yes, I do know that the Wrangler 392 exists. I’ve driven one. It’s a monster, and it’s fantastic. But that’s not my point here. 

On Difficult Decisions

I remember the day back in 2011 where I drove up an hour and a half to go take a visit. “We’re just going to look”, I said. On the way up, we talked about what we wanted and how firm I was in some of my thoughts and ideas surrounding a life-changing decision: getting a dog. Getting a pet of any kind is an endeavor, and it comes with a lot of wants and desires for what puppy fits your family best.
More “On Difficult Decisions”