Recent Articles

[Michael Lopp, writing about Writer Pro](http://randsinrepose.com/archives/do-you-want-to-write/):
> Preferences are a sign of design laziness; they are an indication the people responsible for building the application don’t have enough empathy or desire to do the work they intend to be paid for: design the application so I that I can work, not think about how I might work.

He listed Word, Excel, and Photoshop as examples of “kitchen sink” apps which are packed full of features. I’d add to that list OmniFocus. I think the above quote encapsulates my issues with a lot of apps these days in general.

I’d recommend ignoring all the ridiculous stuff going around about patents surrounding Writer Pro (they’ve wisely decided to drop the whole thing) and just check out the app, especially if you make software. Writer Pro is an exercise in stripping an app down to what is needed, not what is asked for.

There’s an old adage about how we got cars with tail fins in the mid-1950s. It goes something like this: “instead of asking people what they wanted in a new car, they started asking people what their neighbor would buy.” And then we got cars with fins.

I can’t find a reference for this, but the adage seems to encapsulate the design decisions of a lot of software. Designing what *you* think the user wants instead of pairing things down to only what the user actually *needs*. It feels nearly impossible to do at times, especially if you dislike people emailing you screaming for features. But I think it is the direction that good, nay *great*, software is headed.

[Weswanders in *The Verge* forums](http://www.theverge.com/2013/12/21/5234580/patent-pending-ias-militant-stance-on-syntax-control) (worth reading):

>So, does iA actually have the exclusive right to the idea of Syntax Control, putting unsuspecting future developers on a collision course with iA? It appears the answer is no. What’s more, iA’s claims of beating everyone to the punch appear to be disingenuous at best.

This is an absurd stance for iA to be taking with Writer Pro, because as it turns out the Syntax Control stuff is more or less baked into OS X and iOS. I can’t wait to see other developers add in Syntax Control.

I am all for *every* writing app getting better. However, the hard part is always mixing and matching writing apps as more and more they want to play in their own sandboxes only.

Writer Pro is the best writing app on iOS, but I think Ulysses III is likely still the best on OS X (I need more time with Writer Pro on OS X to make the a firm statement). But even if I wanted to use UIII and Writer Pro together — it would be easier to make my own writing app.

The way I see it, right now:

– Writer Pro is easily the prettiest of the lot.
– Ulysses III has a fantastic organization and workflow system — the best of the lot.
– Byword has the very wise ability to publish your writing to your blog.
– Editorial makes my life easier with workflow automation.
– Editorially makes shared editing a snap.

I want the best of all this writing tools, but even if I wanted to use them all — I would be stuck copying and pasting all day long. Lame.

I’m a huge productivity nerd, wait, make that recovering productivity nerd — which means I am actually productive. (Doing work instead of fiddling with things heralded to make you more productive.)

I got sidetracked there, sorry.

I’ve used OmniFocus since it came out and kGTD before that. I also used Things for quite a while and I’ve had flings with other to-do systems in the meantime. I helped Kyle craft Begin into the simple to-do app it is today. New to-do list apps are familiar to me, I just tend to actively ignore them.

Then Michael Lopp posted this:

Over the course of the weekend, I moved everything I’m tracking into Asana. I’ve been using Asana on and off for a year. It’s added a little more friction and a little more religion to my task tracking process, but it’s also done something Things hasn’t done in years – it’s new bevy of functionality has me asking one of my favorite engineering questions, “How can I do this better?”

There were some back and forth debates around Lopp’s post. I chimed in, saying I was going to look at other to-do options:

My goal isn’t to try and leave OmniFocus, but to make sure OF still is the best solution for me. OF has gotten so ugly on the Mac and iPad I almost refuse to use it in those places. Which means I am essentially using the iPhone app, and even the new iPhone app isn’t the best looking app.

I started with Asana and then tried almost every other multi-platform, modern, to-do list out there. Something full featured, something that can replace most of the functionality of OmniFocus, while also adding to it. In short: I was looking for an OmniFocus-like app that could also work with teams.

I didn’t find one.

What I found is Flow, a tool I hadn’t used in since it launched. Flow is primarily focused on team task management but I have been testing it as a standalone, single person, tool. While parts of the app are silly for a single user, it’s still useable as a personal tool, which means it passed my first test.

Flow costs real money: An annual subscription instead of an upfront purchase, which I think is the main reason it has survived. Flow’s revenue depends on the company’s ability to keep the product moving forwards.

The good news about Flow is that their most important app — the iPhone app — is the best of the lot. The iPad app is pretty good, but doesn’t support landscape orientation (odd). The Mac app is just a menubar quick entry app, which is quite nice because I can map it to a keyboard shortcut (like OmniFocus), but annoying that I have to run the Flow web app in a Fluid instance if I want a persistent view of my tasks. Overall the apps are solid.

Flow is now mature and, with its team tools, feels like it’s trying hard to be anything but OmniFocus…

On OmniFocus

In testing, using, and helping to develop Begin I realized the shortcomings of OmniFocus. It’s a fantastic tool, but it’s long in the tooth. It needs more than a UI overhaul and I’m not confident that there is enough value in waiting for that. If OmniFocus is overhauled it will be top-notch once again.

But why should I wait?

The value I get using a better product while I wait for OmniFocus to be updated will far exceed the cost of shifting between tools if OmniFocus is ever improved. Not to mention that OmniFocus will seemingly never be multi-platform — it will always be within the realm of Apple.

I love Apple but I loathe the idea of my important to-do lists being tied only to Apple products. Especially when it comes to teamwork — you just can’t force everyone to use Apple products (as much as I would love that) so multi-platform becomes a must have. ((Fair to say that Flow is a Mac tool with a web component, but that web component is all you really need these days to make something multi-platform.))

The Flow

I’m looking forward to rolling out Flow to all the people I work with as I think that will be the moment when it leap frogs OmniFocus in a big way.

Flow has more structure than OmniFocus and, more importantly, a lot fewer GTD-styled features. While I’ve never been a strict GTD follower, I do appreciate many aspects of the system. It took quite a while to get comfortable in Flow given the change from a GTD focused system to a task/list focused system. Gone are contexts, projects, start dates, time estimates, etc. You have to make peace with the idea that you get your task, assign it to a list and set a due date. Basic to-do stuff, but it can feel shocking when you come from OmniFocus.

Quick Reasons That I Really Like Flow

Topping the list are features for teams. The lack of team functionality in full-featured to-do list apps is akin to the lack of cloud synchronization in to-do list apps just a couple of years ago.

Team management is a must have feature for almost everyone working today.

Beyond team functionality, here are two little things I love:

• While OmniFocus supports notes on each task, I much prefer the comments field in Flow. I can use it as a running note log for myself on each non-team task. Say I have a task to call a person, but they don’t answer. The task is still important, so I reschedule it for tomorrow, but I still leave a note showing that I left a message. It becomes a quick activity log to tell me when I called, and how many times I called before I reached the person. Flow also shows a little log of who changed the due date, giving you a good idea of how badly you are delaying doing something.
• Lists and Workspaces. OmniFocus uses Contexts, Projects, Groups, and Single Action Buckets. Ugh. Flow simplifies that to Workspaces and Lists. Changing workspaces changes everything, it’s like switching databases, and is a really great way to separate personal and professional to-do management within one app. Within each workspace you can have tons of separate lists for further to-do breakdowns. (You can view your tasks from different workspaces in one place too.) I’ve long abandoned using projects and contexts in OmniFocus, so lists are really all I need as a way to track things and I’m finding the simplicity of moving away from OmniFocus freeing.

Overall I like Flow. My one complaint is that I truly do miss start dates. Due dates are great, but start dates are the way I love to work.

For now, Flow is making me happier.

Note

I’m not prepared to do a full review of Flow just yet, I’ve only been using it for a few weeks. I am prepared to switch completely and start rolling it out to my office. I’ll report back after using it full-time for a while.

Right now, the most requested feature of this site (from both members, and non-members) is for a podcast. I started preparing one; creating live streaming, live chat, its own site, found a person to partner with, etc. All I needed was a little design, some sponsors, and to start recording.

Except that was months ago and I have very little motivation to do a podcast. My reasoning — excuse — is that I don’t have time. That, though, is mostly a lie. I have plenty of time to do a weekly podcast if I want.

No, the real reason that I am not podcasting is because I’ve come to loathe the medium.

Every time I think “OK, time to do that podcast", I start listening to some podcasts, and then I quickly fall 20, 30, 40 episodes behind, because really podcasts are largely a pile of shit and they bore the crap out of me. ((I sometimes feel like they are only recorded so hosts can complement each other while they jerk-off.))

I’ve been thinking about why I feel this way and I think it’s largely focused around the goal of most (but not all) podcasters. Whether explicitly stated, or implied, most tech podcasters seek to create "a podcast that allows you to listen in on two good friends chatting about topics you’re interested in". That sounds great on the surface but in reality I don’t want to listen in on two people I barely know talking about things.

The reason I don’t want to listen in is because two friends talking are never on point. Subjects jump, there are insider jokes/back stories that I don’t get — but most of all I’d rather be a part of that conversation than a party eavesdropping on that conversation.

If you’ve never listened to the This American Life podcast, then I apologize because the rest of this post will make little sense. TAL is the best podcast out there — the scripting, pacing, research, and editing is top notch. The show feels casual, but has enough format, flow, and scripting that it becomes comfortable to listen to, instead of wanting to join in on. I think this is what most people desire to create, but don’t understand why having a casual chat doesn’t create this. ((I am among those people.))

The goal of a podcast should not be that the podcasters enjoy the show, but that the listeners enjoy the show. I think that’s lost on most podcast hosts.

Who is talking should be less important than what’s being said — just like writing a blog — and yet that’s not the case.

The who has become more important than the content.

Most popular tech podcasts are between 60-120 minutes each, recorded weekly — which is just absurd if you think about how little content is actually being shared. If these podcasters took time to plan out their shows with their podcasting partners, I wouldn’t be surprised if the shows were on average 30-60 minutes — or half their current length. ((But then where would you fit all six sponsors? OUTRAGE!)) If any one of these hosts sat down and wrote about the topics they wanted to cover on the podcast, their blog posts would be about 500 words (or less) for each topic. But yeah, go ahead and ramble on for two hours.

So here’s my proposal for making podcasts better: if you want me to spend 1-2 hours a week listening to your show, then you better spend at least that much time preparing for each show. Reading your RSS/Twitter feeds doesn’t count as preparation. ((You don’t actually have to do this, of course, because I don’t listen to a single podcast anymore.))

And, to bring this back around to a podcast here, there’s no way I am doing that amount of preparation for a medium that is positively futile trying to turn a profit in — so I won’t waste your time. ((Or mine, for that matter.))