Just wanted to share my initial experience using Daylite and Things.

One of the aspects I've found somewhat troublesome with Daylite is the amount of effort it takes to add several new tasks at once, i.e. a brain dump of things I know I need to do, quickly. I've also found that pipelines, while helpful with recurring projects that require the same general steps/stages, don't really give me the flexibility to organize project tasks, re-order tasks, etc. So I started using Things by Cultured Code. I have to say I find it easier and more intuitive to use than OmniFocus, and I recently found that by syncing Things with Calendar, I can also, by default, sync tasks--at least one direction--that I created in Things to Daylite. So I've played around with it a bit and other than the fact that once the tasks I sync are in Daylite I still need to link them to a project or contact, I'm finding it doable. And quicker--at least for tasks related to projects. I still create one-off or follow-up tasks in Daylite that arise during the course of a conversation or day. The only nag is that if I mark a task complete in Daylite, syncing doesn't work in reverse. If I mark a task complete in Things or in iCal it updates Daylite on the next sync.

I'd be interested in how other Daylite/Things users are combining the two programs to develop workflows.

I think Things is great.

It sync both ways via iCal at least. As long as you use categories also in iCal.

I love the way Things organizes the tasks and nested groups for tasks. I think if Daylite were to incorporate such structure it would be great.

However, using Things with Daylite is doable as you said. It reads quicker and seeing grouped tasks quickly as clusters, is more intuitive than what Daylite has at the moment.

I am just currently using them in tandem. I rarely need to link a contact to a task so this works perfectly.