Yesterday I had a busy day, that had me shuttling between Berkeley, Oakland, and San Francisco. In days like these, I prefer to work from my iPad (as opposed to a traditional laptop computer.) The iPad takes up less space, which makes it easier to use in cramped public transport. It also has an LTE modem, so I can remain connected to the internet when I’m out and about. Its smaller screen also encourages focus, which helps in distracting environments. I love it, and on days like these, I wonder when the day will come when I can do most of my work from an iPad.
That said, working from the iPad requires that I shift how I think about the structure of my work. I’ve written before about how I keep all my project materials organized using folders in the file system of my Mac. While iOS includes a Files app that allows interacting with such file structures, the system encourages app-centric (rather than project-centric) way of working. Rather than thinking “I’m now working on project x, and all the stuff for project x is in this folder,” context switching calls for remembering what app I was working in: “I was editing the document for project x in Google Docs; hence I must open Google Docs.”
Many of the productivity apps in iOS allow for arbitrary document groupings. Hence, I find myself replicating my file structure in the various apps. I end up with a project x folder in Google Drive, another in Pages, another in Keynotes, another in OneNote, etc. This adds to my workload and requires that I keep track of which app I used for what. I find it a less natural way of working than keeping everything grouped in a single folder. It’s one of the challenges of working in iOS that I’m continually looking to overcome.
Get updates via email
Sent every other week. I'll never share your address. Unsubscribe any time.