I have been a DT user for over 10 years, and it’s my number one work-related app. I have been toying with note-taking apps like Apple Notes, Evernote, NotePlan, and Obsidian. I have about 200 GB of engineering files in my DT4 work database. I’ve been thinking about diving into Obsidian with both feet, and the more I study, the more I ask myself: with DT4’s ability to handle MD files and its linking, why not just use DT4 and my note-taking app?
Has anyone tried using DT4 with an Obsidian substitute?
So, DEVONthink as your main notetaker is a very viable choice, made by many.
But, if you want some advice on that, maybe explain more about what your typical notes are like. Just plain text. Rich text? Lots of tables? Or, lots of LaTeX. (Mathjax is supported DEVONthink.)
I’ve slowly been migrating all of my note-taking needs into DT. I won’t say what I’ve done is perfect, and others might approach entirely differently, but for me the selling point has been the ability to quickly link words/phrases/sentences to anything in DT. In that sense, some of my documents quickly become more like wikis than notes.
I was just at a conference and needed a single document that linked to various notes/groups in various databases. For the longest time I had been using RTF files, but these do not render the same on my iPad mini in DEVONthink To Go (and this is an Apple issue, not one to be solved by DT).
One day (also very recently) I ended up pointing ChatGPT at the latest DT manual, explained my frustration, and it suggested to try using markdown files. I think I tried once before, but never really took to it, but the way it explained how my ‘pain points’ could be solved with .md files, I figured I would try again. In the end, I think this will be my preferred format going forward. Still allow linking, of course, and highly customisable (well, the reader view is) using custom CSS.
I’ve previously posted what I think DEVONthink should add to bridge the gaps. It’s not much.
Obsidian is better at assigning metadata to Markdown files (the only type of file it really can process) through front matter. If DEVONthink did this, it would address longstanding gripes about the program-wide metadata selections which clutter the interface and require using inspectors that are not as straightforward to navigate to as the Markdown file itself.
Obsidian is better at showing views of a group with its bases feature. DEVONthink should offer per group view options. (Yes, I know a smart folder can be rigged to do this, but it creates additional friction and clutter). Ideally the icon view would also have user-definable fields that could display below the icons (including metadata).
DEVONthink offers a native Mac experience, very reliable sync, and a lot of other features Obsidian does not have. I don’t believe the above list would be a significant effort.
Properties can be declared at the front of markdown files in DEVONthink. These populate the “Properties” inspector.
tags: #single, #monumental
subject: test
title: Organized Chaos
organization: National Association of Keyboard Cleaners
copyright: 1945
comment: what would be better than butter?
author: Gandy Dancer
Aliases: Music History
(using properties defined in my test database)
If Settings > Files > Tags > Import > Convert hashtags to tags is set then the ``tags: line shown in the illustration will put the contents in the tags of the document
As I do research /a lot/ from iOS (my Mac cannot connect to office network), I wish that DTG (and DT) clipper (to MD) worked like Obsidian’s (thereafter OC).
OC captures a page as seen by the browser, including for all my content behind paywall.
OC shows me immediately the MD, rather that using the “create a doc API but fetch, parse and translate to MD once DTG is in the foreground.
OC uses the translated page when I use safari translation (I could post script that in DT, but I work first in DTG)
(last but not least, but off topic, someone needs to create a standard way to name the resource folder for a .md document, so the the .md and resource can be interpreted as one by systems)
I use DT4 and Obsidian. Used it to support my MA. DT4 as the centre for source material and Obsidian capture notes and to shape the dissertation. I would not recommend them as alternatives but rather as part of an integrated workflow.
Yes, they work fine together. I index my Obsidian vault inside a DT database. However, nowadays I have Obsidian only because of its integration with Readwise Reader.
When I first started using DT back in 2023 (I think), I was using Obsidian and very happy with it. But I found it challenging to be storing other documents that those notes referenced in another app (DT), especially when I knew DT could manage Markdown notes also. I sat down and documented the features that I cared most about in my note-taking app. There were 7 of them:
A UI that I love using (doesn’t discourage me from using it)
Easy to take notes with minimal friction
Easy to jump between notes and related content as I read so the flow isn’t disrupted
Powerful search so things are easy to find
Easy to create connections between notes
A system that organizes itself so I feel in control of my system without having to do periodic cleanup
Promotes a cohesive document management system
Obsidian hit the mark on 4 of them, and DT hit the mark on 6 of them. Through this analysis, I realized that the biggest thing keeping me in Obsidian was the UI that I loved, but eventually the friction it created from not having a single system won out. I started using DT for note-taking, and to keep it simple, I chose not to migrate my old notes over. I still have my Obsidian notes indexed so I can search them and find them. If I find that I need to update one or work with it, I just move it into DT at that time.
Long-time DT user here. For me DT is where everything lives, and Markdown is the format I write in. That’s also why I never felt the need for an Obsidian-style app on top. I have also tried Evernote, OneNote, Apple Notes etc.
One setup choice matters a lot: I index my files in DT instead of importing them. The .md files stay as normal files on disk, so I can reach them from the file system and from any other app, while DT still gives me search, tags, links and AI on top. I like that the files are never locked inside a database.
Typora is my helper next to it, not a replacement for anything:
AI output straight into DT as Markdown. When I ask DT to review something, for example a data processing agreement, I tell it to save the result as an .md file. It lands next to the source document, searchable and linkable like everything else.
Meetings. Because the files are indexed, I can open the same .md directly in Typora and share it on screen. It has live preview, so there’s no raw syntax and no editor clutter, just the finished-looking document.
Reading and checking AI-generated documents. Typora is a pleasant way to read, tidy up and sanity-check them.
Export, only when needed. If something has to leave the house, I export to PDF or Word. Typora lets you set a separate theme for PDF export and a style reference document for Word (via Pandoc), so the output always keeps the same clean look without touching the source.
So the rule is simple: write in Markdown, keep it in DT, export to other formats only when someone else needs them. No second copy to maintain, and the .md stays the single source of truth. Like jczerwonka said, one system instead of two.