It’s easy to bang out a quick outline and later revise it. Multicolumn outlines are a major selling point. Omnipresence sync works well across devices, but you have to actively manage what you sync. There’s no straightforward way to sync templates between MacOS and iOS versions. Omni-automation seems promising but also very complex, not as accessbile as URL-based schemes available on many current apps like Omni’s own omnifocus. Export options do not support markdown natively. I still find the product useful because of ease of editing and multicolumn support, but these limitations are a big source of friction. A lot of the drawbacks I see with this app date to decisions Omni made when icloud sync simply did not work. That’s when they opted for omnipresence as a way to sync individual files across machines. That works but does not scale well across more than a few files. Omnipresence does not support folders and hierarchies. It does not natively integrate with the iOS 11 files app. In other words, the strategy adopted a few years ago to work around non-functioning core apple technologies is a drawback now that apple has an architecture that actually works. Similar remarks can be made for automation. There’s not a simple way to link to a file and have it open in omnioutliner. Part of this is due to omni’s powerful but complex automation strategy. Part of this is due to the reliance on omnipresence. Export strategies seem to focus almost exclusively on Microsoft Word and PDF. A native markdown export option would be a nice addition for simple single column outlines.