Bullet Journal App

I’m still using my Bullet Journal® notebook, and Ryder Carroll has released a Bullet Journal app for iPhone, under the name Bullet Journal.app for $2.99. It’s available on iTunes or the app store.

It’s not an app that functions as a an actual journal, rather, it’s intended to help people set up their first Bullet Journal, and be a guide to getting the most out of a Bullet Journal. The internal name is Bullet Journal Companion, and that’s apt; it’s a companion for your analog notebook. The app was released in February of 2017, and while I downloaded it then, I wasn’t really impressed. There have been several updates, and a new feature, the Library, has been added, as of the version released on May 17, 2017.

When you launch the app, the first screen you see is a linked table of contents:


The Reflection section is an exercise in mindfulness, as the Web page announcing the Bullet Journal Companion app notes:

Keeping track of what you need to be doing is important. Keeping track of why you’re doing those things is critical. Reflection will help keep you focused on the why through daily trackable reminders prompting you to unplug and review your notes.

The idea is that you set an AM and PM time to reflect each day on why you’re doing what you are doing. There are several inspirational quotations, and you can “log” or track the fact that you did in fact reflect by tapping a calendar date.  If you set up Notifications, the Bullet Journal Companion will remind you to reflect.  I’m not one to find this appealing, but others may.


I think that the purpose of the Library is to allow you to use your iPhone’s camera to take photos of a BuJo® page, give the Bullet Journal app permission to use the photo, and then associate it with a specific journal, date range and one or more tags to create a digital index of sorts. The search function appears limited to tags, rather than actual contents. I suspect that there are plans to allow OCR or some better ways of locating data than tags; as it stands it’s not terrible useful, and it’s certainly not innovative (see for example EverNote or Moleskine notebooks and app or Baron Fig notebooks and Codex.app.


Most of the articles appear to be also available on the official BulletJournal Website, though I admit I can’t find the one on Reflection on the site. The articles are a useful resource, especially for those getting started.


The Pocket Guide is a version of the step by step setup guide Carroll wrote for his Website. It goes through the basics of creating your first bullet journal with a blank notebook. It’s quite useful in that respect, and much easier than trying to look at a Web site while you work. I would absolutely have found it helpful when I set up my bullet journal. It’s updated, by the way, when the app updates, but the content is local to your phone, which means you can use it without being connected to the ‘net.


This appears to be an overview of the Official Bullet Journal notebook, also sold from the Website, but it doesn’t appear to be an actual store in terms of being able to buy one from your iPhone.

The Guide has merit for those starting out, but not $2.99 worth. The free .pdf Starter Guide you can download when you subscribe to the Bullet Journal Newsletter is, in my mind, more helpful. I’m not outraged at spending $2.99, but the Bullet Journal Companion app strikea me as somewhat useless; it’s not going to stay on my phone.

Adding Week Numbers to Apple’s iCal

It is often helpful to know what week, out of the possible 52 weeks in a calendar year, a particular week is. Here’s how to tell Apple’s.app Calendar to show week numbers.

  1. Open Calendar.app(or iCal on earlier versions of macOS) on your Mac.
  2. Choose Preferences from the Calendar menu.
  3. Click Advanced in the Toolbar.
  4. Click the box to the left of Show week numbers.
  5. Close the window.
Advanced tab of the Preferences for Calendar.app on macOS

Now look at your Calendar. You’ll see gray week numbers along the left margin of your Calendar.

macOS Calendar with week numbers.

To display week numbers in Google’s Calendar see this post.

Adding Week Numbers to Google Calendar

It is often helpful to know what week, out of the possible 52 weeks in a calendar year, a particular week is. Here’s how to tell Google Calendar to show week numbers.

  1. Log on to your Google Calendar
  2. In the sidebar to the left, click the pop-up menu for Other calendars.
  3. Select Browse Interesting Calendars from the pop-up menu.
  4. On the top of the Interesting Calendars page, click More.
  5. Click Subscribe to the right of Week Numbers.
  6. Click the Back to Calendar link to see your calendar, now with small blue week numbers in the top right corner of every Monday, next to the time setting at the top of the calendar.
The arrow points to the week number. This is week 16.

To add week numbers in macOS / OS X’s iCal, see this post.

Brett Terpestra’s iOS iTextEditors Resource Page

Brett Terpestra, the developer of the very useful OS X Marked app (a previewer for Markdown files), has created a page listing and describing iOS text editors.

As he notes:

The information was compiled by the web community on an open Google spreadsheet. I cannot vouch for its current accuracy, but will be verifying everything as I’m able. It’s meant to help you find the most useful way to write, code or take notes for your personal needs. Every editor is geared toward a slightly different purpose, with their own strengths and focus.

There are a bunch there that I’ve tried, and many that are new to me, but the way Brett has created a chart comparing features is really helpful. There really is an iOS text editor for everyone, and his detailed chart makes that clear.

Markdown and Me

As part of my determination to come up with a cleaner less keystroke-intensive workflow for all my writing, I’m taking a hard look at Markdown.

Dustin Curtis’ Markdown Mark

I first heard about Markdown back in 2004. I’d been blogging for a few years, and and hand-coding HTML. I came to HTML with surface familiarity with SGML in a library and deep familiarity with WordPerfect and WordStar. I’d been following Dean Allen’s development of Textile, and using Brad Choate’s MT-Textile plug-in for MovableType. John Gruber of Daring Fireball (one of the blogs that introduced me to blogging) created Markdown (with assistance from Aaron Swartz) as a way to format text for the Web without having to delve into HTML. In 2004 Gruber wrote about Markdown:

Markdown is a text-to-HTML conversion tool for web writers. Markdown allows you to write using an easy-to-read, easy-to-write plain text format, then convert it to structurally valid XHTML (or HTML).

One of the virtues of Markdown is that it is easy to use, and easy to remember. In Markdown, you use *for bold*, _ for italic_. Headings are marked by a leading *for the largest heading, **for the next size down, ***for the next level. The tags are easier to remember and shorter than those for HTML. They’re minimalist, and less likely to obscure text and slow down writing or editing.

John Gruber thoughtfully provides simple to understand Markdown syntax documentation.

When I discovered that Gruber’s Markdown Perl scripts worked with MovableType (this blog ran on MovableType then), I installed it and used it for a while. When I moved from MovableType, I stopped actively using Markdown, but I remained interested in both Markdown and Textile (and even used TextPattern Dean Allen’s CMS bases on Textile). But recently, I became much more actively interested in Markdown for a couple of reasons.

First, TidBITS, the publishers of Take Control ebooks, started  using Markdown as part of it’s work flow for creating Take Control ebooks. Next, Michael Cohen asked me to find a way to support Markdown in his WordPress Blog. He had become accustomed to writing in Markdown because of Take Control books. Secondly, publisher of The Magazine and smart tech writer Glenn Fleishman relied on Markdown format to produce The Magazine. Glenn’s enthusiasm about Markdown got me looking at Markdown much more closely than, say, learning enough Markdown to work on Wiki documents intended for internal documentation.

Why Use Markdown

  • A Markdown file is liquid data; it’s going to be easy to convert in the future, just as it is easy now to covert Markdown formatted text files to HTML, RTF, .Doc, or .PDF.
  • Markdown means fewer keystrokes than HTML. That means less keyboarding and no reaching for a palette or button to click. The longest tag I know of is three characters in a row.
  • Markdown lets you use HTML as needed, without having to do anything exotic involving obscure technical feats or escape codes.
  • Markdown may be easier to implement than HTML when writing on an iPad. At least that’s my current theory.
  • Markdown allows you to concentrate on the text as content, rather than the text as document.

Last year I wrote a long essay (eventually published by Boing Boing) that I initially drafted in Markdown, then hand-converted to HTML. I know, now, that there were better ways to do that, but I used BBEdit for the Markdown version and for the conversion to HTML, so it was relatively trivial to do. BBEdit not only fully supports Markdown as a language, it was one of the first applications Gruber provided Markdown tools for. The current version of BBEdit (11.0.2) has built in support for Markdown (including the ability to Preview Markdown files in BBEdit and customizable syntax coloring). And using Markdown in documents destined for the Web doesn’t mean I can’t simply insert any HTML I need that isn’t covered by Markdown tags.

For any markup that is not covered by Markdown’s syntax, you simply use HTML itself. There’s no need to preface it or delimit it to indicate that you’re switching from Markdown to HTML; you just use the tags.— John Gruber

If you want more BBEdit Markdown support, Watts Martin has created a nifty BBEdit Markdown Extension Package that builds on the work of John Gruber and Aaron Swartz, and adds some additional commands, not the least of which are Transformation commands to convert Markdown to HTML, HTML to Markdown, and Markdown to BBCode. There’s a catch to using Markdown in BBEdit; you have to set Markdown as a Language in BBEdit’s Preferences, and you need to use “.md” and “.mdown” as file name suffixes/extensions.

I’m going to spend a few weeks or months deliberately using Markdown as much as possible. I’ve installed Watts Martins Markdown Extension Package in BBEdit. WordPress via a Jetpack plugin supports Markdown, and there are a number of dedicated Markdown editors for OS X (Markdown Pro from RADSense Software, Mou from 25.io, Typed from Realmac Software) and iOS (Editorial from OMZ Software, Byword from Metaclassy, and others).