A pet peeve of mine in Things is the inability to have sub-areas. In my eyes, you’re forced into categorizing your tasks into one of two ways – neither of which work all that great:
- Option 1: Areas for all the things!
Pro: You’re actually using areas and projects as Culture Code intended
Con: In order to pull this off, you’ll likely have lots of areas which becomes overwhelming to look at, especially on iOS.
- Option 2: Areas for higher level things, and projects for sub areas.
Pro: Less visual clutter
Pro: By using projects for sub-areas, you can take advantage of project-only features like headers
Con: You’re not using the app as intended so you lose the distinction between actual projects and sub areas
While I’ve settled with Option 2 as the better option for my use cases, I’ve never been fully satisfied with my projects and sub areas being indistinguishable from one another.
Over the past several months of using Things, I’ve played around with a few characters to differentiate the two. The two that have stood out in my mind are the checkbox symbol (☑︎) and what Apple’s character palette considers a “Parenthesis Extension” (⎜). ( They actually have separate characters for both left and right extensions, but I can’t seem to find any visual difference between the two.)
I eventually settled with prefixing my sub-areas the parenthesis extension rather than prefixing each project with the checkbox. The extension seemed to introduce the least amount of visual clutter, and I find the divide also visually indents the sub-areas nicely under their main areas which helps to further the idea of it being nested under the area.
I still wish Cultured Code would just allow us to selectively disable the “progress pies” for sub-areas, but until then, this is a nice way of quickly distinguishing sub-areas from projects.